Configuring the PeopleSoft Server for the PeopleSoft Adapter Projects

This section provides configuration information for the PeopleSoft Integration Gateway and Java CAPS postings.

• Configuring PeopleTools 8.42

• Configuring PeopleTools 8.13

Overview

For Java CAPS to post and receive messages from PeopleSoft, you must configure the PeopleSoft server. The configurations are different for PeopleTools 8.13 and 8.42. For PeopleTools 8.42, there are also different configurations depending on whether the PeopleSoft adapter Project uses JMS, HTTP, or both. The table summarizes the different configurations.

Table 27 Configuration Requirements for PeopleSoft

Version JMS HTTP PeopleTools 8.42 Source node Target node .bindings file IntegrationGateway.properties Source node Target node HTTP listening connector HTTP publication handler PeopleTools 8.13 n/a PeopleSoft message node HTTP message node Message channel inbound Message channel outbound PeopleSoft subscription handler HTTP publication handler

The sections describe how to configure PeopleSoft servers to communicate with the PeopleSoft adapter using PeopleTools 8.42 or 8.13. Information about the PeopleSoft server can be found in the PeopleBooks documentation provided by PeopleSoft.

Configuring PeopleTools 8.42

This section describes how to configure PeopleTools 8.42 to integrate using Java CAPS. When you use this version of PeopleTools, you can create the PeopleSoft adapter Projects that use inbound and outbound JMS data flows, and inbound HTTP data flows. Inbound HTTP data flows are only supported when you use a Java CAPS Business Process Manager implementation of the adapter.

Configuring PeopleSoft for Enterprise Service Bus Posting

The following section describes how to create PeopleSoft nodes to receive and post messages with Oracle Java CAPS.

To Create Source Nodes to Receive Enterprise Service Bus Posts

The procedure describes how to set up the PeopleSoft node to receive Enterprise Service Bus messages.

1. Log into the PeopleSoft server.
2. Follow the PeopleSoft documentation to create a new node and configure it.
   
3. Add a transaction for the Enterprise Service Bus post using your own naming convention and configure it.
   
4. Click Edit.

   The Transaction Detail tab appears.

   
   
5. Configure the transaction.
6. Click Messages. From the Messages tab, configure the messages for the Enterprise Service Bus post.
   

To Activate Message Channels to Receive Enterprise Service Bus HTTP Posts

Each channel must be defined and activated before the adapter can post any data. The procedure describes how to activate the message channels for subscription to the PeopleSoft adapter.

1. From the PeopleSoft Application Designer, create a channel. You can use the default properties.
2. Create the request and response message definitions. These message do not require PeopleCode.
3. Click Message Properties.

   The Message Properties dialog box appears.

4. Select the Active option and click OK.
   

   Figure 1 Activating Message Channels

   

To Create Target Nodes to Post Messages to Enterprise Service Bus Using HTTP

The procedure describes how to create and configure PeopleSoft nodes to post messages to Enterprise Service Bus using HTTP.

1. Follow the PeopleSoft documentation to create a new node using your own naming convention and configure it.
   

   Figure 2 Creating Nodes to Post to Enterprise Service Bus

   
2. Select the target connector ID. From the Connectors tab, enter the values displayed in the following figure.
   

   Figure 3 Configuring the Connector to Post to Enterprise Service Bus using HTTP

   

   Use the following format for the PRIMARYURL property:

   http://<yourmachinename>:18001/<yourdeploymentname>_servlet_<servletname>
   /<servletname>

   This property must match the logical Adapter Servlet-url property defined in the NetBeans IDE . The port number must match the default Web server port number specified in the application server properties in the Environment. The Deployment Profile is the name of the Project’s Deployment Profile defined in NetBeans. The Deployment Profile name must be followed by _servlet_servletname.

3. Configure the transaction.
4. Click Edit.
5. Click Messages. The Messages tab is displayed.

To Create the Target Node to Post to Enterprise Service Bus Using JMS

After creating the source node in PeopleTools, follow the procedure to create the JMS target node.

1. Follow the PeopleSoft documentation to create a new node using your own naming convention and configure it.
   

   Figure 4 Creating Nodes to Post to Enterprise Service Bus Using JMS

   
2. Select the target connector ID, and enter the values shown.
   

   Figure 5 Configuring the Connectors to Post to Enterprise Service Bus Using JMS

   

   The JMS properties, such as persistence and acknowledgement modes, must match the settings for the JMS client as defined from the Connectivity Map. For information about JMS properties, refer to the Oracle Java CAPS JMS Reference .

   The JMSQueue or JMSTopic property must match the name of the queue/topic in the Connectivity Map. The target destination must match the incoming queue/topic, and the source destination must match the outgoing queue/topic.

   The JMSFactory property must point to the topic or queue ConnectionFactory for the topic or queue properties in the JNDI bindings file.

   The JMSUrl property must point to your JNDI bindings file (see To Create the JNDI Bindings File).

   Make sure that the node that uses JMSTargetConnector as the connector is setup correctly in regard to the JMSUserName and JMSPassword properties.

Additional HTTP Configurations

Two types of HTTP connectors are used with PeopleSoft adapter Projects that use HTTP to communicate to PeopleSoft: the HTTP listening connector and the HTTP target connector.

The PeopleSoft server uses the HTTP listening connector to receive messages from. The PeopleSoft adapter HTTP client external application is used to post to the HTTP listening connector. You do not have to configure the HTTP listening connector; the connector is started automatically by the PeopleSoft Integration Application.

However, you must set the location for the HTTP listening connector in the Environment properties of the PeopleSoft Adapter. The routing of messages in the PeopleSoft server is decided by the content of the message in the header section.

The HTTP target connector is used to send HTTP messages to Enterprise Service Bus. The Enterprise Service Bus component receiving the HTTP message is a servlet. The servlet name is specified in the Connectivity Map.

To Verify the HTTP Listening Connector

1. In a text editor, open the web.xml file from WebLogic_Home\config\peoplesoft\applications\PSIGN\WEB-INF.
2. Verify that the following section is included, and add it if it is absent.
   

   Figure 6 Verifying the HTTP Listening Connector

   

Additional JMS Configurations

Additional JMS configuration tasks include the following:

• To Configure Inbound JMS Connections

• To Create the JNDI Bindings File

• Starting and Stopping the JMS Listening Connector

• Verifying the JMS Connection

To Configure Inbound JMS Connections

To configure inbound JMS connections, edit the IntegrationGateway.properties file as described in the procedure.

1. Open the IntegrationGateWay.properties file from WebLogicHome\config\peoplesoft\applications\PSIGW\WEB-INF.
2. Edit the file for the JMS queue listener properties.

   You can configure multiple queues by using the convention ig.jms.queue1, ig.jms.queue2, ig.jms.queue3, and so on. The following table shows how the JMS listener is configured for the GenericOutQueue.

   JMS Queue Listener Properties

   
   

   ig.jms.Queues=1 “1” indicates only one queue. ig.jms.Queue1=GenericOutQueue The first queue name “GenericOutQueue”, must be the same in the .bindings file. The Java code used to generate the entry in the .bindings is: queue = new STCQueue("GenericOutQueue"); q = null; try { q = (Queue) jndifContext.lookup("GenericOutQueue"); System.out.println(q.getClass().getName()); } catch (Exception e) { System.out.println("fcontext GenericOutQueue lookup exception"); e.printStackTrace(); } if (q == null) { System.out.println("q is null...bind GenericOutQueue as GenericOutQueue"); jndifContext.bind("GenericOutQueue", queue); } ig.jms.Queue1.Provider=SunSeeBeyond The “SunSeeBeyond” entry must match the configuration entry in the integrationgateway.properties file: ig.jms.JMSProvider.JNDIFactory.SeeBeyond=com.sun.jndi.fscontext.RefFSContextFactory ig.jms.Queue1.JMSFactory=QueueConnectionFactory “QueueConnectionFactory” is the JNDI name in the .bindings file. Use the following Java code to generate the entry: QueueConnectionFactory tgtqcf = null; try { /*you can change the jndi name here, the jndi name use here must be exactly same *as in the websphere’s Generic JMS Provider’s configuration External JNDI Name */ tgtqcf = (QueueConnectionFactory) jndifContext.lookup("Queue ConnectionFactory"); } catch (Throwable e) { System.out.println("fcontext Queue ConnectionFactory lookup exception"); e.printStackTrace(); } if (tgtqcf == null) { System.out.println("fcontext Queue ConnectionFactory lookup is null..."); jndifContext.bind("QueueConnection Factory", srcqcf); } else { System.out.println("fcontext Queue ConnectionFactory is NOT null...unbind then re-bind QueueConnectionFactory"); jndifContext.unbind("Queue ConnectionFactory"); jndifContext.rebind("Queue ConnectionFactory", srcqcf); } ig.jms.Queue1.MessageSelector= See the Oracle Java CAPS JMS Reference . ig.jms.Queue1.Url=file:c:/jndibindings/ The URL of the .bindings file. Because PeopleSoft only supports fcontext, this is a directory name. ig.jms.Queue1.User=Administrator User name to Enterprise Service Bus JMS server. ig.jms.Queue1.Password=SwBAuVVABok= Encrypted value of the password to Enterprise Service Bus JMS server. Use the PeopleSoft utility pscipher to get the encrypted value.

3. Edit the file for the JMS queue listener properties.

   You can configure multiple queues by using the convention ig.topic1, ig.topic2, ig.topic3, and so on. The table shows how to configure the JMS topic to use the GenericOutTopic.

   JMS Queue Listener Properties

   
   

   ig.jms.Topics=1 “1” indicates only one topic. ig.jms.Topic1=GenericOutTopic The first topic name “GenericOutTopic”, must be the same in the .bindings file. The Java code to generate this entry in the .bindings is: topic = new STCTopic("GenericOutTopic"); t = null; try { /*you can change the jndi name here, the jndi name use here must be exactly same *as in the websphere’s Generic JMS Provider’s configuration External JNDI Name */ t = (Topic) jndifContext.lookup ("GenericOutTopic"); System.out.println(t.getClass(). getName()); } catch (Exception e) { System.out.println("fcontext GenericOutTopic lookup exception"); e.printStackTrace(); } if (t == null) { System.out.println("t is null...bind GenericOutTopic as GenericOutTopic"); jndifContext.bind("GenericOutTopic", topic); } ig.jms.Topic1.Provider=SunSeeBeyond The “SunSeeBeyond” entry must match the configuration entry in the integrationgateway.properties file: ig.jms.JMSProvider.JNDIFactory.SeeBeyond=com.sun.jndi.fscontext.RefFSContextFactory ig.jms.Topic1.JMSFactory=TopicConnectionFactory “TopicConnectionFactory” is the JNDI name in the .bindings file. Use the following Java code to generate the entry: TopicConnectionFactory tgttcf = null; try { /*you can change the JNDI name here, the JNDI name use here must be exactly same *as in WebSphere’s Generic JMS Provider’s configuration External JNDI Name */ tgttcf = (TopicConnectionFactory) jndifContext.lookup("TopicConnectionFactory"); } catch (Throwable e) { System.out.println("fcontext TopicConnectionFactory lookup exception"); e.printStackTrace(); } if (tgttcf == null) { System.out.println("fcontext TopicConnectionFactory lookup is null..."); jndifContext.bind( "TopicConnectionFactory", srctcf); } else { System.out.println("fcontext TopicConnectionFactory is NOT null...unbind then re-bind TopicConnectionFactory"); jndifContext.unbind( "TopicConnectionFactory"); jndifContext.rebind( "TopicConnectionFactory", srctcf); } ig.jms.Topic1.MessageSelector= Refer to the queue table. ig.jms.Topic1.Url=file:c:/jndibindings/ Refer to the queue table. ig.jms.Topic1.User=Administrator Refer to the queue table. ig.jms.Topic1.Password=SwBAuVVABok= Refer to the queue table.

To Create the JNDI Bindings File

To enable the PeopleSoft Adapter to post to PeopleSoft using JMS, you must have a JNDI bindings file in place. You can generate the bindings file with any standard JNDI generation application. Oracle provides a sample generation application called PSFTBindJMS.java. This program and two associate applications, compile.bat and run.bat, are included in the sample Project file.

You must edit and recompile the PSFTBindJMS.java file before generating the bindings file.

1. Create the directory, C:\testprogram.. Copy the PSFTBindJMS.java, compile.bat, and run.bat files to this directory.

   ---

   Note - The latest version of the Enterprise Service Bus API Kit JAR files must be added to the WebLogic PeopleSoft-PIS server classpath. To confirm this, check the JAR files in the server’s setENV.cmd file located in the following location (or similar): WebLogic_Home\config\peoplesoft\setEnv.cmd. If you installed the PeopleSoft-PIA service as a Windows Service, you must uninstall and reinstall the service by running unInstallNTServicePIA.cmd first, then running installNTServicePIA.cmd. This is a runtime classpath requirement to confirm the new classpath.

   ---

2. Open the PSFTBindJMS.java file in a text editor and follow the directions presented in the text of the file. Edit the JNDI bindings generation application with the Enterprise Service Bus host name and location. Verify that the Enterprise Service Bus JMS server port number is correct.

   This port number must match the Server port property for the JMS IQ Manager in the NetBeans. For more information, refer to the Oracle Java CAPS JMS Reference .

3. Modify the following line to point to your own directory. For example:

   fcontextprops.put(Context.PROVIDER_URL, "file:C:\\CAPSExports\\PeopleSoft\\JMS");

   ---

   Note - If you are installing Java CAPS and the PeopleSoft Adapter on a computer that had previous versions of Java CAPS or ICAN installed, be sure to delete all of the previously installed API JAR files, and follow the directions in the Enterprise Service Bus API Kit Developer’s Guide to modify your classpath to include the new API JAR files.

   ---

4. Double-click compile.bat to compile the program. A class file is generated.
5. Double-click run.bat to run the program. This creates a .bindings file.
6. Copy the .bindings file to the location of the JMSUrl property described in the section above.

   When you run the bindings generation application for the first time, the following message is displayed:

   fcontext TopicConnectionFactory lookup exception, you never had this jndi entry
   fcontext TopicConnectionFactory lookup is null... will bind to the jndi name
   fcontext GenericInTopic lookup exception, it doesn’t exist
   GenericInTopic is null...bind GenericInTopic as GenericInTopic
   fcontext GenericOutTopic lookup exception, it doesn’t exist
   GenericOutTopic is null...bind GenericOutTopic as GenericOutTopic
   fcontext ErrorTopic lookup exception, it doesn’t exist
   t is null...bind ErrorTopic as ErrorTopic
   fcontext QueueConnectionFactory lookup exception it doesn’t exist
   fcontext QueueConnectionFactory lookup is null...bind with new value
   fcontext GenericInQueue lookup exception, it doesn’t exist
   GenericInQueue is null...bind GenericInQueue as GenericInQueue
   fcontext GenericOutQueue lookup exception
   GenericOutQueue is null...bind GenericOutQueue as GenericOutQueue

   In the subsequent runs, the following message is displayed:

   fcontext TopicConnectionFactory is NOT null...unbind then re-bind 
   TopicConnectionFactory will overwrite old value
   com.stc.jms.client.STCTopic
   fcontext GenericInTopic is NOT null...unbind then re-bind GenericInTopic 
   will overwrite old valuecom.stc.jms.client.STCTopic
   fcontext GenericOutTopic is NOT null...unbind then re-bind GenericOutTopic 
   will overwrite old valuecom.stc.jms.client.STCTopic
   fcontext ErrorTopic is NOT null...unbind then re-bind ErrorTopic 
   will overwrite old value
   fcontext QueueConnectionFactory is NOT null...unbind then re-bind 
   QueueConnectionFactorycom.stc.jms.client.STCQueue
   fcontext GenericInQueue is NOT null...unbind then re-bind GenericInQueue 
   will overwrite old valuecom.stc.jms.client.STCQueue
   fcontext GenericOutQueue is NOT null...unbind then re-bind GenericOutQueue 
   will overwrite old value

7. Once you have completed all of these steps, restart the PeopleSoft-PIA services. You can restart the PIA services from the Windows Services console, or you can restart the service from a Command Line using the following command:

   startIA.cmd

   After you execute this command, monitor the PIA_weblogic.log file until you see the following output:

   #### <> <000329>

   This indicates that the PIA Service is started. If you use this method of starting the PIA service, be aware that the Windows Services console will not accurately reflect that the service has been started.

8. Stop and restart the JMSListeningConnector using the URL (see Starting and Stopping the JMS Listening Connector). After you start the JMS Listening Connector, monitor the PIA_weblogic.log. The following message indicates that the JMS Listening Connector has started correctly:

   #### <> <> <101047> <[WebAppServletContext(2244929,PSIGW,
   /PSIGW)] JMSListeningConnectorAdministrator: init>
   #### <> <> <101047> <[WebAppServletContext(2244929,PSIGW,
   /PSIGW)] PeopleSoftListeningConnector: init>

   If you follow the procedure To Create the JNDI Bindings File before the PIA service is ready, the JMS Listening Connector will not be active, so it will not receive messages from Enterprise Service Bus.

Starting and Stopping the JMS Listening Connector

To start the JMS Listening Connector, use the following command:

http://hostname:port/PSIGW/JMSListeningConnectorAdministrator?Activity=START

To stop the JMS Listening Connector, use the following command:

http://hostname:port/PSIGW/JMSListeningConnectorAdministrator?Activity=STOP

Verifying the JMS Connection

To verify if your JMS connection works, you can use the StartSendMaster.bat provided by PeopleSoft in the following location:

WebLogic_Home\config\peoplesoft\applications\PSIGW

Verifying PeopleSoft Server Logs

You can verify log information for the PeopleSoft server in the following directory:

WebLogic_Home\config\peoplesoft\applications\PSIGW

Notes on PeopleSoft Server Disconnections for JMS

If the domain is shut down during a JMS session with PeopleSoft, the PeopleSoft server may loose the session. You must reestablish the connection on the PeopleSoft server.

Configuring PeopleTools 8.13

This section describes how to configure PeopleTools 8.13 to integrate using the Enterprise Service Bus. When you use this version of PeopleTools, you can create PeopleSoft Adapter Projects that use inbound HTTP Collaborations. Outbound HTTP Collaborations are only supported when you use Java CAPS Business Process Manager together with Enterprise Service Bus.

perform the following tasks to configure PeopleTools 8.13:

• To Create PeopleSoft Nodes to Receive Enterprise Service Bus HTTP Posts

• To Activate the Message Definition to Receive Enterprise Service Bus Posts

• Defining Message Channel Routing Rules

• Adding the PeopleSoft Subscription Handler

• Configuring for Subscription

• Creating an HTTP Adapter Message Node

• Activating the Message Definition for Subscription

• Defining the Message Channel Routing Rules

• Adding the HTTP Publication Handler

To Create PeopleSoft Nodes to Receive Enterprise Service Bus HTTP Posts

The procedure describes how to create and configure PeopleSoft nodes for Enterprise Service Bus HTTP posting.

1. In the PeopleTools Application Designer, click New on the File menu.

   The New dialog box appears.

2. Click Message Node and click OK to display the Message Node dialog box for Node 1.
3. Right-click the Locations pane and click Insert Location.

   The Location dialog box appears.

4. Enter the URL for the PeopleSoft Gateway Servlet and click OK.

   For Apache:

   http://PSFTHOST/servlets/psft.pt8.gateway.GatewayServlet

   For WebLogic:

   http://PSFTHOST/servlets/gateway

   where PSFTHOST is the name of the host computer where PeopleSoft runs.

   The URL name displays in the Message Node dialog box similar to Figure 7.

   
   

   Figure 7 PeopleSoft Node for Receiving Enterprise Service Bus HTTP Posts

   
5. Click Save As on the File menu.
6. Enter the name of the message node.
7. From the File menu, click Open.

   The Open Object window appears.

8. To verify that the message node is ready for use, select Message Node from the Object Type list and click Open.

   A list of all message nodes appears. The name of the new message node appears in the Objects Matching Selection criteria pane.

   Message nodes with PSFT prefixes are created by the PeopleSoft installation. PSFT_EP is the PeopleSoft local node for the Financials application. It is specified as a subscriber to messages sent from the PeopleSoft Adapter, and a publisher of messages to the HTTP server.

   
   

   Figure 8 Viewing Message Nodes

   

To Activate the Message Definition to Receive Enterprise Service Bus Posts

PeopleSoft comes with a set of predefined message definitions. The desired message definition is configurable in the adapter with the Subject property. The following instructions describe how to activate the message definition for subscription to the PeopleSoft Adapter.

Each message used for publication must be defined. This definition corresponds to the XML message the adapter publishes, and contains the elements of the data to be published. However, before the Adapter can publish any data, the message definition must be activated. The Application Designer includes a list of these definitions.

1. In PeopleTools Application Designer, click Open on File menu.

   The Open Object dialog box appears.

2. Click Message from the Object Type list.

   This displays all available PeopleSoft message definitions.

   
   

   Figure 9 Viewing Available Message Destinations

   
3. Double-click the message definition.

   The Message window appears, displaying the record details of the chosen message structure.

   
   

   Figure 10 Message Structure Details

   
4. Click Object Properties on the File menu.

   The Message Properties dialog box appears.

5. Click the Use tab.
6. Select the Active option and click OK.
   

   Figure 11 Activating the Message Definition to Receive Enterprise Service Bus Posts

   
7. Save your current changes.

   You have now activated the message definition for publishing or subscribing.

Defining Message Channel Routing Rules

This procedure describes how to configure message channels. Before you start, determine which message channel you will use. You can configure the PeopleSoft Adapter for this message channel with the Channel property.

To Configure the Message Channel

Each message channel logically groups messages together. For purposes of the procedure, the ADVANCED_SHIPPING_RECEIPT message is grouped into the ADVANCED_SHIPPING_NOTICE message channel.

1. Log into the PeopleTools Application Designer.
2. Click Open on the File menu.

   The Open Object dialog box appears.

3. Select Message Channel from the Object Type list and click Open.

   This displays all available message channels.

4. Double-click the message channel to be used.

   The Message Channel window appears for that channel.

5. Click Routing Rules, right-click the pane, and from the shortcut menu, click Insert Message Node.

   The Insert Message Node dialog box appears, displaying the available message nodes.

6. Select PSFT_EP and click Insert.

   The message is inserted into the routing rules table.

7. Select STCPUBLISHER and click Insert.
8. Click Cancel to close the dialog box.

   The message nodes are now defined on the Routing Rules tab of the Message Channel window.

   
   

   Figure 12 Viewing the Message Nodes

   

To Define the Routing Directions

Routing directions provide you with the ability to assign destinations (Publish To/Subscribe From) to a message node. This section describes the procedure for defining the routing directions for the adapter message node, Subscribe From.

1. In the Routing Rules Tab of Message Channel window in the Application Designer, right-click Both (Publish and Subscribe) for STCPUBLISHER, click Routing Direction, and then click Subscribe From.
2. Right-click Both (Publish and Subscribe) for PSFT_EP, click Routing Direction, and then click Publish To.

   The Routing Rules tab now shows that the adapter message node is subscribing to messages from PSFT_EP and is publishing to STCHTTP.

   
   

   Figure 13 Viewing Routing Directions

   
3. Click Save on the File menu.

   You have now defined the routing rule that allows the appropriate message to be published from the adapter to PeopleSoft.

Adding the PeopleSoft Subscription Handler

The procedure describes how to add the PeopleSoft subscription handler. Before you start the procedure, make a note of the following PeopleSoft configurations:

• Jolt listener host

• Jolt listener port

• PeopleTools version

• Operator ID

• Operator ID password

To Add the PeopleSoft Handler Directory

1. Navigate to the following URL in a browser to open the handler directory:

   For Apache:

   http://PSFTHOST/servlets/psft.pt8config.ConfigServlet

   For WebLogic:

   http://PSFTHOST/servlets/gateway.administration

   where PSFTHOST is the host where the PeopleSoft Application Messaging Gateway is installed.

   The Handler Directory page appears.

   
   

   Figure 14 Adding the PeopleSoft Handler Directory

   
2. Click Add handler.

   The Add Handler page appears.

3. Enter the PeopleSoft handler class:

   psft.pt8.psfthandler.PeopleSoftHandler

   and click Save.

   
   

   Figure 15 Viewing the New Handler

   
4. Click Load to load the PeopleSoft handler class you just added.

   The status changes to Loaded successfully.

5. Click Configure to configure the handler.

   The Manage Lookup Table page for the PeopleSoft handler appears.

   
   

   Figure 16 Managing the Lookup Table

   
6. Click Add a New Node to associate the node with this subscription handler.

   The Add an Address window appears.

   
   

   Figure 17 Adding an Address

   
7. Enter the values for the new node, PSFT_EP, associated with the subscription handler. These values are mandatory.
8. Click Save address.

   The Manage Lookup Table page now displays the new node.

   
   

   Figure 18 Viewing the New Node

   

   The Application Messaging Gateway is now ready to receive XML messages from the adapter and publish the XML messages to PeopleSoft.

Configuring for Subscription

To configure PeopleSoft to publish XML messages to the PeopleSoft Adapter involves the following steps:

• Creating an HTTP Adapter Message Node.

• Activating the Message Definition for Subscription.

• Defining the Message Channel Routing Rules.

• Adding the HTTP Publication Handler.

Creating an HTTP Adapter Message Node

Refer to To Create PeopleSoft Nodes to Receive Enterprise Service Bus HTTP Posts to create a message node associated with the PeopleSoft Adapter. A message node called STCHTTP is used as an example.

Activating the Message Definition for Subscription

Refer to To Activate the Message Definition to Receive Enterprise Service Bus Posts to activate the message to be published to the PeopleSoft Adapter. In this case, activate the PO-EXPECTED_RECEIPT_SHIPTO message.

Defining the Message Channel Routing Rules

Refer to Defining Message Channel Routing Rules to define the routing rules for the message channel to be used.

• Insert the PSFT_EP message node and the HTTP message node previously created.

• Define the routing direction. Select Subscribe From for PSFT_EP and Publish To for the HTTP message node (STCHTTP).

Adding the HTTP Publication Handler

This procedure describes how to add the HTTP publication handler. Before you start, verify that the HTTP publication handler is installed. Also, obtain the HTTP configuration values for the adapter which is to receive the XML message(s) from PeopleSoft. These are required when configuring the message node corresponding to the subscription handler.

To Obtain the HTTP Configuration Values

1. Navigate to the following URL in a browser to open the handler directory:

   For Apache:

   http://<yourmachinename>:18001/<yourdeploymentname>
   _servlet_<servletname>/<servletname>.

   For WebLogic:

   http://<PSFTHOST>/servlets/gateway.administration

   where, <PSFTHOST> is the host where the PeopleSoft Application Messaging Gateway is installed.

   The Handler Directory page appears.

   
   

   Figure 19 Adding the PeopleSoft Handler Directory

   
2. Click Add Handler.

   The Add Handler page appears.

3. Enter the HTTP publication handler class and click Save.

   com.stc.ewpsoft8.stchttphandler.HTTPHandler

4. Click Save.

   The Handler Directory page displays the new handler.

   
   
5. Click Load.

   The status changes to Loaded successfully.

6. Click Configure for the HTTP handler.

   The HTTP Handler Directory page appears.

7. Click Add an HTTP Node to associate a node with this subscription handler.
8. Enter the values for the new node associated with the subscription handler. Scroll to the right to access additional columns.
9. In the Include Headers column, indicate whether or not you want header information to be retained in the received messages. All values are mandatory.
10. Selecting the check box preserves the header information.
11. Deselecting the check box strips the header information.
12. Click Save.

    The STCHTTP node entries appear. If the entries are correct, the Application Messaging Gateway now can receive XML messages from PeopleSoft and publish the XML messages to the PeopleSoft Adapter (in HTTP mode).

    You can now ping the HTTP host from the system where the com.stc.eWays.psofthandler.jar file is installed. You may need to use the system’s full host name.