Configuration Manager - Payments - Instance

The Instance page of the Configuration Manager is used to specify basic information about the WebSphere Commerce Payments instance. 

Instance Name
Enter the name that you want to call your WebSphere Commerce Payments instance.  The default name is wpm. You will not be able to modify this name later, so ensure that you choose a name carefully.
iSeries The name must be 10 characters or less.
Password Required for startup
Select this check box to require the manual entry of the Payments instance password whenever WebSphere Commerce Payments is started. The default is to require entry of the Payments instance password at startup.  (If you are starting a Payments instance through the Configuration Manager, however, manual entry of the instance password is not required regardless of this check box setting.) If you would like to encrypt and store the instance password so that you do not have to enter the instance password whenever a Payments instance is restarted, deselect this check box. For more information about starting WebSphere Commerce Payments through the IBMPayServer command or through other methods, refer to the WebSphere Commerce Installation Guide.
Instance Password
Enter the password to be associated with this Payments instance.
WebSphere Node Name
AIXLinuxSun Solaris Operating EnvironmentWindows  Enter the name of the WebSphere Application Server Admin Node in which to configure the WebSphere Commerce Payments application server. Enter this name carefully, otherwise the configuration will fail. The default node name is the WebSphere system host name.
iSeries See the OS400 Options panel.
Protocol Threads
Enter the number of protocol threads that should exist in the protocol thread pool for the payments cassette. The default number is 8.  Protocol threads are used to process server-side protocol specific messages within a cassette.
Service Threads
Enter the number of service threads to be started by WebSphere Commerce Payments. The default number is 6. Service threads are used to perform current or future tasks in the background.
Minimum Access Role
Select the minimum access role a user should have to be able to view sensitive data. The default minimum access role is clerk. If the role is set to clerk, all users can view the sensitive data. If the role is set to any other value, users below that role will see masked data (*****) in place of the actual sensitive data. A role of none means no one is allowed to see sensitive data. Sensitive data is determined by the payment cassette. For example, it might be the credit cardholder's card number, or the credit card expiration date. For information about what data is considered sensitive for IBM-provided payment cassettes, refer to the appropriate cassette supplement.
Socks Server Host
Enter the fully-qualified host name of your socks server. (This field is displayed only after the Payments instance has been created.)
Socks Server Port
Enter the port number that your socks server uses. (This field is displayed only after the Payments instance has been created.)
Site Admin ID
Enter the ID for the Site Administrator user. (This field is displayed only during instance creation.)