Manage Profile command

Manage profile command is a command line tool that you can use for either creating, delete, list, setting default profile. The Profile Management tool makes use of this tool for actual profile creation.

You can execute the manageprofile.sh from was_home/bin directory and you can use it for following things

• Create profile: You can create a profile by using a command like this
  
manageprofiles -create -profileName profile_name -profilePath fullyqualified_profilepath -templatePath
fullyqualified_profile_templatepath -nodeName node_name -cellName cell_name
-hostName host_name

  


• Delete profile:Removing a profile is multi step process and the exasct steps depend on the type of profile that your trying to delete. But the basic idea is first remove the node and then go to profile_home/bin and execute manageprofile -delete command to delete the profile and then execute manageprofiles -validateAndUpdateRegistry command to clean the profile registry
  

profileRegistry.xml file

Each profile you create is registered in a profile registry: <was_home>/properties/profileRegistry.xml


This is sample profileRegistry.xml file from my machine

<?xml version="1.0" encoding="UTF-8"?>
<profiles>
<profile isAReservationTicket="false" isDefault="true" name="Dmgr01" path="C:\Cert\WebSphere\AppServer\profiles\Dmgr01" template="C:\Cert\WebSphere\AppServer\profileTemplates\cell\dmgr"/>
<profile isAReservationTicket="false" isDefault="false" name="AppSrv01" path="C:\Cert\WebSphere\AppServer\profiles\AppSrv01" template="C:\Cert\WebSphere\AppServer\profileTemplates\cell\default"/>
</profiles>



Creating custom profile

A custom profile defines an empty node on a system. The purpose of this profile is to define a node on a system to be federated to a cell for central management. As you create the profile, you will have the option to federate the node to a cell during the wizard, or to simply create the profile for later federation. Before you can federate the custom profile to a cell, you will need to have a running deployment manager.

You might want to create a custom profile when your end goal is create cluster, Lets say if you want to create a horizontal cluster on 3 machines then you might want to create Application Server profile on Machine 1 and custom profile on Machine 2 and 3. Then you can configure application server on Machine 1 and use it as a template for creating cluster and add Machine 2 and Machine 3 nodes in the cluster. The WAS process will take care of creating application servers based on your machine 1 configuration on other 2 machines.

Follow the Profile Management wizard to create custom profile like this








If you dont want to federate the node at the time of profile creation Check the "Federate this node later" checkbox

Profile Management Tool(PMT)

Profile Management tool is a GUI tool that you can use to create profile, You can launch it in following ways

• By going to was_home/bin/ProfileManagement/pmt.bat command


• In case of windows environment by going to Start - programs - IBM WebSphere - Application Server Network deployment v6.1 - profile management


• As a part of installation program select the launch Profile Management tool on the last page

Irrespective of how you launch the PMT tool this is the second screen that you get and rest of flow depends on type of profile that you want to create

Creating profile

You have three options to choose from for creating a profile

• Installation Time: You can create a profile as part of installation process, the installation wizard lets to you decide what type of profile you want to create


• Profile Management Tool: You can launch profile management tool, which is GUI program by executing to was_home/bin/ProfileManagement/pmt.bat. Once PMT is launch you can use the wizard to create type of profile that you want. PMT is used only for creating profile


• Manage profile command line tool: You can use manage profile command line tool to either create or delete a profile

Installation Verification Tool

Installation Verification tool(IVT) can be used to verify the installation of product and the Application server or Deployment manager profile. You can run the Install verification tool after installing product (With either DMGR or AppServer) profile, or after creating DMGR or AppServer profile. The IVT tool makes sure that the server process can start.


The install verification tool works differently depending on the type of profile that your verifying, If you are trying to verify a Deployment Manager, it will check that if DMGR is started if not it will start the DMGR and check if there are any errors in SystemOut.log or SystemErr.log.




If your trying to verify application server profile then it will check if the application server is started, if not start it. Once the server is started it will make requests to ivt servlet to verify that it can respond to request for servlet, JSP and EJB. In addition to that it will scan SystemOut.log and SystemErr.log to make sure that there are no errors.



No installation verification is possible for a custom profile. After federating the node and using the deployment manager to create a server, you can start the server process to verify its functionality.