Administer > Manage instances > WebSphere Commerce Payments instance > WebSphere Commerce Payments
Create a WebSphere Commerce Payments instance
The first step in migrating WebSphere Commerce Payments is to create a Payments instance.
Procedure
- If WebSphere Commerce and WebSphere Commerce Payments are on the same machine and you are not using IBM HTTP server.
- Verify if the web server plugin path to the WCS instance is set to the default Plugin installation directory. For example...
drive:/WebSphere/Plugins/config/webserver1/plugin-cfg.xml
- If it is, change the Web server plugin path to the WCS instance profile directory. For example...
C:/WebSphere/AppServer/profiles/instance/config/instance_cell/nodes/instance_node/servers/webserver1/plugin-cfg.xml
- Start Configuration Manager.
If WebSphere Commerce Payments is on a separate node from WebSphere Commerce, ensure that the Configuration Manager server on the WebSphere Commerce Payments node is started.
Important consideration for DBCS users
For IBM i, when creating an WebSphere Commerce Payments instance, start Configuration Manager using a user profile that has the required CCSID for the language in which you want the instance created. Valid CCSIDs are listed in Creating an OS/400 or i5/OS user profile.
For example, a WebSphere Commerce Payments instance might not be created with a CCSID of 5026 (CRTPYMMGR CCSID(5026)). You can create and run an instance on a system where the CCSID *SYSVAL is 5026.
Before creating a WebSphere Commerce Payments instance under a different WebSphere Application Server instance, stop and then restart the Configuration Manager server and client.
- Select...
WebSphere Commerce | hostname | Payments Instance List (right-click) | Create Payments InstanceThe length of the WebSphere Commerce or Payments instance name you enter cannot be greater than 10 characters long and cannot include the following characters: / \ " | < > ? * : &
The length of the Payments instance name you enter into WCIM cannot be greater than 12 characters long, and cannot include the following characters: / \ " | < > ? * : &
- Complete the Payments instance creation wizard information.
- When completing the wizard, ensure that the value you enter in the Site Admin ID field is the WebSphere Commerce Site Administrator ID.
- On the WCSRealm page, ensure that you enter the fully qualified host name for the WebSphere Commerce Web server in the Commerce Web server Hostname field.
If you are using a separate Web server for WebSphere Commerce Payments, ensure that you do not enter the host name of the Web server you are using for WebSphere Commerce Payments, enter the name of the Web server for WebSphere Commerce.
- When you have completed all the necessary information in all the panels, the Finish button is enabled.
Click Finish to create the WebSphere Commerce Payments instance.
- You are prompted for the following information:
- You are asked to populate the Oracle database. Select Yes if you want the database to be populated, or No if you do not want the database to be populated.
- If you choose to use an existing DB2 database, you are asked to populate the database.
Select Yes if you want the database to be populated, or No if you do not want the database to be populated.
- The time required to create an instance depends on the speed of the system. The progress bar that displays when you start creating the instance will indicate when the process has finished.
- When instance creation is complete, a dialog box appears containing a summary. Click OK to close the dialog box. Ensure that you review contents of the dialog. It might contain additional instructions.
- Exit Configuration Manager by clicking on Console and Exit.
- Verify the creation of the WebSphere Commerce Payments instance.
The configuration information for the new WebSphere Commerce Payments instance is stored in the following file. Confirm that this file exists before checking the log files produced during instance creation.
The log files are in...
WC_INSTALL/logs/Configurator.1.log
WC_USER/logs/Configurator.1.log
WC_USER/logs/WCSconfig.log
- Continue by following the instructions in the Mandatory post-instance creation tasks. Complete the following instructions for WebSphere Commerce and WebSphere Commerce Payments to function correctly.
- Configure the WCS instance to connect to Payment instance
- Open Configuration Manager.
- Select...
WebSphere Commerce | hostname | Commerce | Instance List | instance | Instance Properties | Payments
- Make sure that the value filled in for the "Web server Hostname" field is the fully qualified hostname of the machine where WebSphere Commerce Payments is installed. If it is not, then update it. Complete any other necessary fields and click Apply. For help on completing the fields, click Help.
See also
- Configure cassettes
In this step you authorize cassettes and create WebSphere Commerce Payments users and accounts,
- Modify a WebSphere Commerce Payments instance
- Configure WebSphere Commerce to connect to the Payment Manager
You can manually configure the WCS instance to connect to the Payment Manager server using the compatible payment model.
- Create multiple WebSphere Commerce Payments instances
If you are using WebSphere Commerce Payments to process payments in WebSphere Commerce, each instance of WebSphere Commerce requires its own instance of WebSphere Commerce Payments. For every new WCS instance you create, also create a new WebSphere Commerce Payments instance.
- Ensure that WebSphere Commerce Payments is started
To ensure that WebSphere Commerce Payments is started:
- Federate WebSphere Commerce Payments
- Delete a WebSphere Commerce Payments instance
You can delete a WebSphere Commerce Payments instance.
- Use Internet Information Services (IIS) Manager Web server with WebSphere Commerce Payments