Contents

Index

Advanced Plug-in Procedures

This page contains the following information:

How to Prepare an Established Cluster for Use With This Plug-in
How to Use Custom Installer State Files With This Plug-in
How to Use This Plug-in to Install Data-Service Agents

How to Prepare an Established Cluster for Use With This Plug-in

Cluster nodes can remain in full production while you perform any of the following procedures.

1. Configure the N1SPS virtual hosts.

a. Create the required virtual hosts as described in How to Create N1SPS Virtual Hosts for Use With This Plug-in.

b. Configure virtual host variables as described in Variables for Plug-in Virtual Hosts of Type "clusterNode" and
Variables for Plug-in Virtual Hosts of Type "cluster".

2. Install the "scConfigFiles" component.

a. Select the component details page for the component "/com/sun/SunCluster/simpleComps/scConfigFiles".

b. Click the "run" action for the component procedure "install:default".

The list of target hosts must include the complete list of "clusterNode" host types for each cluster to be
updated. Do not include physical hosts or hosts of type "cluster".

c. Click the "run plan" button.

3. Install the "scNativeScripts" component.

a. Select the component details page for the component "/com/sun/SunCluster/simpleComps/scNativeScripts".

b. Click the "run" action for the component procedure "install:default".

The list of target hosts must include the complete list of "clusterNode" host types for each cluster to be
updated. Do not include physical hosts or hosts of type "cluster".

c. Click the "run plan" button.

4. Mark-only install the "scSoftware" component.

a. Select the component details page for the component "/com/sun/SunCluster/scSoftware".

b. Click the "run" action for the component procedure "install:markOnly".

The list of target hosts must include the complete list of "clusterNode" host types for each cluster to be
updated. Do not include physical hosts or hosts of type "cluster".

c. Click the "run plan" button.

5. Mark-only install the "sunCluster" component.

a. Select the component details page for the component "/com/sun/SunCluster/sunCluster".

b. Click the "run" action for the component procedure "install:markOnly".

c. Configure the "sunCluster" component variables as described in Variables for Plug-in Component "sunCluster".

The list of target hosts must include the complete list of "clusterNode" host types for each cluster to be
updated. Do not include physical hosts or hosts of type "cluster".

d. Click the "run plan" button.

How to Use Custom Installer State Files With This Plug-in

Custom Sun Java Availability Suite (JAS) installer state files can be used with the plug-in plans for
creating clusters, adding cluster nodes, and only installing cluster software. However, all of these
plans skip the JAS installation step if it is found that the Sun Cluster software itself is already
installed, either by the plug-in or by other means. So, custom JAS installer state files can only be
effectively used if the Sun Cluster framework software is not yet installed.

To use a custom JAS installer state file, perform the following steps:

1. Create a JAS installer prototype state file.

JAS installer state files might have Solaris version dependencies. So, make sure that the custom state
file that you create is compatible with your release of Solaris.

Refer to the Java Enterprise System (JES) installation documentation for information regarding JES
or JAS state files.

• The easiest way to create a prototype state file without actually installing anything is to run the
  JAS installer as follows:

  # installer -no -nodisplay -saveState myPrototypeStateFile

  Respond to the "installer" prompts to best customize your prototype. Then edit the new prototype to
  remove references to individual node names and IP addresses.

• Alternatively, you can start with one of the state files that ships with this plug-in.

  1. Select the component-details page for the component "/com/sun/SunCluster/simpleComps/scConfigFiles".
  2. Click "download system#directory". You will find the state files in "root/JAS_StateFiles/solaris_cluster_3_2/Solaris_9"
  and "root/JAS_StateFiles/solaris_cluster_3_2/Solaris_10".

2. (Optional) Edit the state file IDs in the prototype state file.

Each JAS/JES state file includes "[STATE_BEGIN ..." and "[STATE_DONE ..." statements. The last field
in each of these two statements is a state-file ID ("... statefile_id]". If you replace the
"statefile_id" with the string "STATEFILEID", this plug-in will substitute "STATEFILEID" with an
appropriate state-file ID. This applies to both installer and uninstaller state files.

3. (Optional) Perform additional edits to the custom state file.

Refer to the Java Enterprise System (JES) installation documentation for information regarding JES
or JAS state files.

4. Push the new custom state file.

Use one of the following methods:

• Copy the new state file to each of the hosts that will depend upon it. Place the new state file in
  the same location on each host. Use any method that you are most comfortable with to copy the customized
  state file to each new node.

• Use N1SPS to push out the custom state file.

5. Use the new custom state file in plug-in plans.

The plans for creating clusters, adding cluster nodes, and only installing cluster software all prompt
for the following:

Java Availability Suite installer state file: Provide the full path of the state file.

The use of custom JAS uninstall state files is also supported by the plan that uninstalls Sun Cluster
software.

How to Use This Plug-in to Install Data-Service Agents

You can use this plug-in to install any Sun Cluster data-service agents that are found on the Java
Availability Suite (JAS) distribution. To install such agent software, follow the instructions in
How to Use Custom Installer State Files With This Plug-in. Edit the "PSP_SELECTED_COMPONENTS"
statement to include both the data-service agent and "SCAgents".

For example, a state file with the following statement will result in the installation of both the
Sun Cluster framework and the Oracle RAC agent software:

PSP_SELECTED_COMPONENTS = SCCore, SCManager, SunCluster,
SunCluster_Oracle_RAC, SCAgents, EntsysUninstallerSUNWentsys5

As another example, a state file that includes the following will install both the Sun Cluster framework
and all of the agent software:

PSP_SELECTED_COMPONENTS = SCCore, SunCluster_HA_SAP_liveCache_3.1,
SunCluster_HA_SAP_3.1, SunCluster_HA_DHCP_3.1, SCDirServer,
SunCluster_HA_KERBEROS_3.2, SunCluster_HA_NFS_3.1,
SunCluster_HA_MQI_3.1, SunCluster_HA_SUN_GRID_ENG_3.1, SCAppServer,
SCManager, SunCluster_HA_SAPDB_1.0, SunCluster_HA_APACHE_TC_3.1,
SunCluster_HA_N1G_SPS_3.1, SunCluster_HA_Samba_3.1, SCCalServer,
SCMsgServer, SunCluster_HA_MQS_3.1, SunCluster,
SunCluster_HA_BEA_WLS_3.1, SCMQ, SunCluster_HA_POSTGRESQL_3.2,
SunCluster_HA_Oracle_3.1, SunCluster_Oracle_RAC,
SunCluster_HA_MYSQL_3.1, SunCluster_HA_SOLARIS_ZONES_3.1,
SCInstantMessaging, SCHADB, SCWebServer, SunCluster_HA_DNS_3.1,
SunCluster_HA_Apache_3.1, SCAgents, SunCluster_HA_SAPWebAS_1.0,
EntsysUninstallerSUNWentsys5

This plug-in only supports the installation of agent software at the time that the Sun Cluster framework
is installed.