PeopleSoft Connection policy (PeopleSoftConnection)

Use a PeopleSoft Connection policy to control, at run time, connections to PeopleSoft applications.

You can use PeopleSoftInput and PeopleSoftRequest nodes to accept input from, and send requests to, PeopleSoft applications. PeopleSoft nodes can get connection details from either the adapter component or a policy. By using a policy, you can change the connection details for an adapter at run time without the need to redeploy the adapter.

To enable connection details for the PeopleSoftInput or PeopleSoftRequest node to be retrieved from a policy, you must deploy a policy with the same name as the PeopleSoftAdapter, of type PeopleSoftConnection, in the default policy project for the integration server. This policy must be deployed before the message flow containing the PeopleSoft node is started. For example, if a PeopleSoftInput node is configured to use the adapter file PeopleSoftCustomerInbound.inadapter, ensure that the name of your PeopleSoftConnection policy is PeopleSoftCustomerInbound. When the PeopleSoft node starts, it uses connection details in the policy to connect to PeopleSoft.

If you redeploy a PeopleSoft Connection policy, all message flows that are using the policy will be stopped and restarted.

The properties of this policy are described in the following table:

Table 1. Properties of the PeopleSoft Connection policy
Property Property name in .policyxml file Description of properties

Host name

hostName

Identifies, either by name or IP address, the server that hosts PeopleSoft Enterprise.

This property is mandatory. By default, the value of this property is an empty string, therefore you must set a valid host name or IP address.

Port

port

The port number that the adapter uses to access the PeopleSoft Enterprise server.

This property is mandatory. By default, the value of this property is an empty string, therefore you must set a valid port number.

Connection idle timeout

connectionIdleTimeout

The number of seconds for which a connection can be idle before it is closed by IBM® App Connect Enterprise to effectively maintain the connection pool. The default value for this property is 0 (zero) seconds, indicating that no timeout occurs.