Package in which to configure the connection.

You must create the package using Designer before you can specify it for this parameter. For general information about creating packages, see the webMethods Service Development Help for your release.

Folder in which to configure the connection.

Name you want to give the connection. Connection names cannot have spaces or use special characters reserved by the Designer. For more information about the use of special characters in package, folder, and element names, see the webMethods Service Development Help for your release.

Host name or IP address of the machine on which your PeopleSoft Application Server is running.

Port number of the PeopleSoft Application Server.

Default value is 9000.

User name that you use on your PeopleSoft Signon window.

Password that you use on your PeopleSoft Signon window.

Optional. Domain connection password to add an extra layer of security between the application server domain and the connections created.

PeopleSoft language code that the adapter uses to create all PeopleSoft sessions with locale-specific information.

Default: Blank. The PeopleSoft system will use the base Locale and base tables for all transactions.

PeopleSoft country code that the adapter uses to create all PeopleSoft sessions with locale-specific information.

Default: Blank. The PeopleSoft system will use the base Locale and base tables for all transactions.

See PeopleSoft Country Codes and Language Codes for PeopleSoft Language Codes and equivalent ISO Locales.

PeopleTools version of the backend PeopleSoft application server.

Default: PeopleTools version of the psjoa.jar file used.

Enables the adapter service templates to provide a list of all available CIs for you to choose when configuring a service.

If you select FALSE, you must type the exact name of the CI you want the adapter service to use on the Component Interface tab when you configure the adapter service.

If you select TRUE, each PeopleSoft Adapter service template displays a list of all available CIs on the PeopleSoft system. You can select a CI from the list when you configure the adapter service. Selecting this option has the following effects on adapter service configuration and on connections:

To configure adapter services successfully, all classes of the selected CI must be included in the PeopleSoft.zip file that is located in the WmPeopleSoftAdapter\code\jars directory.

If the CI is available in the list but is not included in the PeopleSoft.zip file, you will receive the error "Can not find component interface…". For more information about the PeopleSoft.zip file, see Configuring Adapter Connections.

Enables the adapter to use connection pooling. Default: true.

See Adapter Connections for more information about connection pooling.

If connection pooling is enabled, this field specifies the minimum number of connection objects that remain in the connection pool at all times. When the adapter creates the pool, it create this number of connections. Default: 1.

Maximum number of connection objects that can exist in the connection pool. When the connection pool has reached its maximum number of connections, the adapter will reuse any inactive connections in the pool or, if all connections are active, it will wait for a connection to become available. Default: 10.

If connection pooling is enabled, this field specifies the number of connections by which the pool will be incremented if connections are needed, up to the maximum pool size. Default: 1.

If connection pooling is enabled, this field specifies the number of milliseconds that the Integration Server will wait to obtain a connection with the database before it times out and returns an error.

For example, you have a pool with Maximum Pool Size of 20. If you receive 30 simultaneous requests for a connection, 10 requests will be waiting for a connection from the pool. If you set the Block Timeout to 5000, the 10 requests will wait for a connection for 5 seconds before they time out and return an error. If the services using the connections require 10 seconds to complete and return connections to the pool, the pending requests will fail and return an error message stating that no connections are available.

If you set the Block Timeout value too high, you may encounter problems during error conditions. If a request contains errors that delay the response, other requests will not be sent. This setting should be tuned in conjunction with the Maximum Pool Size to accommodate such bursts in processing.

If connection pooling is enabled, this field specifies the number of milliseconds that an inactive connection can remain in the pool before it is closed and removed from the pool.

The connection pool will remove inactive connections until the number of connections in the pool is equal to the Minimum Pool Size. The inactivity timer for a connection is reset when the connection is used by the adapter.

If you set the Expire Timeoutvalue too high, you may have a number of unused inactive connections in the pool. This consumes local memory and a connection on your backend resource. This could have an adverse effect if your resource has a limited number of connections.

If you set the Expire Timeoutvalue too low, performance could degrade because of the increased activity of creating and closing connections. This setting should be tuned in conjunction with the Minimum Pool Size to avoid excessive opening/closing of connections during normal processing.

Number of times that the system should attempt to initialize the connection pool at startup if the initial attempt fails. Default: 0 (a single attempt).

Number of seconds that the system should wait between attempts to initialize the connection pool. This field is irrelevant if Startup Retry Count is 0. Startup Backoff Timeout's default is 10.