Administer > Manage instances > WebSphere Commerce Payments instance > WebSphere Commerce Payments > Create a WebSphere Commerce Payments instance

Federating WebSphere Commerce Payments

Procedure

1. Install WAS ND product on a separate machine from the machines on which you installed WebSphere Commerce, WebSphere Commerce Payments, the database, and the Web server.

   You can install other application servers on the same machine as the deployment manager if the dmgr machine has the capacity.

2. On the WAS ND machine, start the deployment manager profile.

   Record the SOAP port number that is defined when creating the deployment manager profile.

3. Create the WebSphere Application Server non-root user and group on the WebSphere Commerce Payments node.

4. Update addNode.sh...

   1. Log on to the WebSphere Commerce Payments node as root.

   2. Edit...
      WAS_HOME/bin/addNode.sh

   3. In the text file, find the following line of text:

      "$JAVA_HOME"/bin/java \

   4. Append the following line...

      -Xms256m -Xmxmax_allowedm \

      Where, max_allowed is the maximum value allowable by your operating system. This value must be a multiple of 1024. Append the letter k or K to indicate kilobytes, or m or M to indicate megabytes.

5. Log on to the WAS ND Administration Console.

6. Change the Maximum Heap Size value to the maximum value supported by the operating system.

   System Administration | Deployment Manager | Java and Process Management | Process Definition | Java Virtual Machine

7. On the Payments node, increase the SOAP connection timeout to 6000.

   Edit...

   WAS_WC_PROFILE/properties/soap.client.props

   ...and set...

   com.ibm.SOAP.requestTimeout=6000

8. Restart the Deployment Manager.

9. Verify the system clock on the payments node and the WAS ND node are synchronized within 5 minutes of each other.

10. On the WebSphere Commerce Payments node:

    1. Log on as the non-root user.

    2. Federate the WebSphere Commerce Payments application...

       WCP_profiledir/bin/addNode.bat dmgr_host SOAP_port -includeapps

       WCP_profiledir	Directory created for the WAS profile used by a WebSphere Commerce Payments instance
       dmgr_host	Fully-qualified host name of the deployment manager node.
       SOAP_port	SOAP port on which the deployment manager listens. Default: 8879.
       -includeapps	When federating a Payments profile that contains a Payments instance, include this parameter to ensure that the Payments EAR file is transferred to the new configuration.

       The WebSphere Commerce Payments instance is stopped automatically during the federation process.

    After federating a Payment profile, the node agent must be managed by the non-root user.

11. Reset the SOAP connection timeout to the original value.

12. Re-create the virtual hosts required by the WebSphere Commerce Payments application server.

    1. Login to WebSphere Commerce Payments Node as non-root user.

    2. Run the following command:

       WC60_Install/payments/bin/createPaymentsVirtualHost.sh payments_instance

       Where, payments_instance is the name of the WebSphere Commerce Payments instance

13. Regenerate Plugin-cfg.xml for updated Payments web server configuration.

    1. Log on to the WAS ND Administration Console.

    2. Generate plugin_cfg.xml for payment webserver1...

       Servers |WebServer | webserver1 (WPM_wpm_node) | Generate Plug-in

    3. Copy the updated plugin-cfg.xml file to the Web server machine

    4. Update the path to the plugin-cfg.xml file in the Web server configuration file on the WebSphere Commerce Payments node.

    5. Restart the Web server.

    
    

    +

    Search Tips   |   Advanced Search