WSRR v7.5 Installation - What's all the Buzzz... It is supposed to be Silent
KailashPeri 120000MHKD Visits (4450)
Silently installing WebSphere Service Registry & Repository (WSRR) v7.5 - Part I
This is the first of three part blog that describes different installation scenarios of WSRR v7.5 silent installation.
• Part I - Installation of WSRR on a stand-alone WebSphere Application Server with a single Database for WSRR, Activity and Service Integration Bus (SIBus) databases.
• Part II - Installation of WSRR on a federated WebSphere Application Server with three separate databases for WSRR, Activity and SIBus
• Part III - Installation of WSRR on a WebSphere Application Server cluster
WSRR DVD Image Part Numbers
To install WSRR in a silent mode, you would need a command that reads a response file that contains the commands to install the product. A sample response file (tem
Template Response file - Demystified
The response file is an XML file that contains several elements and attributes. We will categorize these into 4 sections viz. Server, Installation Manager (IM), WebSphere Application Server (WSAS), WSRR & Business Space and Miscellaneous Properties.
The top section of the temp
The sample response file has a preference element the describes access to internet for repository updates. If the system you are installing WSRR does not have direct internet access, modify the following element
<preference value=”true” name= "com
and set value attribute to "false"
<preference value=”false” name= "com
Installation Manager Section
The above section specifies where IM will be installed. This is identified by the installLocation attribute (eg: C:/I
Note: Only one instance of IM can exist on a system. If you have an existing IM, ensure that installLocation, eclipseLocation and eclipseCache attributes are set to point to your existing IM installation directories. If the existing IM is an older version than the one supplied with the DVD, IM will be upgraded.
WebSphere Application Server, WSRR and Business Space
This portion of the response file contains directives to install WAS, WSRR and Business Space. On Line 56 in the above figure installLocation attribute indicates where WSAS, WSRR and BusinessSpace will be installed (eg: C:/I
The id value on Line 57 and profile value 71, 72 and 73 is the profile ID that IM uses to identify the WSAS installation. You could change the id to a name of your choice (one that does not exist already) as long as the ids on Line 56 and profile field (lines 71-74) have the same value. The profile ID is an IM profile id and should not be confused with WSAS profile (created with manageprofiles command).
This section contains miscellaneous properties and must not be modi
WSRR profile can be created using a response file with profile parameters and executing manageprofiles command with the response file.
During the installation process, WSRR generates a number of sample response files for creating profiles based on the database product of your choice. The sample response files are located in <WAS
As an example, we will use crea
Profile Response File – Internals
The response file directive ‘create’ specifies that a new profile is to be created with
• Profile Name - WSRRSA
• Profile Directory - WSRR Install Directory specified by installLocation (emp
• Profile Template Used - <WSRR Install dire
The above are the default settings for WAS administrator, JMS user and RunAs user ids. Please change them according to your organizational spec
Ensure that you configure the following variables to the appropriate values on your system
wsrrDbType - Database Type
wsrrDbLocation – Database installation dire
wsrrDbUserID / wsrrDbPassword – User Id / password to access the DB (userid must exist and should be less than 8 characters)
Once you configure the values, run the manageprofiles command
Please refer to the Installation and profile creation log files section in the information center for various logs generated during installation and profile creation.
Once the installation is completed, you would need to start the Application Server and log in to WSRR WebUI and load the configuration profiles. Stay tuned for more details.