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 WebSphere Commerce instance you create, you must also create a
WebSphere Commerce Payments instance.
While it is possible
to create multiple instances in any configuration of WebSphere Commerce
components, the assumption is as follows:
- A WebSphere Commerce instance and its associated WebSphere Commerce
Payments instance exist on the same node. Multiple WebSphere Commerce
instances using remote WebSphere Commerce Payments instances is not
supported.
- The Web server and database server exist on the same node as WebSphere
Commerce and WebSphere Commerce Payments.
- You have an existing WebSphere Commerce instance.
- You have an existing WebSphere Commerce Payments instance.
Before you begin
Ensure that the node meets the following requirements:
- If you are using the minimum required amount of system memory,
increase the system memory by 512 MB for each additional WebSphere
Commerce instance and its associated WebSphere Commerce Payments instance
on a system.
- For each additional WebSphere Commerce instance and its associated
WebSphere Commerce Payments instance on a system, increase the system
virtual storage by 1 GB.
- If you are using Oracle Database with WebSphere
Commerce, each additional WebSphere Commerce instance and its associated
WebSphere Commerce Payments instance require a data file. The table
spaces and Oracle Database IDs required by WebSphere Commerce and
WebSphere Commerce Payments can be created for you when you create
the instances.
- Each WebSphere Commerce instance must have its own host name.
This host name is also used by the associated WebSphere Commerce Payments
instance.
- Each host name for each instance requires its own IP address.
The IP address must be valid on the network, with associated host
names in the DNS server. The IP address must also be on the same VLAN
as the IP address of the original instance.
-
Notes:
- You can also use the IP address and host name of the node for
one of the instances. In this case, you need just two IP addresses
for two instances.
- Each set of WebSphere Commerce and WebSphere Commerce Payments
instances requires its own host name.
- The host name for each instance must resolve fully to separate
IP addresses. To verify that you can run Configuration Manager and
create multiple instances, run the nslookup command
on both the host name and IP address for each instance. Ensure that
the host name resolves to its correct IP address. Ensure that the
IP address resolves to its correct host name:
nslookup 'host1.domain' nslookup 'xxx.xxx.xxx.xxx' nslookup 'host2.domain' nslookup 'yyy.yyy.yyy.yyy'
- Web server prerequisites
If you are using IBM HTTP Server, you
can skip this section.
If you are using Microsoft IIS or Sun
Java System Web Server, you must do the following steps:
About this task
These instructions describe how to create an additional
WebSphere Commerce Payments instance.
These variables represent
the parameter values for your first and second instance and are intended
to show where values are unique or common between instances.
Normally,
you have operational existing WebSphere Commerce and WebSphere Commerce
Payments instances and you want to create an additional instance or
instances. If you have an existing instance, you do not have to modify
any of the parameter values for that instance to add an additional instance.
You might want to modify some parameters of your original instance
in order to better organize your multi-instance environment.
Procedure
- Create a Web server associated with the new virtual host
name and new IP address. See the Web server documentation for instructions.
- Depending on your Web server:
Option | Description |
---|
Microsoft IIS |
Configure the Web server. |
Sun Java System Web Server |
Configure the Web server. |
- Before continuing, ensure that the following URLs work:
Original instance |
New instance |
http://host1.domain |
http://host2.domain |
http://host1.domain:5432 |
http://host2.domain:5432 |
https://host1.domain |
https://host2.domain |
https://host1.domain:5433 |
https://host2.domain:5433 |
https://host1.domain:8000 |
https://host2.domain:8000 |
https://host1.domain:8002 |
https://host2.domain:8002 |
https://host1.domain:8004 |
https://host2.domain:8004 |
https://host1.domain:8006 |
https://host2.domain:8006 |
- Creating multiple WebSphere Commerce Payments instances
If you have created your first WebSphere Commerce Payments
instance, create each additional instance that you require by following
the instructions in Creating a WebSphere
Commerce Payments instance. In the following table, the existing
instance is represented by Original instance and the new instance
is represented by New instance. You do not have to modify the values
for an existing instance.
Important: You cannot create
multiple WebSphere Commerce Payments instances in the same Configuration
Manager session. Restart Configuration Manager before you create another
WebSphere Commerce Payments instance.
The following table
lists the modified default values for the new instance. Replace these
values with the actual values that you want to use for your instance.
Field in Configuration Manager |
Original instance |
New instance |
Instance - Instance name |
Payments_instance_1 |
Payments_instance_2 |
WebSphere Node Name |
host_name |
host_name This should be the same host name as the original
WebSphere Commerce Payments instance. |
Database - Database name |
Payments_db1 |
Payments_db2 |
Database - Datafile name |
Oracle_datafile1 |
Oracle_datafile2 |
Database - Database user ID |
Oracle_user1 |
Oracle_user2 |
Database - Tablespace name |
Payments_instance_1TBLSPC |
Payments_instance_2TBLSPC |
Web server - host name |
host1.domain |
host2.domain |
WebSphere Commerce - host name |
host1.domain |
host2.domain |
Web server - Primary Document Root (IBM HTTP Server) |
HTTP_installdir/htdocs1 |
HTTP_installdir/htdocs2 |
Web server - Primary Document Root (Sun Java System Web Server) |
SunONEweb_installdir/docs1 |
SunONEweb_installdir/docs2 |
Web server - Primary Document Root (Microsoft IIS) |
C:\WINNT\System32\inetsrv\ iisadmin\htmldocs1 |
C:\WINNT\System32\inetsrv\ iisadmin\htmldocs2 |
Ensure that you verify the instance creation. by following
the instructions in Verifying
the instance creation.
After verifying the additional
WebSphere Commerce Payments instances, test the instances.
- Testing multiple instances
- Start all WebSphere Commerce Payments instances.
- Test the following URLs:
Original instance |
New instance |
http://host1.domain |
http://host2.domain |
http://host1.domain:5432/webapp/ PaymentManager |
http://host2.domain:5432/webapp/ PaymentManager |
https://host1.domain |
https://host2.domain |
https://host1.domain:5433/webapp/ PaymentManager |
https://host2.domain:5433/webapp/ PaymentManager |
https://host1.domain:8000/accelerator |
https://host2.domain:8000/accelerator |
https://host1.domain:8002/adminconsole |
https://host2.domain:8002/adminconsole |
https://host1.domain:8004/ orgadminconsole |
https://host2.domain:8004/ orgadminconsole |
- Installing the WebSphere Application Server Web server
plug-in on a remote machine
To
configure your remote Web server to communicate with your WebSphere
Commerce machine, you must install the WebSphere Application Server
Web server plug-ins.
- Verifying the instance creation
Confirm that this file exists before checking
the log files produced during instance creation.
Creating a
WebSphere Commerce Payments instance produces log files in the following
directory: WC_installdir\instances\payments_instance_name\logs
Where
payments_instance_name is the name of WebSphere Commerce Payments
instance.
Creating a WebSphere Commerce Payments instance produces
the following log files:
- createdb.log
- createdb.err.log
Creating a WebSphere Commerce Payments instance produces the
following files in the following directory:
- WC_installdir/logs
- WC_userdir/logs
- Configurator.1.log This log file is required
by IBM support if there is problem with the Payments instance creation.
- WCSconfig.log