Deprecated feature

Federating WebSphere Commerce Payments

Procedure

If you have not already installed the WebSphere Application Server Network Deployment product on a separate machine from the machines on which you installed WebSphere Commerce, WebSphere Commerce Payments, the database, and the Web server, do so now. Only one system hosts the deployment manager. As it federates application servers, it expands the cell that it manages. Although you can install other application servers on the same machine as the deployment manager, it is not generally done unless you have a machine with the capacity to host both products. The deployment manager is the central administrative manager.
On the WebSphere Application Server Network Deployment machine, start the deployment manager profile.
Note: Record the SOAP port number that is defined when creating your deployment manager profile.
Create the WebSphere Application Server non-root user and group if they do not already exist on the WebSphere Commerce Payments node.
To prevent problems in the next step, update addNode.sh by completing the following instructions:
1. Log on to the WebSphere Commerce Payments node as root.
2. Open the following file in a text editor:
  - WAS_installdir/bin/addNode.sh
  - WAS_installdir/bin/addNode.bat
3. In the text file, find the following line of text:
```
"$JAVA_HOME"/bin/java \ 
```
4. Insert the following line of text below the "$JAVA_HOME"/bin/java \ line of text:
```
-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. Save the changes and exit the text editor.
Log on to the WebSphere Application Server Network Deployment Administration Console.
Expand System Administration > Deployment Manager > Java and Process Management > Process Definition > Java Virtual Machine.
Change the Maximum Heap Size value to the maximum value supported by your operating system.
Note: You can reduce this number once you have completed the federation process.
Restart the Deployment Manager.
Before federating the WebSphere Commerce Payments application server node into the deployment manager cell, you must increase the SOAP connection timeout to 6000. To adjust the SOAP timeout setting complete the following steps on the WebSphere Commerce Payments node:
1. Open the following file in a text editor:
```
WAS_WC_profiledir/properties/soap.client.props
```
2. Search for the com.ibm.SOAP.requestTimeout entry, and set the value to 6000. For example, com.ibm.SOAP.requestTimeout=6000.
  Note: For more information, see WebSphere Application Server Best Practices.
3. Save the file, and exit.
Ensure that the system clock on your WebSphere Commerce Payments node and your WebSphere Application Server Network Deployment node are synchronized within 5 minutes of each other. If they are not, federation will fail.
On the WebSphere Commerce Payments node:
1. Log on as the non-root user.
2. Federate the WebSphere Commerce Payments application server into the deployment manager cell by issuing the following command:
```
 WCP_profiledir/bin/addNode.bat deployment_manager_host_name SOAP_port -includeapps
```
```
 WCP_profiledir/bin/addNode.sh deployment_manager_host_name SOAP_port -includeapps
```
```
 WCP_profiledir/bin/addNode deployment_manager_host_name SOAP_port -includeapps
```
  Note: Your WebSphere Commerce Payments instance is stopped automatically during the federation process.
  
  The command is shown on multiple lines for display purposes only, enter the command on one line.
  
  The variables and parameters in the command are defined as follows:
  
  WCP_profiledir
  
  This directory is created for the WebSphere Application Server profile that is used by a WebSphere Commerce Payments instance.
  
  deployment_manager_host_name
  
  This is the fully-qualified host name of the deployment manager node.
  
  SOAP_port
  
  This is the SOAP port on which the deployment manager listens. This port number is defined when creating the deployment manager profile. The default deployment manager port is 8879.
  
  -includeapps
  
  When federating a WebSphere Commerce Payments profile that contains a WebSphere Commerce Payments instance, you must include this parameter to ensure that the WebSphere Commerce Payments application (EAR) file is transferred to the new configuration.
3. After federating a Payment profile, the node agent must be managed by the non-root user. For more information, see the following topics:
  - WebSphere Application Server Best Practices.
  - Running an Application Server and node agent from a non-root user
You must reset the SOAP connection timeout to the original value. To adjust the SOAP timeout setting complete the following steps on the WebSphere Commerce node:
1. Open the following file in a text editor:
```
WC_profiledir/properties/soap.client.props
```
2. Search for the com.ibm.SOAP.requestTimeout entry. Reset the entry to the original value. For more information, refer to:
  - WebSphere Application Server Best Practices
3. Save the file, and exit.
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:
```
WC70_Installdir/payments/bin/createPaymentsVirtualHost.sh payments_instance_name
```
  Where, payments_instance_name is the name of the WebSphere Commerce Payments instance
Regenerate Plugin-cfg.xml for updated Payments web server configuration.
1. Log on to the WebSphere Application Server Network Deployment Administration Console.
2. Expand Servers > WebServer, and select webserver1(WPM_wpm_node), click Generate Plug-in button to generate plugin_cfg.xml for payment webserver1.
Copy the updated plugin-cfg.xml file to your Web server machine. For more information, refer to:
- Communicating with Web servers
Update the path to the plugin-cfg.xml file in the Web server configuration file on the WebSphere Commerce Payments node.
Restart your Web server.