Creating a Middleware Resource

Using Oracle Cluster Ready Services 13-11 ■ The database home is installed on a shared disk. The data files of this database are on the same or different shared disks. CRS resources have been created for all these shared disks with ascrsctl and started. ■ A CRS resource has been created for the database listener with an ascrsctl command, and the resource is started. ■ The database is CFC enabled. See Section 12.2.4, Transforming an Oracle Database for details. ■ Ensure the database sid and Oracle home are valid. ASCRS does not do extensive validation of this information for this release. The following is a syntax example for creating the database instance resource: ascrsctl create -n mydb -type db -oh cfcdb -lsnr mydblsnr -disk ohdisk datadisk Creating all the other database resources requires the following: ■ A valid Oracle database home. ■ The database SID name. ■ The disk resource name for the Oracle home. ■ A valid virtual IP resource name. This is required for the Oracle Database Console dbconsole database resource only. ■ The database is CFC enabled. For online help information for creating an Oracle database resource, use the following command: ascrsctl help -c create -t db

13.4.1.5 Creating a Middleware Resource

OPMN instances and WebLogic servers are collectively called Application Server AS components and are managed by separate resources. Specifically, all OPMN managed components have to be managed by one resource and all servers under a WebLogic domain have to be managed by a different resource.

13.4.1.5.1 Creating a Resource for OPMN Managed Components The following information

is needed for creating a resource for an OPMN managed instance: ■ A valid instance home for the OPMN managed components. ■ A disk resource name for the instance home ■ A disk resource name for the instances Oracle home if is on a different shared disk ■ The names of the OPMN managed applications for inclusion in the resource. If you plan to include only a subset of all the components, the other remaining components wont be managed by CRS and they shouldnt be started outside CRS. By default, all the components are included. Before creating the OPMN resource, carefully check the following: ■ The Oracle home is installed on a shared disk. The OPMN instance is on the same or different shared disk. CRS resources have been created for all these shared disks with ascrsctl and started. Shutdown all OPMN managed applications. ■ The OPMN server and its managed Oracle Fusion Middleware components have been CFC enabled. Refer to Section 12.2.2.6, Transforming Oracle Process 13-12 Oracle Fusion Middleware High Availability Guide Management and Notification Server through Section 12.2.2.9, Instance-specific considerations and to Section 12.2.3, Transforming Oracle Fusion Middleware Components for the steps to enable CFC for Oracle Fusion Middleware components. ■ On Windows, ensure the start method of the OPMN Windows service pertaining to this instance is ’Disabled.’ The following is a syntax example for creating the resource Oracle home and instance home are on the same disk. All components are included.: ascrsctl create -n myopmn -type as -ch cfcas -disk ohdisk For online help information for creating an OPMN instance resource, use the following command: ascrsctl help -c create -t as

13.4.1.5.2 Creating a Resource for WebLogic Servers Creating a CRS resource for a

WebLogic domain requires more preparation than other resource types. Due to its complexity, the procedure is divided into the following sections: ■ Basic Setup ■ Node Manager Setup ■ Administration Server Setup ■ Creating the Resource Basic Setup Before starting the basic setup, be sure that WebLogic is installed on shared disks. WebLogic Server software and the domain instance can be installed on either the same or separate shared disk. In addition, before proceeding to the following Node Manager and Server Setup, ensure that the WebLogic Server environment is CFC enabled. See Section 12.2.2.3, Transforming the Administration Server for Cold Failover Cluster through Section 12.2.2.5, Transforming Node Manager for details on enabling CFC for the Oracle WebLogic Server environment. Once CFC is enabled, you can manually start and stop the server, the original node, and the failover nodes without noticeable difference. To create the dependency resources: 1. Create a CRS resource for each shared disk and start it on the node on which it was created. 2. Create a CRS resource for the virtual IP with the ascrsctl command and start it on the same cluster node. Node Manager Setup To set up the Node Manager 1. For Windows Server 2008, on each node, create Node Manager Windows service if it does not already exist, by executing the following command from the WL_ HOMEserverbin directory: installNodeMgrSvc.cmd From Windows Service Manager, make sure this service is in manual start mode. Using Oracle Cluster Ready Services 13-13 2. If you have not yet done so, change Node Managers username and password. The initial password is randomly generated. To change the Node Manager password, in the WebLogic Server Administration Console, select Domain, Security, General , and then Advanced. Enter the new password and click Save. 3. If you have changed anything in steps 1 or 2, restart the Node Manager. On Unix, using the following command from the WL_HOMEserverbin directory: startNodemanager.sh On Windows, start Node Manager from the service manager.: 4. Start the WebLogic scripting tool in the WL_HOMEcommonbin directory. To persist Node Manager’s user login information in the ascrscf.dat and ascrskf.dat files, use the following commands: nmConnectnmUser,nmPasswd,hostname,nmPort,domainName,domainDir storeUserConfig’WL_HOMEcommonnodemanagerascrscf.dat’, ’WL_HOMEcommonnodemanagerascrskf.dat’,’true’ nmDisconnect exit 5. For Unix platforms, copy CRS_HOMEascrspubliccfcStartNodeManager.sh to the WL_HOMEserverbin directory, and make the script executable. After you have started Node Manager for the first time, you can edit the nodemanager.properties file to set the StartScriptEnabled property. The nodemanager.properties file does not exist until Node Manager is started for the first time. In the WL_HOMEcommonnodemanager directory, set the StartScriptEnabled property in the nodemanager.properties file to true. StartScriptEnabled=true Check the nodemanager.properties file to ensure no value is assigned to ListenAddress, and that a valid port number is assigned to ListenPort. When this property is set in the nodemanager.properties file, you no longer need to define it in the JAVA_OPTIONS environment variable. Server Setup 1. All WebLogic servers listen on the virtual IP. To ensure this is configured correctly, log in to the WebLogic Server Administration Console and navigate to Environment Servers server_name Configuration General page and verify that the virtual IP and the port number are both set correctly and click Save. 2. Each server must also listen on the localhost. To ensure this is configured correctly, log into the WebLogic Server Administration Console and do the following:

a. In the Domain tree, select Environment, Servers, server_name, Protocols, and