Using wsadmin to Configure Oracle Fusion Middleware 4-3
WAS_HOMEprofilesDmgr01logsAboutThisProfile.txt. {WAS_HOME}profilesDmgr01binstartManager.sh
{WAS_HOME}binaddNode.sh localhost DepMgrSAOPPort -user yourAdminUserName -password yourAdminPassword -profileName CustomProfileName
Stop the custom node and Deployment Manager. {WAS_HOME}profilesCustomProfileNamebinstopNode.sh -user yourAdminUserName
-password yourAdminPassword {WAS_HOME}profilesDmgr01binstopManager.sh -user yourAdminUserName -password
yourAdminPassword
4.1.2 Environment Setup for IBM WebSphere AS
Before you can use wsadmin to configure your Oracle Fusion Middleware products in an IBM WebSphere AS environment, you must first create an Application Server
profile. To do so, enter the following commands. This command assumes that the WAS_HOME
environment variable has been defined as the WebSphere home directory.
■
UNIX:
Create the Application Server profile and define the Administrator user name and password.
{WAS_HOME}binmanageprofiles.sh -create -templatePath {WAS_HOME}profileTemplatesdefault -enableAdminSecurity true
-adminUserName yourAdminUserName -adminPassword yourAdminPassword
■
Windows:
WAS_HOME\bin\manageprofiles.cmd -create -templatePath WAS_HOME\profileTemplates\default -enableAdminSecurity true
-adminUserName yourAdminUserName -adminPassword yourAdminPassword
In these commands, WAS_HOME represents the IBM WebSphere home directory.
4.1.3 Prerequisites for DB2 Databases
If you are using a DB2 database, you must perform the steps in this section prior to using wsadmin to configure FMW products.
1.
On the Deployment Manager machine, run wsadmin, specifying the Deployment Manager profile. For example, to run wsadmin for the Dmgr01 profile on a UNIX
operating system, enter the following command:
MW_HOMEoracle_commoncommonbinwsadmin.sh -profileName Dmgr01
2.
Enter the following command at the wsadmin prompt:
Note: As an alternative to these steps, you can use the IBM
WebSphere Administrator Console to set the DB2_JCC_DRIVER_ PATH
variable to the DB2 driver directory path.
Note: Before performing Step 2, do not execute the
OracleMWConfig.startConfig command to start a
configuration session. The following command should be executed outside of a configuration session.
4-4 Configuration Guide for IBM WebSphere Application Server
AdminTask.setVariable[-variableName DB2_JCC_DRIVER_PATH -variableValue
Db2DriverDirectory -scope Cell=cellName, Node=nodeName]
In this command, Db2DriverDirectory is the full path to the directory in which the DB2 drivers are located on the Deployment Manager node, cellName is the
name of the cell, and nodeName is the name of the Deployment Manager node.
3.
For each Application Server node in the cell, enter the following command at the wsadmin
prompt: AdminTask.setVariable[-variableName DB2_JCC_DRIVER_PATH
-variableValue Db2DriverDirectory -scope Cell=cellName,
Node=nodeName] In this command, Db2DriverDirectory is the full path to the directory in which
the DB2 drivers are located on the Application Server node, cellName is the name of the cell, and nodeName is the name of the Application Server node.
4.
Enter the following command to save your changes: AdminConfig.save
5.
Enter exit to exit from the wsadmin session. Whenever you add a new Application Server node to the cell, repeat this procedure,
skipping Step 2.
4.2 Starting and Ending a Configuration Session
