In Tools 8.50 the ‘secureFileKeystorePasswd’ parameter of the integrationgateway.properties file must now be encrypted.

This posts is a part of the PeopleTools 8.50 Hints & Tips series on BAOA regarding PeopleSoft 8.50 tools upgrade.

That can be done  through the application so that you do not need to restart the web server.
1. Navigate to PeopleTools -> Integration Gateway -> Configuration – Gateways.

PeopleCode compile error after a Tools-only upgrade to PeopleTools 8.50

This posts is a part of the PeopleTools 8.50 Hints & Tips series on BAOA regarding PeopleSoft 8.50 tools upgrade.

Five new keywords have been introduced in PeopleTools 8.50:

• Primitive
• Compound
• Collection
• Document
• DocumentKey

Some applications released before 9.1 use the word “collection” as class name what result in a PeopleCode compiler error such as:

PeopleCode compiler error.(The create operator can only be used for application classes(2,96)) for program xxxx.yyyy.OnExecute(2,405).

My previous post was about the integration between Siebel and BI Publisher that was available since Siebel 8.1. As I mentioned back then, the integration is promising, but presented  some serious limitations to BI as a report generation tool for Siebel, and I promised to touch this issue again in a new post. Well, here we go.

With the patch to Siebel 8.1.1.1, some of the isssues have been resolved, while some serious new ones have been created. Our main reason to upgrade (Siebel to 8.1.1.1 and BI Publisher to  10.1.3.4.1) were issues with Active Directory. The Siebel Security Model provided by BI was not documented nor functioning properly in the earlier version. This has been resolved in the new version. The Siebel Security Model basically works like this: a user requests a report, BI then checks in Siebel whether the user has the right responsibility (yes, you need to add the XMLP_DEVELOPER responsibility to each user that needs to create reports) and then BI creates the report and sends it back to Siebel. Works a like charm!

Last week, during our practice meeting, Oracle provided us with a presentation about Fusion Applications. Very interesting to see what the scope of V1 is and what the approach to customers will be.

Everybody has heard that Fusion Applications is generally available in the first quarter of 2011. Co-existence is the approach to current and new customers. By implementing Fusion modules within the current application landscape, Oracle will introduce Fusion Applications at customers.

The focus area’s for co-existence are:

• HCM: Talent Management
• HCM: Workforce Lifecycle Management
• FMS: Accounting Hub
• CRM: Sales Territory Management

 I’m trying now to arrange demo’s focussing on Fusion HCM and CRM. That will make our consultants even more enthusiastic !!!

This posts is a part of the PeopleTools 8.50 Hints & Tips series on BAOA regarding PeopleSoft 8.50 tools upgrade.

Configuring Report Manager – List/Explorer – PeopleTools 8.50

Report Manager is a utility in PeopleSoft to view reports from another place than Process Monitor. It has fours pages: List, Explorer, Administration and Archives.

Setup of Integration Broker needs to be done and PUB/SUB App Server Processes are required to be up and running.

Configuration steps

Service Operation configuration

IB needs to be configured for four services

• PSRF_FOLDER_CREATE
• PSRF_REPORT_CREATE
• PSRF_REPORT_DATE _CHANGE
• PSRF_REPORT_DELETE

Navigate to PeopleTools -> Integration Broker -> Integration Setup -> Service Operations

Open Service Operation  PSRF_FOLDER_CREATE

In the General tab:

• Be sure that  the Service Operation  active
• If the Routing status from Local-to-local is “Does not exist”, check “Generate Local- to-Local” and click the Save button.

In the Routings tab, verify if there is only one routing definition active.

Repeat this step for the other  three services.

Clean cache and restart the application server.