websphere

Remember about the config directory in the profile;
..................................................

There is a config directory in application server profile

vikas/IBM/WebSphere/AppServer/profiles/AppSrv01/config/cells





To create  a profile We need to go to the WAS root bin directory.

/vikas/IBM/WebSphere/AppServer/Bin

ls
Here in bin directory we see all the files such as.
Was root belongs to all the profiles.

  1. addnode.sh  ----> this is used to add a node to the deployment manager.
  
   This command will allow us to add a node to dMGR
   If i want to add the application server to deployment manager , then i have to use the
   add node command.

   2. If i want to start a server --  startserver.sh
                               
                                   stopserver.sh

    In 6.1  if i want to create any profiles from command prompt.. 
    i have to use    manageprofiles.sh

   3. ./manageprofiles.sh   ---> To create any profile we use this command.
    
    This is a executable file.
    
    ./manageprofiles.sh -help
     
    then it will help you to create the profiles. 
  
   4.  Creating a DMGR profile.
     ./manageprofiles.sh -create -help
      

   4.a.   While creating we see a profile template directory in the Was root.

      vikas/IBM/WebSphere/AppServer/profileTemplates/

   4.b. The Template names are: cell default dmgr  managed

     SO we have to give this name to create a profile

     so let us start again.....

   ./manageprofiles.sh -create -templatePath              <<<<<<<<<<<<<<<<

     /texas1/IBM/WebSphere/AppServerprofileTemplates/dmgr -profileName Dmgr01

    -profilePath /vikas/IBM/WebSphere/profiles/Dmgr01          <<<<<<<<<<<<<<<<<



  This is the way to create a profile.

  Now we can tail the installaton.

  There is alog directory in the was root that creates log files while installation.

  In was root directory there is a log directory.

  In that directory , there is a manage profiles.
  
  vikas/IBM/WebSPhere/AppServer/logs/manageprofiles    <<<<<<<<<<<<

   6. We see Dmgr01_create.log file here 

    Now do 
    
    tail -f Dmgr01_create.log                   <<<<<<<<<<<<<

   We can see the installation of the profile and all.

  
   If we see INTCONFSUCCESS in the log profile.

  After creating the profile we need to see the serverindex.xml file <<<<<

   To get the information about the port numbers.
  
   Now...
   vikas/IBM/WebSphere/AppServer/profiles/Dmgr01

   We can create any number of profiles using one instance of Application server 

   using one instance of Application Server.

       vikas/IBM/WebSphere/AppServer/profiles/Dmgr01/config/cells/was1Cell02/nodes/was1CellManager01/servers


The above is the path for the location of the serverindex.xml  <<<<<

We can see the profiles port number

WC_adminhost

the port number is 9060.                               <<<<<<<<<

   We can even give default port number by using 
  -port   at the end of manage profiles    <<<<<<<<<<

  The Default port number for the WSAS is 9060

  The Default secured port number is 9043
  

  The command to start the Deployment Manager


  The command to start the Server is ./startServer.sh    <<<<<<<<<<<<<

  The command to start the DMGR is ./startManager.sh     <<<<<<<<<<<<<

  We have to go to DMGR Bin directory and do startManager.sh or stopManager.sh to stop the DMGR

  __________________

  How to check if a java process is up or down.

  ps -ef|grep java

  When we do this grep java in dmgr bin directory it shows weather it is running or not.

  At the end of the file we see ger01 dmgr.... which means that it is running.

  _______________

  Now go to application Server bin directory.

  wasroot-/AppServer/profiles/AppSrv01/bin

  Now do

  ./startServer.sh server1

Now we see that it is running.

    Before uninstaling the Any Application Server we need to stop the Servers.

   ______________________

To find the servers are up or down.. we check

ps -ef |grep java

or else.. we can go to the AppServer /bin    <<<<<<<<<<

Then do ./serverStatus.sh -all               <<<<<<<<<<<<<<

   
   @ Version info---
   
   To find which version of the application server we have installed .

   We need to go to the was root bin and then do.

   ./versionInfo.sh                           <<<<<<<<<<<<<<<<<<<<<<<<<

   In the was root bin directory.

________________________________________________

   ______________________________
   |                            |
   |       UNINSTALLATION       |
   |                            | 
   |____________________________|

   To uninstall the WSAS we need to stop all the processes and profiles that are running.

   To check  which processes are up we check as follows.
   
   In WAS root bin directory.

   ps -ef|grep java        <<<<<<<<<<<<<<

   We see all the processes that are up

   We can do kill -9    

   or go to The particular profiles bin directory and do.

   stopserver.sh    <<<<<<<<<  for application server

   stopManager.sh               <<<<<<<<<<<<<    for DMGR

   ---  After all the processes are down then check again by the folowing command


   ps -ef|grep java  in was root  directory.

   Now go to the WAS ROOT and do ls
     
   go to uninstall directory

    now ... uninstall the application server

   cd uninstall/
    
    Now we are in vikas/IBM/WebSphere/AppServer/uninstall

    ./uninstall -silent

    ---- Now if we want to tail it

  go to root
  cd /tmp
  cd niflogs
  tail -f log.txt

It doesnt remove all the files.. we need to remove them manually.

   go to root and do

   rm rf vikas/                     <<<<<<<<<<<<<<<<< 

   
   


   



/Vikas/IBM/WebSphere/AppServer/profiles/Appsrv01/config/cells/wasCell01/nodes/wasNode01/server1

The above path shows us that :

Cell ----->contain multiple nodes.. ---->nodes contain multiple servers.

The Application server profile contains a default server called server1.