Administer > Overview of administering a WebSphere Commerce site > Configuration Manager > Open Configuration Manager
Open Configuration Manager on an IBM i system
The Configuration Manager provides a graphical interface for configuring a WCS instance.
Configuration Manager consists of two components: a client component and a server component. The client component is a Graphical User Interface that is used to create or modify a WebSphere Commerce or WebSphere Commerce Payments instance. The client is installed on a Windows system as part of the Remote WebSphere Commerce Management utilities component from the WebSphere Commerce v184.108.40.206 Server Runtime DVD. The Windows system must be on the same network as the remote IBM i system.
The Configuration Manager server component runs on the remote IBM i system, which must have the licensed program for Java 5761-JV1 installed. The server component is installed as part of the WebSphere Commerce server runtime component on the remote IBM i system. The client and server components are able to communicate via RMI/IIOP protocol.
The default user ID for Configuration Manager is configadmin and the default password is the password that was specified when the product was installed on the IBM i system. For example, config1admin.
- Prepare the IBM i system to start the Configuration Manager server.
Option Description If modifying instance-specific properties using Configuration Manager, complete the following steps before starting the server.
- Log on to the IBM i system ensuring that the profile has a *SECOFR user class and is set up with the language specific settings for English or the desired default language for the instance.
- Start a Qshell session and switch to the WC_INSTALL/bin directory.
If creating a new instance, complete the following steps before starting the server.
- Start a Qshell session and change the current directory to the QIBM/ProdData/WebSphere/AppServer/V7/ND/bin directory.
- Run the command osgiCfgInit -all. When the command has completed, the $ prompt will return in the Qshell.
- Change the current directory to the WC_INSTALL/bin directory.
- Start the Configuration Manager server:
config_server.sh [-port server_port_number]
The -port parameter is optional. If you do not specify this parameter, the default port of 1099 is used. The Configuration Manager server will listen on this port number.
If the -port parameter is specified, the value must be between 1024 and 65535 and not currently in use on the IBM i system.
If you are using a system where your primary language is not the same as the language in which you are creating the instance, add the QSYSlanguage_feature_number library into the user profile's library list. Otherwise, the profile will try to locate it under QSYS.
To add the language feature library, use the EDTLIBL command.
If this is the first time that Configuration Manager is run on the system, we will see the following messages:
/QIBM/ProdData/CommerceServer70/lib/ConfigManager.jar /QIBM/ProdData/CommerceServer70/payments/wc.mpf.ear/lib/ibmjsse.jar /QIBM/ProdData/CommerceServer70/lib/Utilities.jar /QIBM/ProdData/CommerceServer70/lib/Enablement-BaseComponentsLogic.jar /QIBM/ProdData/CommerceServer70/lib/jtopen.jar /QIBM/ProdData/CommerceServer70/lib/xerces.jar /QIBM/ProdData/CommerceServer70/lib/sslite.zip
When you receive the following messages, proceed to the next step:
Registry created. CMServer bound in registry.
- Start the Configuration Manager client:
- Use a command prompt on the system on which the Configuration Manager client is installed, change to the Configuration Manager directory.
- Issue the following command:
configClient.bat -hostname IBM_i_host_name [-port server_port_number]
- The fully qualified host name of the server. Ensure the host name is entered in the same letter case as specified in the CHGTCODMN command.
- The port number on the IBM i server on which the Configuration Manager is listening. You only need to specify this value if the server is listening on a non-default port. The port parameter is optional but if it was specified in the config_server.sh command, it needs to be specified here.
- In the Configuration Authentication window, type the Configuration Manager user ID and password and click OK.