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.
Of course, until you federate the node into a cell, the node is not managed. Another thing to keep in mind is that any federated node is a managed node, including federated nodes within Application Server profiles.
The following response file refers to the term managed instead of the term custom in many directive names. Even so, all of the directives in this response file help to define a custom profile.
################################################################################ # # Response file for WebSphere ESB custom profile creation # # This options file is located in the CD_ROOT\ESB\ directory and in the # install_root\bin\ProfileCreator_wbi directory. # # To use the options file under CD_ROOT\ESB\ directory, follow the instructions # in CD_ROOT\ESB\responsefile.esb.txt. The WebSphere ESB # installer locates this file during silent installation # and automatically runs the silent profile creation at the end of installation. # # To use the options file under install_root\bin\ProfileCreator_wbi for silent profile # creation, you must change various values in the file and use the following command # line arguments: # # -options "responsefile.pcaw.esb.managedProfile.txt" -silent # ################################################################################ ################################################################################ # # Profile name # # Set the name for this custom profile. The profile name must be unique for this # WebSphere ESB installation. # # -W profilenamepanelInstallWizardBean.profileName="profileManaged" ################################################################################ # If you want to set this profile to be your default profile, set to "true". # Otherwise set to "false". If this is the first profile being created, the profile # automatically is the default. # -W profilenamepanelInstallWizardBean.isDefault="false" ################################################################################ # # Profile location # # Specify a directory to contain the files that define the run-time environment, # such as commands,configuration files, and log files. If the specified directory # already exists it must be empty. If the directory name contains # spaces, enclose it in double-quotes as shown in the Windows example below. # # Note that spaces in the install location is only supported on Windows # operating systems. # # Default Install Location: # # -P installLocation="<ESB_HOME>\profiles\<PROFILE_NAME>" # -P installLocation="C:\Program Files\IBM\WebSphere\ESB\profiles\profileManaged" ################################################################################ # # Node name # # Please select the node name for the Application Server. Node name under one cell # has to be unique. # # Replace YOUR_NODE_NAME with the actual node name. # -W nodehostnamepanelInstallWizardBean.nodeName="YOUR_NODE_NAME" ################################################################################ # # Host name # # Specify the host name for the Application Server. The host name is the domain # name system (DNS) name (short or long) or the IP address of this computer. # # Replace YOUR_HOST_NAME with the actual host name. Comment the line to use # the default value. # -W nodehostnamepanelInstallWizardBean.hostName="YOUR_HOST_NAME" ################################################################################ # # Cell name # # You should not Modify this, unless absolutely necessary # # The Wizard would set this to short local host name + "Node##Cell" by default. # # If you would like to override the resolved cell name value, uncomment the line and # replace YOUR_CELL_NAME with <YOUR_OWN_VALUE> # # -W setnondmgrcellnameinglobalconstantsInstallWizardBean.value="YOUR_CELL_NAME" ################################################################################ # # Ports value assignment # # The following entries are used to reset port numbers used in the configuration # # They are currently set to the defaults. # Please check to make sure there are no port conflicts. # Port nubmers for each profile can be find in: # <profile>/config/cells/<cell name>/nodes/<node name>/serverindex.xml # # If you specify true for the value of # the -W pctfederationpanelInstallWizardBean.federateLater # directive, port numbers are assigned automatically when you federate the # node with the addNode command. The following port numbers do not apply. # -W pctmanagedprofileportspanelInstallWizardBean.BOOTSTRAP_ADDRESS="2809" -W pctmanagedprofileportspanelInstallWizardBean.SOAP_CONNECTOR_ADDRESS="8878" -W pctmanagedprofileportspanelInstallWizardBean.SAS_SSL_SERVERAUTH_LISTENER_ADDRESS="9901" -W pctmanagedprofileportspanelInstallWizardBean.CSIV2_SSL_SERVERAUTH_LISTENER_ADDRESS="9201" -W pctmanagedprofileportspanelInstallWizardBean.CSIV2_SSL_MUTUALAUTH_LISTENER_ADDRESS="9202" -W pctmanagedprofileportspanelInstallWizardBean.ORB_LISTENER_ADDRESS="9100" -W pctmanagedprofileportspanelInstallWizardBean.NODE_DISCOVERY_ADDRESS="7272" -W pctmanagedprofileportspanelInstallWizardBean.NODE_MULTICAST_DISCOVERY_ADDRESS="5000" -W pctmanagedprofileportspanelInstallWizardBean.NODE_IPV6_MULTICAST_DISCOVERY_ADDRESS="5001" -W pctmanagedprofileportspanelInstallWizardBean.DCS_UNICAST_ADDRESS="9353" ################################################################################ # # Federation # # A custom profile contains an empty node that must be federated to a deployment # manager to become a functional managed node. Identify a running deployment # manager that will administer the node or choose to federate the node later # using the addNode command. # # Set to "true" if you want to federate this custom node later using the addNode # command. You must federate this node later if the deployment manager : # - is not running. # - has security enabled. # - has the SOAP connector disabled # # If you want to federate it now, set to "" and fill in the entries for the host # and port of the deployment manager. # -W pctfederationpanelInstallWizardBean.federateLater="" ################################################################################ # Specify the host name of the deployment manager for federation. # -W pctfederationpanelInstallWizardBean.hostname="YOUR_DEPLOYMENT_MANAGER_HOST_NAME" ################################################################################ # Specify the port number where the deployment manager (DMGR) is reachable on the # above host. The default port value is "8879". # -W pctfederationpanelInstallWizardBean.port="YOUR_DEPLOYMENT_MANAGER_PORT_NUMBER" ################################################################################ # # Profile type # # Must be set to "managed" for installing a custom profile. Do not change this! # -W profiletypepanelInstallWizardBean.selection="managed"