config_server.sh command

This command starts the WebSphere Commerce Configuration Manager server. The Configuration Manager server must be started before starting the Configuration Manager client.

iSeries The config_server.sh command must be issued before issuing a createInstance.sh command.

This command is in the following path:

WC_installdir/bin

Command structure

Diagram of the command structure: the command starts with the fully qualified name of your WebSphere Commerce Server and the configuration path, followed by the command name, config_server.sh  and the ? character. End the command with a list of parameters in the form of name value pairs. Separate each name value pair with the & character. For a detailed description of the parameters and their values, refer to the list entitled Parameter values.

Parameter values

protocol
This is the protocol the Configuration Manager server and client will use when communicating. Valid values are SSL and default (non-SSL).

If you do not specify this parameter, the protocol value is set to default.

port
This is the port the Configuration Manager server and client will use to communicate. Valid port numbers are in the range 1024 - 65535.

If you do not specify this parameter, port 1099 is used.

initfile
This is the initialization file for the WebSphere Commerce Configuration Manager server. This file contains a list of all WebSphere Commerce and WebSphere Commerce Payments instances that currently exist.

If you do not specify this parameter, the following file is used:

AIXLinuxSun Solaris Operating EnvironmentWindowsWC_installdir/instances/wcs_instances
WC_userdir/instances/wcs_instances

Example

The following example starts the WebSphere Commerce Configuration Manager server with all default values, assuming you are already in the WC_installdir/bin directory:

AIXLinuxSun Solaris Operating Environment./config_server.sh
Windowsconfig_server

Behavior

This command starts the WebSphere Commerce Configuration Manager server

Exception conditions

None