Installing Standalone Application Server, Creating Standalone Application Profiles And Deleting Standalone Application profile

  Profile Creations In WebSphere Application Server

Creating Standalone Application Server Profile: 

What is standalone application server profile ?

Each standalone application server profile includes a server1 application server process. Each profile defines a separate standalone application server that has its own administrative interface (Admin Console)

1. To Create a standalone profile, go to WAS Installed bin directory.

# cd /opt/IBM/WebSphere/AppServer/bin

# ./manageprofiles.sh -create -profileName AppSrv01 -profilePath /opt/IBM/WebSphere/AppServer/profiles/AppSrv01 -templatePath /opt/IBM/WebSphere/AppServer/profileTemplates/default



2. Verify post profile creation of standalone profile from the logs, look for "INSTCONFSUCCESS"

# grep -i INSTCONFSUCCESS /opt/IBM/WebSphere/AppServer/logs/manageprofiles/AppSrv01_create.log


3. Start the JVM by using below command.

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

# ./startServer.sh


4. How to Check Status of Standalone Application Server

#cd /opt/IBM/WebSphere/AppServer/bin

#  ./serverStatus.sh -all

5. Loginto Admin Console using port no. 9043 

https://localhost:9043/ibm/console

After loginto Admin Console like this




6. Deploy a EAR file from Admin console.


Delete Standalone Application Server Profile

1. Stop the JVM by using below command. 

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

# ./stopServer.sh


2. Listing  Available Profiles

#cd /opt/IBM/WebSphere/AppServer/bin

#  ./manageprofiles.sh -listProfiles

3. Delete the profile by using 

# cd /opt/IBM/WebSphere/AppServer/bin

# ./manageprofiles.sh -delete -profileName AppSrv01





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