Configuring PeopleSoft

You must complete some initial configuration tasks within PeopleSoft, and then some additional configuration tasks required for each component.

Note:
For more information about the tasks listed in these sections, refer to your PeopleTools documentation that describes the PeopleSoft Integration Broker.

Configuring the PeopleSoft application

Complete the following tasks. These are required to set the PeopleSoft application correctly for the delta update propagation process.

  1. Activate the Pub/Sub Server Domain and add a node definition.

    Make sure that the following values are set for the node properties.

    Property Value
    Node Name User created
    Node Description User created
    Node Type PIA
    Routing Implicit
    Authentication None
    Activate Node check box Selected
  2. Specify a gateway and connector for the current node. If the gateway is not available, create one locally with a URL similar to this example: http://gateway_server/PSIGW/PeopleSoftListeningConnector
    Note:
    Gateway_server is the machine name and port, host name, or IP address of the web server hosting the gateway. The gateway uses the PeopleSoft listening connector to receive messages from an integration engine node or a remote gateway.
  3. Edit the JMSTargetConnector properties so that their values match those shown below.
    Property Value Notes
    sendUmcompressed Y
    JMSAcknowledgement AUTO_ACKNOWLEDGE
    JMSDeliveryMode NON_PERSISTENT
    JMSFactory Example value:
    psQCF
    Make this the value of the JMS administered QueueConnectionFactory object in the.bat file.
    JMSMessageTimeToLive 0
    JMSMessageType Text
    JMSPriority 0
    JMSProvider MQSeries
    JMSQueue Example value:
    psQ
    Add this property if it does not already exist. Make its value the value of the JMS administered Queue object in the.bat file.
    JMSReplyTo FALSE
    JMSUrl Point to the directory where you put the.bindings file on the client machine.
  4. Use PeopleTools Application Designer to create a project.

Configuring PeopleSoft components

In addition to the initial tasks you must complete to set up the PeopleSoft application for delta event propagation, you must also complete the following tasks for each component for which you want delta events propagated.

  1. Use PeopleTools Application Designer to build the component and to include the component in the project.
  2. Define a message with a structure similar to the component of interest.

    This means that the message must have the same hierarchy of records as the component. Make sure all primary records are included, and if the component has up datable views, make sure the view records are also included in the message structure.

  3. Open the SavePostChange event function for the component in Application Designer. Add the following PeopleCode at the beginning of the file, replacing TEST_MSG with the name of the message you have just created in step 2.
    Local Message &MSG;
    Local Rowset &ComponentBuffer;
    
    If ComponentChanged() Then
          &ComponentBuffer = GetLevel0();
       
       &MSG = CreateMessage(Message.TEST_MSG);
       &MSG.CopyRowsetDelta(&ComponentBuffer);
       
       &MSG.Publish();
    End-If;
  4. Add an Asynchronous Outbound Transaction to the node.
  5. Generate a WSDL document for the message created in step 2. When the WSDL is generated, it will open in a browser.
  6. Select all in your browser and save as a.WSDL file.
  7. Use the following script to extract the xsd file from the WSDL file you just saved.

    sed '/wsdl/d' $1 | sed '/soap/d' | sed '/xml
    version="1.0"/d'| sed 's/- <xsd:/  <xsd:/g' | sed 's/-
    <\/xsd:/<\/xsd:/g' | sed 's/  <xsd:/<xsd:/g' | sed 's/ 
    <\/xsd:/<\/xsd:/g' > $2

    Save the script to a file, named convertWsdlToXSD.sh. The script executes as follows:

    sh convertWsdlToXSD.sh <INPUTFILENAME> <OUTPUTFILENAME>
    where <INPUTFILENAME> is the name of the WSDL file and
    <OUTPUTFILENAME> is the name of the XSD file
    to be generated

You must complete steps 1 through 7 for each PeopleSoft component for which you want delta changes to be routed from PeopleSoft to the adapter.

Use the XMLODA to generate the business object definition for the corresponding XSD extracted in step 5 above. This definition will be used by the adapter to send the events to the integration broker, InterChange Server Express.

Copyright IBM Corp. 2004, 2005