The responsefile.pcaw.esb.managedProfile.txt file is a sample response file for creating a custom profile. Use the addNode command to federate the custom node into a deployment manager cell to make the node operational. Because of this strong dependency on being a managed node, the profile is often referred to as a managed profile.
Create a custom node using the with an options response file after logging on as root on a Linux® or UNIX® platform, or as a user that belongs to the administrator group on a Windows® platform. Some steps of the installation procedure on a Windows platform require the user to belong to the administrator group and to have the advanced user rights Act as part of the operating system and Log on as a service.
The installation program reads this file to determine the characteristics of a deployment manager profile when you install silently. You can also create additional deployment manager profiles by using this response file after initial installation. The response file is shipped with default values.
Set this value to true if the deployment manager is not running or is not accessible for any of the reasons in the following description of federation.
Specify a value that resolves to the system where the deployment manager is running. Refer to Naming considerations for profiles, nodes, hosts, and cells for more information about host naming.
Specify the value of the deployment manager SOAP port. You must specify the correct value. An incorrect value prevents node federation and results in a total failure with an INSTCONFFAILED indicator. The default SOAP port for the deployment manager is 8879.
Do you federate the node during or after profile creation?
If you try to federate a custom node when the deployment manager is not running or is not available for other reasons, profile creation will fail and the resulting custom profile will be unusable. You must then move this custom profile directory out of the profile repository (by default, the profiles directory in install_root, where install_root is the WebSphere ESB installation directory) before creating another custom profile with the same profile name.
A problem occurs when the -silent option exists in the file. The file works with the option during a direct call to the profile creation wizard, but fails when called from a silent product installation. See Customizing the options response file for information about creating a profile silently during a silent product installation.
The option is unnecessary. Avoid using the option to avoid problems.
The example options response files are in two locations.
Location:
Product disc location | Installed location |
---|---|
/ESB directory | install_root/bin/ProfileCreator directory |
Use the file on the product disc to install WebSphere ESB silently and create a profile.
After installing WebSphere ESB, you can use the installed response file with the -options parameter on the Profile creation wizard command.
The sample options response file, responsefile.esb.txt, controls the first part of the installation and can also start the second part of the installation. To create a profile as part of installing the core product files, use the option in the responsefile.esb.txt file that identifies the response file for creating a profile. The profile response file lets you use the Profile creation wizard silently.
To create a: | Copy the following response file: |
---|---|
Deployment manager profile | responsefile.pcaw.esb.dmgrProfile.txt |
Custom profile | responsefile.pcaw.esb.managedProfile.txt |
Application server profile | responsefile.pcaw.esb.standAloneProfile.txt |
-W pcawresponsefilelocationqueryactionInstallWizardBean.fileLocation= "/opt/IBM/WebSphere/MyOptionFiles/customProfile.txt"
install -options "myresponsefile.txt" -silent
When the core product files exist, create a profile at any time using the Profile creation wizard. Start the wizard from the First steps console or directly using the Profile creation wizard command.
To create a profile for a: | Copy the following response file: |
---|---|
Deployment manager | responsefile.pcaw.esb.dmgrProfile.txt |
Managed node | responsefile.pcaw.esb.managedProfile.txt |
Stand-alone application server | responsefile.pcaw.esb.standAloneProfile.txt |
For example, copy the file as my_options_file.txt
Refer to Naming considerations for profiles, nodes, hosts, and cells for information about naming considerations.