test

N1 Grid Service Provisioning System User's Guide and Release Notes for the Oracle App Server 10g Plug-In 1.0

Chapter 4 Using the Oracle App Server 10g Plug-In

The Oracle App Server 10g plug-in provides a number of specific component types and provides easy access to functions for working with Oracle App Server 10g applications. This chapter describes the following information:

Oracle Infrastructure Topologies

An Oracle infrastructure topology refers to a specific Oracle implementation. Each topology consists of one or more installation modules that install such services as the Metadata Repository (MR), the Oracle Internet Directory (OID), and the Single Sign-On (SSO) module.

The Oracle App Server 10g plug-in includes the following Oracle installation modules. Each module is provided as a component within the N1 Grid SPS.

Deploying Oracle Topologies

To deploy any Oracle App Server 10g topology, you install software on one or more systems. The Oracle Application Server silent installer can only install software in one system at the time. Therefore, to install a complex topology that involves several systems, you sequentially install Oracle modules on one machine at a time.

Setting Session Variables

Before you deploy any Oracle topology, you must create several session variables. Make sure that you set the password flag according to the third column of Table 4–1. Any password must have at least five characters, one of which must be numeric. In addition, passwords cannot contain a hyphen (-).

If the name of the host on which you plan to install the MRInstaller component contains a hyphen, you must redefine the variable globalDBName to remove the hyphen. Any name that is registered in the Internet Directory cannot contain a hyphen. Therefore, avoid hyphens in your variable definitions. See the Oracle documentation for details.

To define a session variable, click Session Variables at the top of the browser interface.

Table 4–1 Session Variables

Variable name 

Description 

Password flag 

sysPass

Password for sys user of metadata repository database

Y 

systemPass

Password for system user of metadata repository database

Y 

sourceImage

Full path (visible by all remote agents) to Disk1 of the installation source 

N 

MRInstallerPWD

Password for MR module 

Y 

IDinstallerPWD

Password for ID module 

Y 

J2EEInstallerPWD

Password for J2EE module 

 

J2EESSOInstallerPWD

Password for J2EESSO module 

Y 

J2EESSONWCInstallerPWD

Password for J2EESSONWC module 

Y 

BIInstallerPWD

Password for BI module 

Y 

PWInstallerPWD

Password for PW module 

Y 

OIDhost

Host name for the system on which the Oracle Internet Directory resides 

N 

OIDdomain

Domain for the system on which the Oracle Internet Directory resides 

N 

ProcedureHow to Deploy the J2EE and Web Cache Topology

Upon completion of this task, each target host has the following components:

Steps

  1. Create the session variables.

    For this topology, you need to create only the sourceImage and J2EEInstallerPWD session variables.

  2. In the Common Tasks section of the N1 Grid SPS browser interface, select Oracle App Server 10g.

  3. In the J2EE & Web Cache Topology section of the Oracle App Server 10g Common Tasks page, click Install.

  4. On the Plans Details page, click Run.

  5. Choose variables to use for the J2EEInstaller component.

    • To use an existing variables set, select a name from the drop-down menu in the J2EEInstaller component row of the Plan Parameters table.

    • To create a new variables set, click Select from List in the J2EEInstaller component row of the Plan Parameters table.

      1. Click Create Set.

      2. Type a name for the variables set.

      3. If a component already exists on this host for which the default value for ORACLE_HOME_NAME is used, define a value for the variable ORACLE_HOME_NAME.

        Note –

        Two components installed in the same physical host cannot have the same ORACLE_HOME_NAME.

      4. Save the variables set.

      5. Select the variables set that you just saved from the drop-down menu in the J2EEInstaller component row of the Plan Parameters table.

  6. To use a holder name other than the default, choose variables to use for the Oc4jHolder component.

    • To use an existing variables set, select a name from the drop-down menu in the Oc4jHolder component row of the Plan Parameters table.

    • To create a new variables set, click Select from List in the Oc4jHolder component row of the Plan Parameters table.

      1. Click Create Set.

      2. Type a name for the variables set.

      3. Change the Holder Name.

      4. Save the variables set.

      5. Select the variables set that you just saved from the drop-down menu in the Oc4jHolder component row of the Plan Parameters table.

  7. To use an instance name other than the default, choose variables to use for the Oc4jInstance component.

    • To use an existing variables set, select a name from the drop-down menu in the Oc4jInstance component row of the Plan Parameters table.

    • To create a new variables set, click Select from List in the Oc4jInstance component row of the Plan Parameters table.

      1. Click Create Set.

      2. Type a name for the variables set.

      3. Change the Instance Name.

      4. Save the variables set.

      5. Select the variables set that you just saved from the drop-down menu in the Oc4jInstance component row of the Plan Parameters table.

  8. To select the target host, click Select from List and choose the target host.

    To install the component in several systems at the same time, select more than one target host from the list.

  9. Verify that the target host set is not selected.

    The checkbox in front of the target host set should be empty. Otherwise, the plan will try to install in the host set plus the hosts you selected in the previous step

  10. Click Run Plan (includes preflight).

    Upon successful completion of the plan, all instances will be running.

ProcedureHow to Deploy the J2EE and Web Cache with Identity Management Topology

Upon completion of this task, each target host has the following components:

Steps

  1. Create the session variables.

  2. In the Common Tasks section of the N1 Grid SPS browser interface, select Oracle App Server 10g.

  3. In the J2EE & Web Cache with Identify Management Topology section of the Oracle App Server 10g Common Tasks page, click Install.

  4. Click Run.

  5. Choose variables to use for the MRInstaller component in this plan.

    • To use an existing variables set, select a name from the drop-down menu in the MRInstaller component row of the Plan Parameters table.

    • To create a new variables set, click Select from List in the MRInstaller component row of the Plan Parameters table.

      1. Click Create Set.

      2. Type a name for the variables set.

      3. If a component already exists on this host for which the default value for ORACLE_HOME_NAME is used, define a value for the variable ORACLE_HOME_NAME.

        Note –

        Two components installed in the same physical host cannot have the same ORACLE_HOME_NAME.

      4. Define a value for the variable szIdentityAdminContext.

      5. Save the variables set.

      6. Select the variables set that you just saved from the drop-down menu in the MRInstaller component row of the Plan Parameters table.

  6. Repeat step 5 to redefine ORACLE_HOME_NAME for the IDInstaller, J2EESSOInstaller, and J2EESSONWCInstaller components, if needed.

  7. To use a holder name other than the default, choose variables to use for the Oc4jHolder component.

  8. To use an instance name other than the default, choose variables to use for the Oc4jInstance component.

  9. To select the target host, click on Select from List and choose the target host.

    Select one host on which you want the MRInstaller component to be installed.

  10. Type the name of the hosts on which you want to install the IDInstaller, J2EESSOInstaller, and J2EESSONWCInstaller components

    Use one host for each component.

    Note –

    Place each component on a separate host.

  11. Verify that the target host set is not selected.

    The checkbox in front of the target host set should be empty. Otherwise, the plan will try to install in the host set plus the hosts you selected in the previous step

  12. Click Run Plan (includes preflight).

    Upon successful completion of the plan, all instances will be running.

ProcedureHow to Deploy the Business Intelligence and Forms Topology

Upon completion of this task, each target host has the following components:

Steps

  1. Create the session variables.

  2. In the Common Tasks section of the N1 Grid SPS browser interface, select Oracle App Server 10g.

  3. In the Business Intelligence and Forms Topology section of the Oracle App Server 10g Common Tasks page, click Install.

  4. Click Run.

  5. Choose variables to use for the MRInstaller component in this plan.

    • To use an existing variables set, select a name from the drop-down menu in the MRInstaller component row of the Plan Parameters table.

    • To create a new variables set, click Select from List in the MRInstaller component row of the Plan Parameters table.

      1. Click Create Set.

      2. Type a name for the variables set.

      3. If a component already exists on this host for which the default value for ORACLE_HOME_NAME is used, define a value for the variable ORACLE_HOME_NAME.

        Note –

        Two components installed in the same physical host cannot have the same ORACLE_HOME_NAME.

      4. Define a value for the variable szIdentityAdminContext.

      5. Save the variables set.

      6. Select the variables set that you just saved from the drop-down menu in the MRInstaller component row of the Plan Parameters table.

  6. Repeat step 5 to redefine ORACLE_HOME_NAME in IDInstaller, J2EESSONWCInstaller, J2EESSOInstaller, and BIInstaller components, if needed

  7. To use a holder name other than the default, choose variables to use for the Oc4jHolder component.

  8. To use an instance name other than the default, choose variables to use for the Oc4jInstance component.

  9. To select the target host, click on Select from List and choose the target host.

    Select one host on which you want the MRInstaller component to be installed.

  10. Verify that the target host set is not selected.

    The checkbox in front of the target host set should be empty. Otherwise, the plan will try to install in the host set plus the hosts you selected in the previous step

  11. In the Plan Variables section of the page, type the name of the hosts on which you want to install the IDInstaller, J2EESSONWCInstaller, J2EESSOInstaller, and BIInstaller components.

    Use only one host for each component.

    Note –

    Place each component on a separate host.

  12. Click on Run Plan (includes preflight)

    Upon successful completion of the plan, all instances will be running.

ProcedureHow to Deploy the Portal and Wireless Topology

Upon completion of this task, each target host has the following components:

Steps

  1. Create the session variables.

  2. In the Common Tasks section of the N1 Grid SPS browser interface, select Oracle App Server 10g.

  3. In the Portal and Wireless Topology section of the Oracle App Server 10g Common Tasks page, click Install.

  4. Click Run.

  5. Choose variables to use for the MRInstaller component in this plan.

    • To use an existing variables set, select a name from the drop-down menu in the MRInstaller component row of the Plan Parameters table.

    • To create a new variables set, click Select from List in the MRInstaller component row of the Plan Parameters table.

      1. Click Create Set.

      2. Type a name for the variables set.

      3. If a component already exists on this host for which the default value for ORACLE_HOME_NAME is used, define a value for the variable ORACLE_HOME_NAME.

        Note –

        Two components installed in the same physical host cannot have the same ORACLE_HOME_NAME.

      4. Define a value for the variable szIdentityAdminContext.

      5. Save the variables set.

      6. Select the variables set that you just saved from the drop-down menu in the MRInstaller component row of the Plan Parameters table.

  6. Repeat step 5 to redefine ORACLE_HOME_NAME in the IDInstaller, J2EESSONWCInstaller, J2EESSOInstaller, and PWInstaller components, if needed

  7. To use a holder name other than the default, choose variables to use for the Oc4jHolder component.

  8. To use an instance name other than the default, choose variables to use for the Oc4jInstance component.

  9. To select the target host, click on Select from List and choose the target host.

    Select one host on which you want the MRInstaller component to be installed.

  10. Verify that the target host set is not selected.

    The checkbox in front of the target host set should be empty. Otherwise, the plan will try to install in the host set plus the hosts you selected in the previous step

  11. In the Plan Variables section of the page, type the name of the hosts on which you want to install the IDInstaller, J2EESSONWCInstaller, J2EESSOInstaller, and PWInstaller components.

    Use only one host for each component.

    Note –

    Place each component on a separate host.

  12. Click Run Plan (includes preflight).

    Upon successful completion of this plan, all instances will be running.

Changing the Global Database Name

By default, the global database name in the MRInstaller uses the host name. If your host name includes a hyphen, you need to change the global database name to remove that hyphen. This change affects several variables in several components.

Table 4–2 Global Database Name Variables

Component 

Variable 

Default 

Changed Example 

MRInstaller 

globalDBName

:[dbSid].:[dbHost]

:[dbSid].SP

J2EESSOInstaller 

szl_ClusterRepository

{":[OIDFQN]:1521::[SID].:[OIDFQN]::[SID].:[OIDFQN]"},

where [OIDFQN] is derived from :[OIDhost].:[OIDdomain]

{":[OIDFQN]:1521::[SID].SP::[SID].SP"}

J2EESSONWCInstaller 

szl_ClusterRepository

{":[OIDFQN]:1521::[SID].:[OIDFQN]::[SID].:[OIDFQN]"}

{":[OIDFQN]:1521::[SID].SP::[SID].SP"}

BIInstaller 

szl_RepositoryUserInput

{":[OIDFQN]:1521::[SID].:[OIDFQN]::[SID].:[OIDFQN]"}

{":[OIDFQN]:1521::[SID].SP::[SID].SP"}

PWInstaller 

szl_RepositoryUserInput

{":[OIDFQN]:1521::[SID].:[OIDFQN]::[SID].:[OIDFQN]"}

{":[OIDFQN]:1521::[SID].SP::[SID].SP"}

Using SSL with Oracle App Server Topologies

By default, the identity management feature (IDInstaller component) is the only topology that uses SSL for secure communication. To enable the J2EESSOInstaller, J2EESSONWCInstaller, BIInstaller, or PWInstaller components to use SSL, change the szOIDwithSSLStatus variable to Y. When you do this, you also need to change the value for the OIDport variable to :[InternetDirectorySSLPort].

The following list shows the relationship between the two variables:

szOIDwithSSLStatus="Y"

OIDport=":[InternetDirectorySSLPort]"

szOIDwithSSLStatus="N"

OIDport=":[InternetDirectoryPort]"

Undeploying Topologies

To undeploy a topology, you uninstall the appropriate topology.

ProcedureHow to Undeploy a Topology

Steps

  1. In the Common Tasks section of the N1 Grid SPS browser interface, select Oracle App Server 10g.

  2. In the appropriate Infrastructure Tasks Topology section of the Oracle App Server 10g common tasks page, click Uninstall.

    The Components Details page displays for this topology.

  3. On the Components Details page, click the Run action next to default:uninstall.

  4. On the Plans Details Run page, select the host from which you want to undeploy the topology.

  5. Click Run Selected Installations.

    The Plans Details Run page reappears with information about the specific host.

  6. To confirm that you want to uninstall this topology, click Run Plan (includes preflight).

    When the topology is uninstalled, all the components that are part of that topology are uninstalled.

Importing Topologies

You can also import an Oracle topology from your datacenter into the provisioning system.

ProcedureTo Import a Topology

Upon completion of this task, components in N1 Grid SPS will represent your topology.

Steps

  1. Identify the topology that you want to import.

  2. Follow the appropriate deployment procedure for the topology that you want to install.

    For more information, see Deploying Oracle Topologies.

  3. Create variable sets for the components and define variables so that they match what you have installed.

  4. Set the value for Full Install to FALSE.

    Most of the infrastructure plans give you the option for full install and uninstall. When you set this variable to FALSE, the N1 Grid SPS software performs the plan at the provisioning software level without doing the Oracle portion. You can then import clusters using Create and Join, and you can import OC4J instances by running Create OC4J.

  5. Click Run Plan (includes preflight).

Modifying Topologies

You can change one of the installed topologies by adding components to it. For example, you might want to install more J2EESSOInstaller components to a J2EE & Web Cache Topology, or you might want to add a BIInstaller to a J2EE & Web Cache with Identity Management Topology.

ProcedureTo Add Components to an Imported Topology

Upon completion of this task, the selected component is installed in the host that you selected. The selected component is associated with an MRInstaller component. This new component will be uninstalled automatically when you uninstall the MRInstaller component with which the selected component is associated.

Steps

  1. In the Application Deployment section of the N1 Grid SPS browser interface, click Components.

  2. If needed, select Change Folder and go to /com/sun/oracle10g_AS.

  3. From the Components page, select the component that you want to add to a topology.

  4. Under component procedures, run the default install.

  5. Select the physical host on which you want to install the component.

  6. Provide the name of the physical host that has the MRInstaller component.

  7. Provide the ORACLE_HOME_NAME value for the host that has the MRInstaller component.

  8. Click Run Plan (includes preflight).

ProcedureTo Start an Enterprise-Related Topology

If your system goes down unexpectedly, or if some other event causes your J2EE & Web Cache or J2EE & Web Cache with Identity Management topology to stop, you can start those topologies through the plug-in.

When you start the J2EE & Web Cache or J2EE & Web Cache with Identity Management topology, the top-level component checks the status of any dependent sub-components. If the sub-component is not started, the start control starts the sub-component.

Note –

For the Business Intelligence and Forms topology and the Portal and Wireless topology, you have to start the individual components separately. Specifically, you have to start the BIInstaller or PWInstaller component, as well as the applicable J2EESSOInstaller and J2EESSONWCInstaller components.

Steps

  1. In the Application Deployment section of the N1 Grid SPS browser interface, click Components.

  2. If needed, select Change Folder and go to /com/sun/oracle10g_AS.

  3. From the Components page, click the J2EESSOInstaller or J2EESSONWCInstaller component that you want to start.

  4. Under component procedures, run the Start control.

  5. Select the physical host on which you want to start the component.

  6. Click Run Plan (includes preflight).

Managing Application Server Instances

This section describes the services available for application server instances.

ProcedureHow to Start an Application Server Instance

Steps

  1. In the Common Tasks section of the N1 Grid SPS browser interface, select Oracle App Server 10g.

  2. In the Application Server Instance Management section of the Oracle App Server 10g Common Tasks page, click Start.

  3. On the Plans Details page, click Run.

  4. Select the virtual target host that is associated with the application server instance that you want to start.

    Tip –

    To start several application servers at the same time, select more than one host.

  5. Verify that the target host set is not selected.

    The checkbox in front of the target host set should be empty. Otherwise, the plan will try to start all application server instances in the host set plus the hosts you selected in the previous step

  6. Click Run Plan (includes preflight).

    At the end of the plan execution, all the application servers will be running.

ProcedureHow to Stop an Application Server Instance

Steps

  1. In the Common Tasks section of the N1 Grid SPS browser interface, select Oracle App Server 10g.

  2. In the Application Server Instance Management section of the Oracle App Server 10g Common Tasks page, click Stop.

  3. On the Plans Details page, click Run.

  4. Select the virtual target host that is associated with the application server instance that you want to stop.

    Tip –

    To stop several application servers at the same time, select more than one host.

  5. Verify that the target host set is not selected.

    The checkbox in front of the target host set should be empty. Otherwise, the plan will try to stop all application server instances in the host set plus the hosts you selected in the previous step

  6. Click Run Plan (includes preflight).

    At the end of the plan execution, all the application servers will be stopped.

ProcedureHow to Create an OC4J Instance

An OC4J (Oracle Application Server Containers for J2EE) instance provides support for J2EE applications. Upon completion of this task, an OC4J instance will have been created in an application server.

Steps

  1. In the Common Tasks section of the N1 Grid SPS browser interface, select Oracle App Server 10g.

  2. In the Application Server Instance Management section of the Oracle App Server 10g Common Tasks page, click Create OC4J

  3. On the Plans Details page, click Run.

  4. To create a new variables set, click Select from List in the Oc4jInstance component row section of the plan parameters table.

  5. Click Create Set.

  6. Type a name for this variable set.

  7. Define a value for the variable instanceName.

    Note –

    Two OC4J instances created in the same application server cannot have the same name. You always need to redefine this value since the default value (home) is used to create the OC4J instance that is always present in an application server.

  8. Save this variable set and select it so it is used in the execution of the plan.

  9. Select the Oc4jHolderHT virtual target hosts on which you want to create the OC4JInstance component.

    Tip –

    To create instances on several hosts at the same time, select more than one host.

  10. Verify that the target host set is not selected.

    The checkbox in front of the target host set should be empty. Otherwise, the plan will try to install in the host set plus the hosts you selected in the previous step

  11. Click Run Plan (includes preflight).

    At the end of the plan execution, each targeted Oc4jHolderHT virtual host will have an additional OC4JInstance component with the name you defined.

ProcedureHow to View All OC4J Instances

Steps

  1. In the Common Tasks section of the N1 Grid SPS browser interface, select Oracle App Server 10g.

  2. In the Application Server Instance Management section of the Oracle App Server 10g Common Tasks page, click View All OC4Js.

    A list of installed OC4J instances appears.

ProcedureHow to Remove an OC4J Instance

Steps

  1. In the Application Deployment section of the N1 Grid SPS browser interface, click Components.

  2. If needed, select Change Folder and go to /com/sun/oracle10g_AS.

  3. Click Oc4jInstance.

  4. Under component procedures, run the default uninstall.

  5. Select the Oc4jInstance component that you want to remove.

    Note –

    You cannot remove the home instance.

Managing Oracle Application Server Clusters

This section presents functionality for cluster management. A file-based cluster is created by assigning the file based repository of an Oracle App Server instance as the cluster repository. When an Oracle App Server instance joins the cluster, the instance stops using its repository and starts using the cluster repository. As a consequence, the former instance immediately adopts the configuration described in the cluster repository.

A cluster is composed of one or more J2EEInstaller components. In a cluster, one J2EEInstaller component is the cluster master and additional J2EEInstaller components are members of the cluster. The instance that represents the cluster master has a component called ClusterMaster installed in its virtual host. In a similar way, the J2EEInstaller components that are members of the cluster have a ClusterMember component installed in them.

ProcedureHow to Create a Cluster

Upon completion of this task, the following changes will have been made:

Before You Begin

To create a cluster, you must already have a J2EEInstaller component installed. For more information, see How to Deploy the J2EE and Web Cache Topology.

Steps

  1. In the Common Tasks section of the N1 Grid SPS browser interface, select Oracle App Server 10g.

  2. In the Cluster Management section of the Oracle App Server 10g Common Tasks page, click Create.

  3. On the Plans Details page, click Run.

  4. Select the virtual host that you want to target.

    The host must be a member of the ClusterHostSet. Also, the host must not contain a ClusterMaster component or a ClusterMember component. You can select more than one virtual host.

  5. Verify that the target host set is not selected.

    The checkbox in front of the target host set should be empty. Otherwise, the plan will try to install in the host set plus the hosts that you selected in the previous step

  6. Click Run Plan (includes preflight).

ProcedureHow to Add a J2EEInstaller Component to an Existing Cluster

Upon completion of this task, the following changes will have been made:

Before You Begin

To assign a J2EEInstaller component to a cluster, the cluster must already exist. See How to Create a Cluster.

Steps

  1. In the Common Tasks section of the N1 Grid SPS browser interface, select Oracle App Server 10g.

  2. In the Cluster Management section of the Oracle App Server 10g Common Tasks page, click Join.

  3. On the Plans Details page, click Run.

  4. On the Plans Details Run page, select the virtual host that you want to target.

    The host must be a member of the ClusterHostSet. Also, the host must not contain a ClusterMaster component or a ClusterMember component. You can select more than one virtual host.

  5. Verify that the target host set is not selected.

    The checkbox in front of the target host set should be empty. Otherwise, the plan will try to install in the host set plus the hosts that you selected in the previous step

  6. Type the value for the ORACLE_HOME_NAME of the J2EEInstaller component that contains the ClusterMaster of the cluster you want to join.

  7. Type the name of the physical host on which the ClusterMaster component is installed.

  8. Click Run Plan (includes preflight).

ProcedureHow to Remove a J2EEInstaller Component from a Cluster

When an Oracle App Server instance leaves the cluster, the cluster repository is copied into the file-based repository of the instance. From this point on, the instance uses its own repository and commands issued to this instance to modify OC4J instances or applications only affect this instance.

Upon completion of this task, these changes will have been made:

Note –

The application server instance leaving the cluster inherits a copy of all the OC4J instances and applications that were deployed in the cluster. N1 Grid SPS limitations cannot represent this change, therefore, this instance will be out of sync with the Oracle application. The home OC4JInstance will be created, but other OC4J instances in the cluster and the applications that they contain will be missing. To resynchronize this component with Oracle, you must use a markOnly install or set the full Install parameter to false when you run plans.

Before You Begin

To remove a J2EEInstaller component from a cluster, the component must be a member of a cluster. See How to Add a J2EEInstaller Component to an Existing Cluster.

Steps

  1. In the Common Tasks section of the N1 Grid SPS browser interface, select Oracle App Server 10g.

  2. In the Cluster Management section of the Oracle App Server 10g Common Tasks page, click Leave.

  3. On the Plans Details page, click Run.

  4. On the Plans Details Run page, select the virtual host that you want to remove from the cluster.

    The host must be a member of the ClusterHostSet. Also, the host must not contain a ClusterMaster component or a ClusterMember component. You can select more than one virtual host.

  5. Verify that the target host set is not selected.

    The checkbox in front of the target host set should be empty. Otherwise, the plan will try to remove components in the host set plus the hosts that you selected in the previous step

  6. Click Run Plan (includes preflight).

ProcedureHow to View Cluster Masters

Steps

  1. In the Common Tasks section of the N1 Grid SPS browser interface, select Oracle App Server 10g.

  2. In the Cluster Management section of the Oracle App Server 10g Common Tasks page, click View Masters.

    A list of the installed ClusterMaster components appears. Each component corresponds to a different cluster.

ProcedureHow to View Cluster Members

Steps

  1. In the Common Tasks section of the N1 Grid SPS browser interface, select Oracle App Server 10g.

  2. In the Cluster Management section of the Oracle App Server 10g Common Tasks page, click View Members.

    A list of the installed ClusterMember components appears. Each component corresponds to a J2EEInstaller component that is a member of a cluster.

ProcedureHow to Remove a Cluster

To remove a cluster you must first remove all the members of the cluster. Follow the procedures explained in previous sections to do so. Once the cluster has no members, follow these steps to remove the cluster.

Steps

  1. In the Application Deployment section of the N1 Grid SPS browser interface, click Components.

  2. If needed, select Change Folder and go to /com/sun/oracle10g_AS.

  3. Click ClusterMaster.

  4. Under component procedures run the default uninstall.

  5. Select the ClusterMaster component that you want to remove.

Working with Enterprise Applications

Use the Oracle App Server 10g Common Tasks page to capture and deploy Oracle enterprise applications.

ProcedureTo Capture an Enterprise Application or EAR File

Steps

  1. In the Common Tasks section of the N1 Grid SPS browser interface, select Oracle App Server 10g.

  2. In the Enterprise Applications (EARs) section of the Oracle App Server 10g Common Tasks page, click Create New.

  3. Type a name for the captured component.

    Note –

    You can include a path to the location to store the captured files. The default folder for the plug-in (/com/sun/Oracle AS 10g) is a read-only directory.

  4. (Optional) Type a label for this component.

  5. (Optional) Type a description for this component.

  6. Select the Oracle administration server on which this enterprise application resides.

  7. Browse through the file system to find the enterprise application to capture.

    Tip –

    Make sure that you select the top of the EAR file. Doing so ensures that all files that are part of the enterprise application are included, such as the XML file in which Oracle maintains application settings.

  8. Click Check-in Selected Item.

  9. Confirm the information on the check-in page, then click Continue to Check-in.

ProcedureTo Deploy Enterprise Applications

Steps

  1. In the Common Tasks section of the N1 Grid SPS browser interface, select Oracle App Server 10g.

  2. In the Enterprise Applications (EARs) section of the Oracle App Server 10g Common Tasks page, click View All.

  3. If needed, select Change Folder and navigate to the directory where you stored your captured files.

  4. Click the name of the component that you want to deploy.

Working with Web Applications

Use the Oracle App Server 10g Common Tasks page to capture and deploy Oracle web applications.

ProcedureTo Capture a Web Application or WAR File

Steps

  1. In the Common Tasks section of the N1 Grid SPS browser interface, select Oracle App Server 10g.

  2. In the Web Applications (WARs) section of the Oracle App Server 10g Common Tasks page, click Create New.

  3. Type a name for the captured component.

    Note –

    You can include a path to the location to store the captured files. The default folder for the plug-in (/com/sun/Oracle AS 10g) is a read-only directory.

  4. (Optional) Type a label for this component.

  5. (Optional) Type a description for this component.

  6. Select the Oracle administration server on which this web application resides.

  7. Browse through the file system to find the web application to capture.

    Tip –

    Make sure that you select the top of the WAR file. Doing so ensures that all files that are part of the web application are included, such as the XML file in which Oracle maintains application settings.

  8. Click Check-in Selected Item.

  9. Confirm the information on the check-in page, then click Continue to Check-in.

Creating and Editing Data Sources

ProcedureHow to Capture a Data Source

Steps

  1. In the Common Tasks section of the N1 Grid SPS browser interface, select Oracle App Server 10g.

  2. In the Data Source section of the Oracle App Server 10g Common Tasks page, click Create New.

  3. Type a name for the captured component.

    Note –

    You can include a path to the location to store the captured files. The default folder for the plug-in (/com/sun/Oracle AS 10g) is a read-only directory.

  4. (Optional) Type a label for this component.

  5. (Optional) Type a description for this component.

  6. Select the Oracle administration server on which this data source resides.

  7. Browse through the file system to find the data source to capture.

    Tip –

    Make sure that you select the top of the WAR file. Doing so ensures that all files that are part of the data source are included.

  8. Click Check-in Selected Item.

  9. Confirm the information on the check-in page, then click Continue to Check-in.

ProcedureHow to Modify a Data Source

Steps

  1. In the Common Tasks section of the N1 Grid SPS browser interface, select Oracle App Server 10g.

  2. In the Data Source section of the Oracle App Server 10g common tasks page, click View.

Component Types

The Oracle App Server 10g Plug-In includes several component types. These component types enable you to quickly model many of the most common Oracle Application Server components and to automatically associate install, uninstall, export, and snapshot behavior with a particular resource. Many of the component types are used by the software when you create and manage servers and clusters. You are unlikely to need to work with any of these components directly.