This chapter discusses how to:
Define permissions.
Set up Query Access Services (QAS).
This section discusses how to:
Set up Crystal Enterprise roles in PeopleSoft Enterprise.
Set up Query profiles.
Grant web library permissions.
Page Name |
Object Name |
Navigation |
Usage |
User Profiles – Roles |
USER_ROLES |
PeopleTools, Security, User Profiles, User Profiles, Roles |
Set up Crystal Enterprise roles. |
Query Profile |
SCRTY_QUERY_PROF |
PeopleTools, Security, Permissions & Roles, Permission Lists, Query Click the Query Profile link. |
Set up permissions to Run Reports, Run to Crystal and Run to Excel. |
WebLib Permissions |
ACL_WEBLIB_ACCESS |
PeopleTools, Security, Permissions & Roles, Permission Lists, Web Libraries Click the Edit link. |
Set up web library permission for your Query. |
Access the User Profiles - Roles page.
In order to provide seamless security integration between PeopleSoft and Crystal Enterprise, a user must be assigned to a role:
A user with this role can see the Run to Crystal link on the Query Manager search page or Query View page.
A user with this role can see the Launch the Admin Launchpad URL on the Launch Crystal Enterprise page.
Access the Query Profiles page.
In order for the Crystal and Excel links to appear on the Query Manager search page, you must select Run to Excel and Run to Crystal in the PeopleSoft Query Output section of the page.
In order for Crystal Enterprise to invoke any Query web service, it must be granted full access to the relevant iScript.
To grant Web Service access for the Query:
Access the Weblib Permission page.
In the Function column, select Full Access for the row labeled ISCRIPT2.FieldFormula.IScript_GetCrystalURL.
Click OK to save your changes.
This section provides an overview on QAS setup and discusses how to:
Configure QAS
Configure Crystal Enterprise
Query Access Services are implemented using the PeopleTools Integration Broker (IB) framework. All the web services exposed by QAS are implemented as synchronous inbound messages using the IB framework. The Integration Gateway web application receives all the web services requests and forwards them to the Integration Engine (application server) for processing.
Note. For all QAS messages, a node called QAS_REMOTE that represents the requesting entity (Crystal Enterprise) is available. Currently, QAS does not support node level password for this node.
Page Name |
Object Name |
Navigation |
Usage |
Query Access Services |
PSQASCONFIG |
PeopleTools, Query Access Services, Configure, Query Access Services |
Define the QAS Integration Gateways URL and the QAS results repository URL. |
Crystal Enterprise |
PSCECONFIG |
PeopleTools, Query Access Services, Configure, Crystal Enterprise Reporting Tools, Crystal Enterprise, Launch Crystal Enterprise Click the Configure Crystal Enterprise link on the Launch Crystal Enterprise page. |
Define the location of the Crystal Enterprise Report Explorer and the location of the Crystal Management Server (CMS). |
Access the Query Access Services page.
To set up QAS:
If you've defined the Integration Gateway default local node, the QAS URL is automatically pre-populated. This URL is synonymous to the one that you use to launch the Crystal Enterprise.
Otherwise, go to the next step.
Click the Edit Integration Gateway URL to access the Gateways page where you can modify the Integration Gateway URL.
Click the Ping button to test the URL.
If the test is successful, the system returns an XML response.
Enter the Query Access Services Result Repository URL.
This URL is used to write the temporary query results into a file location that is specified in the IntegrationGateway.properties file.
Click the corresponding Ping button to test the URL.
If the test is successful, the system returns an XML response.
Enter the Max Query Size in megabytes. This parameter controls the maximum size of the query result set that you can fetch based on the size of QAS WSDL specifications.
The default value is 500.
Click Save to save the settings.
Note. All the URLs on this page are case sensitive, including the Edit Integration Gateway URLlink.
BEA Jolt Connect String Properties
QAS requires that appropriate BEA Jolt Connect String Properties must be configured in the Integration Gateway Properties file, so that incoming QAS requests can be routed to the correct receiving node (application server).
Either the Default BEA Jolt Connect String Properties or the BEA Jolt Connect String Properties for Known Nodes can be configured.
See Using the integrationGateway.properties File.
The following is an example of Default BEA Jolt Connect String Properties:
ig.isc.serverURL=//MYMACHINE:9000 ig.isc.userid=TOPDOG ig.isc.password=VOBN5KcQZMg ig.isc.toolsRel=8.46
One Gateway for Multiple Applications
You can use a single Gateway to configure multiple PeopleSoft applications and one webserver for multiple PeopleSoft applications. To specify multiple applications in one Gateway, you need to add the nodes corresponding to the applications to the IntegrationGateway.properties file.
The following example illustrates how you can specify multiple applications in one IntegrationGateway.properties file.
## default node ig.isc.serverURL=//PLE-KKO:9000 ig.isc.userid=QEDMO ig.isc.password=5/SS3MfAFH4= ig.isc.toolsRel=8.46-111-I1
## non-default node ig.isc.FS_LOCAL.serverURL=//PLE-KKO1:9000 ig.isc.FS_LOCAL.userid=VP1 ig.isc.FS_LOCAL.password=Ez6NDsqOkxI= ig.isc.FS_LOCAL.toolsRel=8.46-111-I1
## non-default node ig.isc.HR_LOCAL.serverURL=//PLE-KKO2:9000 ig.isc.HR_LOCAL.userid=VP1 ig.isc.HR_LOCAL.password=Ez6NDsqOkxI= ig.isc.HR_LOCAL.toolsRel=8.46-111-I1
In the above example, the default node doesn't specify any PeopleSoft application. However, in the non-default nodes, you can see that FS_LOCAL and HR_LOCAL are default nodes used by the Financial and Human Resource application, respectively.
Important! When you add a new domain in Crystal Enterprise, you need to specify the node name on the URL if you are not using the default node of the Gateway.
QAS Repository Location
QAS stores the query result files temporarily in the QAS repository. The location of QAS repository can also be specified in the IntegrationGateway.properties File by the following parameter:
ig.qas.repositoryHomeDir=<full-path for QAS Repository Location>
If this parameter is not configured, QAS stores the temporary files in the default location under the PSIGW web application, for example: %PS_HOME%\webserv\peoplesoft\applications\peoplesoft\PSIGW
See Using the integrationGateway.properties File.
Additional Configuration
For any additional Integration Gateway configuration such as security, refer to the Enterprise PeopleTools 8.46 PeopleBook: PeopleSoft Integration Broker .
See Also
Access the Crystal Enterprise page.
To set up Crystal Enterprise in the PeopleSoft Pure Internet Architecture:
Enter the Crystal Enterprise Web Server URL (http://<machine name>:<port number).
You can use this URL to access the Report Explorer and the Crystal Management Console.
If you want to access the Crystal Management Console (CMC) log on page directly, click either the URL link or the Ping button.
Enter the Crystal Management Server (CMS) machine name and port number.
This URL is used to access the Crystal Enterprise CMS database.
Click the Ping button to test the CMS machine name.
If the test is successful, the message “The Crystal Enterprise CMS database is up and running” appears.
The CE Domain Name is optional.
You don't need to enter a domain name unless you have multiple domains.
If you enter a domain name, you can see a read-only concatenation of the CE Domain name and your current PeopleSoft user ID at the bottom of the page, for example: CRM\CEMGR, when you tab out of the field.
Click Save to save your settings.