NOTE:
a) Ensure that necessary permissions are available for the user running manageprofile.sh
b) Ensure that the filesystem has sufficient space for the creation of the profile
c) Please select the appropriate ProfileName , Directory path , CellName, NodeName etc as per your requirement
Cell Profile :
1) Cell profiles are actually two profiles in one profile creation method .
2) It has a deployment manager profile and a federated application server profile.
3) The federation is also automatically done by the profile creation wizard
4) An Application sever “server1” is also created by default
5) The profile can be created on the same host only and cannot span multiple physical servers
6) Its used to create a fast dev or a test environment for the development team
Steps to create a Cell Profile:
Step1 : Navigate to WAS_HOME/bin directory
| [root@mercury MyServer]# cd /opt/IBM/WebSphere/AppServer/bin |
Execute ./manageprofile.sh
Cell Profile with Minimal Parameters
| [root@mercury bin]#./manageprofiles.sh -create -profileName Dmgr02 -adminUserName wasadmin -adminPassword p@ssword -enableAdminSecurity true -cellName mercuryCell01 -nodeName mercuryCellManager01 -profilePath /opt/IBM/WebSphere/AppServer/profiles/Dmgr02 -nodeProfilePath /opt/IBM/WebSphere/AppServer/profiles/AppSrv01 -appServerNodeName mercuryNode02 -templatePath /opt/IBM/WebSphere/AppServer/profileTemplates/cell/dmgr |
Cell Profile with advanced options ( Custom Ports , Certificates )
| [root@mercury bin]#./manageprofiles.sh -create -profileName Dmgr02 -adminUserName p@sswordwasadmin -adminPassword p@ssword -nodePortsFile /opt/IBM/WebSphere/AppServer/logs/manageprofiles/123_cellNode_portdef.props -enableAdminSecurity true -cellName mercuryCell01 -nodeName mercuryCellManager01 -portsFile /opt/IBM/WebSphere/AppServer/logs/manageprofiles/123_cellDmgr_portdef.props -personalCertDN cn=mercury.com,ou=mercuryCell01,ou=mercuryCellManager01,o=IBM,c=US -profilePath /opt/IBM/WebSphere/AppServer/profiles/Dmgr02 -nodeProfilePath /opt/IBM/WebSphere/AppServer/profiles/AppSrv01 -appServerNodeName mercuryNode02 -enableService false -signingCertDN cn=mercury.com,ou=Root Certificate,ou=mercuryCell01,ou=mercuryCellManager01,o=IBM,c=US -hostName mercury.com -personalCertValidityPeriod 1 -signingCertValidityPeriod 15 -keyStorePassword WEBAS -templatePath /opt/IBM/WebSphere/AppServer/profileTemplates/cell/dmgr |
Step2: Checks to ensure proper profile creation
a) Should get an INSTCONSUCCESS message for manageprofile in the <WAS_HOME>/logs/manageprofiles/<ProfileName>_create.log
b) Navigate to the dmgr and appserver profile folders ie /opt/IBM/WebSphere/AppServer/profiles/Dmgr02 & /opt/IBM/WebSphere/AppServer/profiles/AppSrv01
c) Get the admin console ports from AboutThisProfile.txt or serverindex.xml file for dmgr
d) Start the DMgr, Nodeagent and the server1
e) Check the logs for errors
=====================================================================================
=====================================================================================
Custom Profile
1) A custom profile defines an empty node on a system.
2) The main purpose of this profile is to define a node on a system which can be federated to a cell for management using the DMGR.
3) This profile needs to be federated to the dmgr cell during the profile creation or later using “./addNode.sh dmgr_host soap_port”
4) Before you can federate the custom profile to a cell, you will need to have a running deployment manager.
Steps to create a Custom Profile
Step1 : Navigate to WAS_HOME/bin directory
| [root@mercury MyServer]# cd /opt/IBM/WebSphere/AppServer/bin |
Execute ./manageprofile.sh
| [root@mercury bin]# ./manageprofiles.sh -create -defaultPorts -profileName Custom01 -profilePath /opt/IBM/WebSphere/AppServer/profiles/Custom01 -templatePath /opt/IBM/WebSphere/AppServer/profileTemplates/managed -hostName mercury.com -nodeName mercuryNode01 -federateLater true |
Step2: Checks to ensure proper profile creation
a) Should get an INSTCONSUCCESS message for manageprofile in the <WAS_HOME>/logs/manageprofiles/<ProfileName>_create.log
b) Navigate to the /opt/IBM/WebSphere/AppServer/profiles/Custom01
c) Federate the Custom Profile node to the dmgr cell using “./addNode.sh dmgr_host soap_port”
d) Create Application Servers from the dmgr admin console
=====================================================================================
=====================================================================================
Deployment Manager Profile
1) The DMGR is a single administration in websphere application server,
2) Whenever we create a dmgr by default we will get one node, cell and adminconsole,
3) It is mainly used to do the administrative and configuration activities.
4) The application and cutom server profile has to be federate with the dmgr,
5) Once federation process has been done we can manage the servers from dmgr admin console
Steps to create a Deployment Manager Profile
Step1 : Navigate to WAS_HOME/bin directory
| [root@mercury MyServer]# cd /opt/IBM/WebSphere/AppServer/bin |
Execute ./manageprofile.sh
| [root@mercury bin]# ./manageprofiles.sh -create -profileName Dmgr01 -profilePath /opt/IBM/WebSphere/AppServer/profiles/Dmgr01 -templatePath /opt/IBM/WebSphere/AppServer/profileTemplates/management -serverType DEPLOYMENT_MANAGER -cellName Cell01 -nodeName Dmgr01 -hostName mercury.com -enableAdminSecurity true -adminUserName wasadmin -adminPassword passw0rd |
Step2 : Checks to ensure proper profile creation
a) Should get an INSTCONSUCCESS message for manageprofile in the <WAS_HOME>/logs/manageprofiles/<ProfileName>_create.log
b) Navigate to the /opt/IBM/WebSphere/AppServer/profiles/Dmgr01
c) Start Dmgr using ./startManager.sh from /opt/IBM/WebSphere/AppServer/profiles/Dmgr01/bin
d) Check logs for Error
=====================================================================================
=====================================================================================
Application Server Profile
1) This Profile is used to create a stand alone application server .
2) It will have its independent runtime JVM environment where we can deploy the application etc
3) This Profile can be later federated a DMGR cell to become part of a bigger deployment environment
Steps to create a Application Server Profile
Step1 : Navigate to WAS_HOME/bin directory
| root@mqnode bin]#cd /opt/IBM/WebSphere/AppServer/bin |
Execute ./manageprofile.sh
| [root@mercury bin]# ./manageprofiles.sh -create -profileName MYPROFILE -profilePath /appprofiles/MYPROFILE -templatePath /opt/IBM/WebSphere/AppServer/profileTemplates/default -serverName TEST_SERVER -nodeName MYPROFILENode1 -hostName mercury.com -enableAdminSecurity true -adminUserName wasadmin -adminPassword wasadmin@12 |
Step2: Checks to ensure proper profile creation
a) Should get an INSTCONSUCCESS message for manageprofile in the <WAS_HOME>/logs/manageprofiles/<ProfileName>_create.log
b) Navigate to the profile folder ie /appprofiles/MYPROFILE
c) Start application server using ./startServer.sh TEST_SERVER
d) Check SystemOut.logs for Error
More details on Application Server profile Click here
http://webspherepundit.com/?p=1242
To get automated mail updates of my Posts..
Please subscribe to the site http://webspherepundit.com
And also like the Facebook Page
https://www.facebook.com/webspherepundit