Creating DMGR & Two Managed Profile $ Federating Nodes To DMGR

 In this example I will be creating DMGR, Managed profiles in three different machines/Server/VM.  DMGR Profile will be created on devserver02 server.  Managed (AppSrv01) Profile will be created on devserver03 server. Managed (Custom01) Profile will be created on devserver04 server. Then this Managed nodes will be federated to the DMGR console. Now we can manage the nodes through DMGR Admin Console. Let see how to create this environment on Linux OS.




 1. Create DMGR Profile

# hostname

devserver02

# pwd

 /opt/IBM/WebSphere/AppServer/bin

# ./manageprofiles.sh -create -profileName Dmgr01 -profilePath /opt/IBM/WebSphere/AppServer/profiles/Dmgr01 -templatePath /opt/IBM/WebSphere/AppServer/profileTemplates/dmgr -nodeName dmgrNode01 -cellName dmgrNode01Cell

CWMBU0002I: The deployment manager profile template has been deprecated and replaced by the management profile template with a deployment manager server.

INSTCONFSUCCESS: Success: Profile Dmgr01 now exists. Please consult /opt/IBM/WebSphere/AppServer/profiles/Dmgr01/logs/AboutThisProfile.txt for more information about this profile.




2. Create Managed Profile On Host "devserver03". 

# hostname

devserver03

# pwd

/opt/IBM/WebSphere/AppServer/bin

# ./manageprofiles.sh -create -profileName AppSrv01 -profilePath /opt/IBM/WebSphere/AppServer/profiles/AppSrv01 -templatePath /opt/IBM/WebSphere/AppServer/profileTemplates/managed -nodeName devserver03Node01 -cellName devserver03Node01cell

INSTCONFSUCCESS: Success: Profile AppSrv01 now exists. Please consult /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/logs/AboutThisProfile.txt for more information about this profile.


3. Create Managed Profile On Host "devserver04". 

[root@devserver04 bin]# hostname

devserver04

# pwd

/opt/IBM/WebSphere/AppServer/bin

# ./manageprofiles.sh -create -profileName Custome01 -profilePath /opt/IBM/WebSphere/AppServer/profiles/Custom01 -templatePath /opt/IBM/WebSphere/AppServer/profileTemplates/managed -nodeName devserver04Node01 -cellName devserver04Node01cell

INSTCONFSUCCESS: Success: Profile Custome01 now exists. Please consult /opt/IBM/WebSphere/AppServer/profiles/Custom01/logs/AboutThisProfile.txt for more information about this profile.



4. Start the DMGR on server "devserver02"

# pwd

/opt/IBM/WebSphere/AppServer/profiles/Dmgr01/bin

# ./startManager.sh




5. Federate AppSrv01/devserver03Node01 Node to DMGR Profile/Console, While federating node to dmgr, nodeagent will be started automatically.

# hostname

devserver03

# pwd

/opt/IBM/WebSphere/AppServer/profiles/AppSrv01/bin

# ./addNode.sh devserver02 8879




6. Federate Custome01/devserver04Node01 Node to DMGR Profile/Console, While federating node to dmgr, nodeagent will be started automatically.

# hostname

devserver04

# pwd

/opt/IBM/WebSphere/AppServer/profiles/Custome01/bin

# ./addNode.sh devserver02 8879




7. Login to DMGR console and validate Nodes have been federated. 







8. Nodeagent is running on both the nodes.




Comments

Post a Comment

Popular posts from this blog

 Completed Installation Steps for WAS Version 9 IM Installation: unzip agent.installer.lnx.gtk.x86_64_1.8.5.zip ./installc -acceptLicense -sVP -installationDirectory /opt/IBM/InstallationManager/eclipse Verify the Installation Mnager version /opt/IBM/InstallationManager/eclipse/tools/imcl -version List the Available Package for WASND & SDK8: /opt/IBM/InstallationManager/eclipse/tools/imcl listAvailablePackages -repositories /mnt/package/WAS/repository.xml /opt/IBM/InstallationManager/eclipse/tools/imcl listAvailablePackages -repositories /mnt/package/SDK9/repository.xml Install WASND9 along with SDK8: Note: With out SDK installation will not be performed. ./imcl install com.ibm.websphere.ND.v90_9.0.0.20160526_1854 com.ibm.java.jdk.v8_8.0.3000.20160623_1418 -repositories /opt/IBM/package/WASND9/,/opt/IBM/package/WASSDK/  -installationDirectory /opt/IBM/WebSphere/AppServer -sVP -sharedResourcesDirectory /opt/IBM/IMShared/ -installFixes recommended -acceptLicense -showProgress DMGR Pr
Read more

SSL certificate in WebSphere Application Server

  Here are the step-by-step instructions for renewing an SSL certificate in WebSphere Application Server: 1. Generate a Certificate Signing Request (CSR): * Locate your existing private key and note its location. * Open a command prompt or terminal and navigate to the WebSphere Application Server installation directory. * Run the following command to generate a new CSR: php Copy code keytool -certreq -keyalg RSA -alias < alias_name > -file < csr_file_path > -keystore < keystore_file_path > Replace <alias_name> with the alias of the private key entry, <csr_file_path> with the path where you want to save the CSR file, and <keystore_file_path> with the path to your keystore file. 2. Submit the CSR to a Certificate Authority (CA): * Go to your chosen CA's website or portal and navigate to the certificate renewal section. * Follow the CA's instructions for submitting a CSR and complete any required validation steps. * Submit the CSR fil
Read more

Tomcat Upgrade Steps on Windows.

  Tomcat  Upgrade Steps on Windows. 1, Stop the older version of  Tomcat  service 2, Disable the service 3. Install the new  tomcat  version 4, backup the root webapps index file 5, copy the applications folder to webapps 6, compare the server.xml from older to new and then update the server.xml file in  tomcat  lates version 7, Add factory setting for password encryption in  tomcat  server.xml 8, copy the lib jar files to new  tomcat  lib 9, Edit the  tomcat  properties, JVM, JAVA Class path, JAVA Options, Initial memory pool, Maximum memory pool and local system account 10, Make it automatic and start the new  tomcat  service 11, Make sure application is woking after application team validation 12, uninstall the older version of  tomcat  and make sure you don't delete the folders. Note : These are the steps to be coordinated with application team, and make sure application compatible with the upgraded version during the planning phase. 
Read more