4-2 Configuration Guide for IBM WebSphere Application Server
manageprofiles.cmd command Windows to set up the initial Deployment
Manager profile and the empty custom profile that are needed for configuration. The following sections describe how to do this in an IBM WebSphere ND environment and
an IBM WebSphere AS environment.
4.1.1 Environment Setup for IBM WebSphere ND
Before you can use wsadmin to configure your Oracle Fusion Middleware products in an IBM WebSphere ND environment, you must first create a management profile with
a serverType of DEPLOYMENT_MANAGER. You must also federate add an empty custom profile to the Deployment Manager.
The following script uses IBM WebSphere commands to:
■
Create the Deployment Manager profile and Deployment Manager on the local machine
■
Set the Administrator user name and password for the Deployment Manager
■
Create an empty custom profile
■
Start the Deployment Manager required to federate the custom node
■
Federate the custom node to the local machine
■
Shut down the custom node
■
Shut down the Deployment Manager
The script assumes that the WAS_HOME environment variable has been defined as the IBM WebSphere home directory:
Create the Deployment Manager profile and Deployment Manager, and define the Administrator user name and password. serverType must be
DEPLOYMENT_MANAGER. {WAS_HOME}binmanageprofiles.sh -create -templatePath {WAS_HOME}
profileTemplatesmanagement -serverType DEPLOYMENT_MANAGER -enableAdminSecurity true -adminUserName yourAdminUserName -adminPassword
yourAdminPassword Create an empty custom profile. The default custom profile name is Customnn,
where nn is the next available value in the sequence, starting with 01. When you are creating the first custom profile in the cell, the profile name
is typically Custom01. {WAS_HOME}binmanageprofiles.sh -create -templatePath {WAS_
HOME}profileTemplatesmanaged Start the Deployment Manager and federate the custom node on the same machine.
The startManager.sh command must be issued from the Deployment Manager profile directory, Dmgr01. The DepMgrSOAPPort can be determined by opening the file
Note: You do not have to perform the steps in this section if you
have already used the Configuration Wizard to create the initial Deployment Manager profile and custom profile.
Note:
The commands used to set up the environment in a Windows operating system are the same as in a UNIX operating system, except
that all paths use backslash \ instead of forward slash , and all command names have a .cmd extension instead of a .sh extension.
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
