Administer > Manage instances > WebSphere Commerce Payments instance > WebSphere Commerce Payments > Create 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.

This task details a configuration which is an option to using the WCPayments Plug-in to connect to the Payment Manager.

Procedure

1. Configure the commerce server. Open the WebSphere Commerce configuration file, and find the "PaymentManager" element. Set the properties to the correct values.

   <PaymentManager 
      DTDPath="config/payment/dtd/IBMPaymentServer.dtd" 
      Hostname="vim.cn.ibm.com" 
      PMAdminId="wcsadmin" 
      ProfilePath="config/payment" 
      UseExternalPM="false" 
      UseNonSSLPMClient="0"
      UsePayment="false"
      UseRemote="false"
      UseSocksServer="false" 
      WebPath="/webapp/PaymentManager" 
      WebServerPort="5433" 
      name="Payments"/>
   

   Set the correct values for the following parameters.

   Hostname

   The fully qualified host name or IP address for the WebSphere Commerce Payments Web server.

   PMAdminId

   The registered administrator user for the WebSphere Commerce Server.

   UseExternalPM

   Set this to true.

   UseNonSSLPMClient

   This parameter indicates whether SSL is used for the Payment Manager Web server. Refer to the value of the UseSSL attribute of the PMWebServer element in the WebSphere Commerce Payments configuration file for the payment instance. If the UseSSL attribute value is "true", set this value to 0, else set the value as 1.

   The WebSphere Commerce Payments Configuration file can be found...

   • WC_INSTALL/instances/instance/xml/instance.xml

   • WC_INSTALL\instances\instance\xml\instance.xml

   • WC_USER/instances/instance/xml/instance.xml

   UseSocksServer

   This parameter indicates if a socks server is used. If the instance uses a socks server, set it to "true", otherwise, set it to "false".

   SocksHostname

   The host name of the socks server. This is required when UseSocksServer is set to "true".

   SocksPort

   The port name of the socks server. This is required when UseSocksServer is set to "true".

   WebServerPort

   The Web server port for of the payment manager. Refer to the "PMWebServer" element in the WebSphere Commerce Payments configuration file for payment instance. If "UseNonSSLPMClient" is 0(UseSSL="true"), the value should be the same as the "SSLPort" in "PMWebServer". If "UseNonSSLPMClient" is 1(UseSSL="false"), the value should be the same as "ServerPort" in "PMWebServer". The default values Out of box, the "SSLPort" is 5433, and the "ServerPort" is 5432.

   <PMWebServer RemoteWS="false"
   .
   .
   .
      ServerPort="5432"
      UseSSL="true"
      SSLPort="5433"
   .
   .
   .
   />  
   

   PaymentsEnabled

   This parameter indicates if payment manager is used for payment process. A value of "true" indicates that payment manager is used, while "false" indicates that payment manager is not used. If not specified, the default value is "true". Ensure that it is not set to "false", or else you cannot connect to the payment manager.

2. Configure the WCSRealm of the payment instance.

   1. Open the Configuration Manager.

   2. Select the payment instance.

   3. Navigate to the WCSRealm panel.

   4. Set the WC Hostname as the host name of the WebSphere Commerce instance. For the "Use Non-SSL WC Client" check box and the Web server port, refer to the following snippet in the Web server configuration file of the commerce instance. Open the Web server configuration file of the commerce instance in the following location:

      • WC_INSTALL/instances/instance/httpconf/httpd.conf

      • WC_INSTALL\instances\instance\httpconf\httpd.conf

      • WC_USER/instances/instance/httpconf/httpd.conf

      If SSL is used, find the "VirtualHost" element which specifies "SSLEngine On" in the Web server configuration file. You can find the port for SSL in this virtual host configuration. In this case, the "Use Non-SSL WC Client" check box in the WCSRealm panel should not be selected. If SSL is not used, the "Use Non-SSL WC Client" check box should be selected. Here is a snippet from the httpd.conf file on i5/OS.

      <VirtualHost host_name:80>    ServerName host_name
         Alias /wcsstore  "/QIBM/UserData/WebSphere/AppServer/V6/Base/profiles/profile_name/installedApps/cell_name/WC_instance.ear/Stores.war"     
         Alias /wcs       "/QIBM/UserData/WebSphere/AppServer/V6/Base/profiles/profile_name/installedApps/cell_name/WC_instance.ear/CommerceAccelerator.war" 
      </VirtualHost> 
      <VirtualHost host_name:443>    
         SSLEngine On
         SSLClientAuth 0
         ServerName host_name    
         Alias /wcsstore  "/QIBM/UserData/WebSphere/AppServer/V6/Base/profiles/profile_name/installedApps/cell_name/WC_instance.ear/Stores.war"    
         Alias /wcs       "/QIBM/UserData/WebSphere/AppServer/V6/Base/profiles/profile_name/installedApps/cell_name/WC_instance.ear/CommerceAccelerator.war" 
      </VirtualHost>
      

3. Configure the Policy for cassettes. Refer to Create a payment policy to create a policy for compatible payment.

+

Search Tips   |   Advanced Search