Administering InterChange Server Express may involve starting and shutting down the system and managing the startup parameters and database passwords. This section includes the following topics:
Steps for starting InterChange Server Express
Steps for customizing InterChange Server Express startup parameters
Steps for setting the InterChange Server Express mode for OS/400 and i5/OS
Shutting down InterChange Server Express
Changing the InterChange Server Express and database passwords
Perform the following steps to start InterChange Server Express:
At startup, InterChange Server Express reads the InterchangeSystem.cfg file and sets its properties according to the parameter values listed there. See the WebSphere Business Integration Server Express installation guide for Windows, for Linux, or for OS/400 and i5/OS for a list and description of the configuration parameters.
Perform the following steps to customize the InterChange Server Express startup parameters:
-start
-stop
-stat
The parameters in table Table 4 customize the startup of InterChange Server Express.
Parameter | Function |
---|---|
-c configFile | Name of the configuration file to be used during startup. The default is InterchangeSystem.cfg (not supported in Linux). |
-design | Specifies that the server is started in the design mode. |
-test | Specifies that the server is started in the test mode for Integrated Test Environment, which enables business object inspection in Integrated Test Environment. Usually combined with the -design option so that artifacts can be deployed individually without dependency constraints. |
-i | Allows InterChange Server Express to start up and ignore all error messages. |
-p password | Specifies the password to access InterChange Server Express. If you do not use this parameter, the start_server command uses the password in the InterchangeSystem.cfg file. Use with the -u parameter. |
-s serverName | Specifies the name of the InterChange Server
Express instance. The name is case-sensitive.
For Linux and Windows, this parameter is hard coded as WebSphereICS, and you must modify the start_server.bat or ics_manager script to change the server name. For OS/400 and i5/OS, the default name is QWBIDFT44, and you can create other instances. The serverName parameter is passed to start_server.sh from submit_ics_server.sh. Do not invoke start_server.sh directly, instead invoke submit_ics_server.sh, which requires serverName as a parameter. |
-u loginName | Specifies the user login name for InterChange Server Express. If you do not use this parameter, the start_server command uses the user login name in the InterchangeSystem.cfg file. Use with the -p parameter. |
-v | Displays the version of InterChange Server Express, then exits (not supported in Linux). |
Setting the server mode allows the server to be started in the set mode each time it is started, except when the mode parameter (design, production, testOn or testOff) is passed on the submit_ics_server.sh script.
Perform the following steps to set the server mode for OS/400 and i5/OS:
where:
Shutting down InterChange Server Express stops all running collaborations and connectors and InterChange Server Express itself. All connections to the database are closed and the machine's system resources used by InterChange Server Express are returned.
Perform the following steps to shut down the server gracefully:
On Linux you can also use the $./ics_manager -stopgraceful script to shut down InterChange Server Express gracefully.
On OS/400 and i5/OS, you can also use the stop_server_gracefully.sh
script to shut down InterChange Server Express gracefully. From
the command line, type the QSH command and from the QSHELL environment,
cd to /QIBM/Proddata/WBIServer44/bin and run stop_server_gracefully.sh serverName.
Optional parameters are -uUserName and -pPassword. If these are not specified, the default values are used.
If you want to specify values other than the defaults,
run the following:
stop_server_gracefully.sh serverName -uUserName -pPassword
Gracefully shutting down the system allows all currently processing and queued flows to complete before shutting down. This may take a long time because all flows waiting to be processed by a running collaboration must complete. Existing flows are processed by the collaborations, but no new flows are accepted.
If you want to gracefully shut down the system, the following occurs:
If the collaboration object is a member of a collaboration group, all collaboration objects in the group stop.
If messages from the connectors are in transit to the collaboration object when it stops, they remain in the messaging queues until the collaboration object starts.
Perform the following steps to shut down the server immediately:
On Linux you can also use the $./ics_manager -stop script to shut down InterChange Server Express immediately.
On OS/400 and i5/OS, you can also use the stop_server.sh script. From the command line, type the QSH command, and from the QSHELL environment, cd to /QIBM/Proddata/WBIServer44/bin and run stop_server.sh serverName with -uUserName and -pPassword. The -uUserName and -pPassword parameters are optional. If these are not specified, the default values are used.
Immediately stopping the system forces the system to shut down without processing any more flows. Running connectors and collaborations are stopped immediately. When the system is restarted, flows that were interrupted by the immediate shutdown are redelivered in the same processing order. If one of these flows wrote data to an application, when the flow is redelivered, it tries to duplicate the data and fails because the data already exists. If the collaboration processing the flow is transactional, a rollback occurs. If the flow is not transactional, it is moved to the resubmission queue. See Flow failures for more information on submitting a flow that fails to process.
Use this option when you need to quickly shut down the system. For example, you may want to reboot the system, but a collaboration has multiple events waiting to be processed. Shutting down gracefully may take too much time because the collaborations need to complete all existing work before stopping.
Password encryption provides a measure of security for protecting the IBM WebSphere Business Integration Server Express system and underlying databases from unauthorized user entry. The encrypted string for each of the passwords is stored in InterChange Server Express and is accessed by the server when the password must be decrypted. In the InterchangeSystem.cfg file, the encrypted password is placed in the PASSWORD*= parameter.
The InterChange Server Express administrator and database passwords are requested during system installation by Installer and are encrypted and stored when the system is rebooted at the completion of the installation. Thereafter, you can change the InterChange Server Express password or the database password in System Manager, only if RBAC-enabled. For more information on role-based access control, see Administering role-based access control (RBAC).
The InterChange Server Express user name and password are required during repository copy and restoration. See Using repos_copy.
For instructions on changing the password for InterChange Server Express or for the database(s), refer to the following sections:
Steps for changing the InterChange Server Express password
Steps for changing the database passwords
Perform the following steps to change the password for InterChange Server Express:
The encrypted password is stored in the InterchangeSystem.cfg file.
The repository database passwords can be changed through System Manager after the InterChange Server Express system is running.
Perform the following steps to change the database passwords:
A dialog box for changing the password appears.
A maximum of 30 characters is allowed.