The Configuration Manager provides a graphical interface for configuring a
WebSphere Commerce instance.
Before you begin
If you are modifying an existing WebSphere Commerce instance, ensure that
the WebSphere Application Server management server (for example, server1 or dmgr) is started
successfully. Ensure that it is running before you modify instance-specific properties in Configuration Manager. For more information about starting the server, see Starting and stopping WebSphere Commerce.
Procedure
-
Start the Configuration Manager server by completing the following steps:
-
Log in as root.
-
Open a terminal window.
-
Issue the following command:
xhost + host_name
where
host_name is the fully qualified domain name of the system on which you want to
run the
Configuration Manager.
Note: When you start the Configuration Manager over an
X-client such as Exceed, the xhost command must be issued from the console
terminal, while the other commands are issued from a terminal session in the X-client. When you use
an X-client, host_name is the fully-qualified domain name of the X-client
system.
-
Issue the following command:
su - wasuser_ID
where
wasuser_ID is the non-root user ID created before you installed
WebSphere Commerce. The default
WebSphere Application Server user name is
wasuser.
-
Issue the following commands:
export DISPLAY=host_name:displayNumber.screenNumber
cd WC_installdir/bin
./config_server.sh
where
- host_name is the fully qualified domain name of the system on which you want
to run the Configuration Manager.
- displayNumber.screenNumber is the number on the top of
your terminal window. Your terminal might contain a displayNumber only.
For example, if your terminal shows both a
displayNumber and
screenNumber such as
0.0, then issue a command similar to the
following
export DISPLAY=myhostname:0.0
If your terminal shows a single digit such as
1, then issue a command similar to
the following
export DISPLAY=myhostname:1
Notes:
- To ensure that the Configuration Manager server and Client are secure, you can use the
-protocol SSL command line option.
- Do not close the terminal window where you entered the config_server.sh
command or the Configuration Manager server stops.
- Do not run the Configuration Manager server as a background process - this is a
potential security risk.
- Do not leave the Configuration Manager server running unless there is a client connected
- this a potential security risk.
-
Start the Configuration Manager client by completing the following tasks:
-
Open another terminal window.
-
Issue the following command:
xhost + host_name
where
host_name is the fully qualified domain name of the system on which you want to
run the
Configuration Manager.
-
Issue the following command:
su - wasuser_ID
where
wasuser_ID is the non-root user ID created before you installed
WebSphere Commerce. The default
WebSphere Application Server user name is
wasuser.
-
Issue the following commands:
export DISPLAY=host_name:displayNumber.screenNumber
cd WC_installdir/bin
./config_client.sh[-protocol SSL]
where
- host_name is the fully qualified domain name of the system on which you want
to run the Configuration Manager.
- displayNumber.screenNumber is the number on the top of
your terminal window. Your terminal might contain a displayNumber only.
Note: To ensure that the Configuration Manager server and client are secure, you can
use the [-protocol SSL]
command line option. If this the [-protocol
SSL]
option is used, both the client and the server must use it.
-
In the Configuration Authentication window, enter the Configuration Manager user ID and
password and click OK.