This topic describes how to install available Integration Server features on a base node.
Before you begin
If you encounter a problem such as not having enough temporary space or not having the right packages on your system, cancel the installation, make the required changes, and restart the installation.
The installation of new features uses the InstallShield for Multiplatforms (ISMP) wizard to perform the installation. You can use the Installation wizard or perform the installation from a command line, using the silent installation method.
Installation programs in WebSphere Application Server products
If you are adding features to the base product, see Installing additional features on a base Application Server.
This topic describes adding features to the Integration Server on a base node.
Why and when to perform this task
You can add features to the WebSphere Business Integration Server Foundation product on a stand-alone base node at any time, by running the Installation wizard for WebSphere Business Integration Server Foundation again.
If you are adding features to WebSphere Business Integration Server Foundation on a managed node, you cannot install certain deactivated features. The following Integration Server features are always hidden and deactivated on a federated base node:
Integration Server features that are not grayed out are available for installation on a managed base node. You do not have to unfederate the base node to add available Integration Server features.
If the managed node does not have both the administrative console feature and the administrative scripting features, the following Integration Server features are hidden and deactivated:
To install any of these deactivated features, you must remove the base node from the cell as described in the following procedure. See Installing deactivated Integration Server features on a base node for a procedure to install available features to the Integration Server on a stand-alone or managed node.
You do not have to remove a managed node from a cell to install available features. Use the following procedure to avoid component regression problems when installing available features to WebSphere Business Integration Server Foundation on a base node.
Steps for this task
You cannot install features correctly as a non-root user on a Linux or UNIX system, or as a non-administrator on a Windows system.
Corresponding entries in the response files exist for every prompt that is described as part of the wizard. Comments in the response file describe how to customize the options.
The rest of this procedure assumes that you are using the Installation wizard.
The Installation wizard does not support hot keys, such as Alt-N. You can tab to Next and press Enter to select it, for example.
The license
that the Installation wizard displays can contain characters that display
incorrectly in Japanese. For example, the section labeled Part 1 does
not show the number 1. These missing characters do not significantly
affect the content of the license agreement.
User ID to authenticate with the embedded messaging queue manager
This field is the JMS user ID who authenticates the connection to the JMS provider. This user ID must have administration rights for the messaging service.
The JMS user ID must be less than or equal to 12 characters.
You can create the user ID later and add the user to the mqm user group. Or specify the root user as the value for the field:
root
Password
Type the password for the user you specified as the JMS user ID in the first field.
Confirmation password
Repeat the password for the user you specified as the JMS user ID in the first field.
Security role for the business process system administrator
This field is the security role mapping. Specify the user or group from the domain user registry that is mapped onto the role of Business Process Administrator. The value to use depends on the local settings. For example, you can specify that the Administrator group is to perform the security role on some systems.
The user registry can be the local operating system, Lightweight Directory Access Protocol (LDAP), or custom registry. The user or group specified must already exist in the user registry being used.
See Using Process Choreographer for more information.
The Installation wizard starts the firststeps command.
See Recommended updates for WebSphere Application Server for information about downloading and installing updates. See Installing interim fixes, cumulative fixes, and fix packs for information about using the update installer program.
Results
You can successfully install available features for the Integration Server on a base node.