Useful WebSphere 8 Install Scripts

22 Oct 2012

October 22, 2012

Useful WebSphere 8 Install Scripts

October 22, 2012 Blog, Middleware Training, WebSphere, WebSphere Application Server 0 Comment

Some useful command line scripts to help with Installing WebSphere Application Server 8 using IBM Installation Manager. Creating profiles using manageprofiles command line utility.

Record a WebSphere 8 install and generate an XML response file

./IBMIM -skipInstall /tmp/iimRegistry3 -record /var/apps/responsefiles/was8nd_silent.xml

1	./IBMIM -skipInstall /tmp/iimRegistry3 -record /var/apps/responsefiles/was8nd_silent.xml

Install WebSphere Application Server 8 ND using command-line and recorded response file

./IBMIM --launcher.ini silent-install.ini -input /var/apps/responsefiles/was8nd_silent.xml -log /var/apps/responsefiles/was8nd_silent_log.xml -acceptLicense

1	./IBMIM --launcher.ini silent-install.ini -input /var/apps/responsefiles/was8nd_silent.xml -log /var/apps/responsefiles/was8nd_silent_log.xml -acceptLicense

Verify install

/opt/IBM/WebSphere/AppServer/bin/versionInfo.sh

1	/opt/IBM/WebSphere/AppServer/bin/versionInfo.sh

Delete a profile using manageprofiles

/opt/IBM/WebSphere/AppServer/bin/manageprofiles.sh -listProfiles

/opt/IBM/WebSphere/AppServer/bin/manageprofiles.sh -delete -profileName Dmgr01

/opt/IBM/WebSphere/AppServer/bin/manageprofiles.sh -listProfiles

/opt/IBM/WebSphere/AppServer/bin/manageprofiles.sh -delete -profileName Dmgr01

Creating a Deployment Manager Profile and Two Nodes (managed profiles)

#Deployment Manager
export WAS_BINARY_DIR="/opt/IBM/WebSphere/AppServer"
export PROFILE_NAME="Dmgr01_Prof"
export WAS_PROFILE_DIR="/var/apps/was8nd/profiles"
export CELL_NAME="Cell01"
export HOST="localhost"
export NODE_NAME="Cell01Dmgr01"
export START_PORT="10000"
export DMGR_ADMIN_USER="wasadmin"
export DMGR_ADMIN_PASSWORD="wasadmin"
${WAS_BINARY_DIR}/bin/manageprofiles.sh -create -profileName ${PROFILE_NAME} -profilePath ${WAS_PROFILE_DIR}/${PROFILE_NAME} -templatePath ${WAS_BINARY_DIR}/profileTemplates/management -serverType DEPLOYMENT_MANAGER -cellName ${CELL_NAME} -hostName ${HOST} -nodeName ${NODE_NAME} -startingPort ${START_PORT} -isDefault -enableAdminSecurity true -adminUserName ${DMGR_ADMIN_USER} -adminPassword ${DMGR_ADMIN_PASSWORD}

#Node Agent 01
#Use a unique name even though you plan to federate the custom profile or stand alone profile into a deployment manager cell.
export WAS_BINARY_DIR="/opt/IBM/WebSphere/AppServer"
export PROFILE_NAME="Node01_Prof"
export WAS_PROFILE_DIR="/var/apps/was8nd/profiles"
export CELL_NAME="Cell01Node01"
export HOST="localhost"
export NODE_NAME="Cell01Node01"
export START_PORT="10100"
export DMGR_ADMIN_USER="wasadmin"
export DMGR_ADMIN_PASSWORD="wasadmin"
export DMGR_SOAP_PORT="10003"
export DMGR_HOST="localhost"
${WAS_BINARY_DIR}/bin/manageprofiles.sh -create -profileName ${PROFILE_NAME} -profilePath ${WAS_PROFILE_DIR}/${PROFILE_NAME} -templatePath ${WAS_BINARY_DIR}/profileTemplates/managed -cellName ${CELL_NAME} -hostName ${HOST} -nodeName ${NODE_NAME} -startingPort ${START_PORT} -dmgrHost ${DMGR_HOST} -dmgrPort ${DMGR_SOAP_PORT} -dmgrAdminUserName ${DMGR_ADMIN_USER} -dmgrAdminPassword ${DMGR_ADMIN_PASSWORD}

#Node Agent 02
#Use a unique name even though you plan to federate the custom profile or stand alone profile into a deployment manager cell.
export WAS_BINARY_DIR="/opt/IBM/WebSphere/AppServer"
export PROFILE_NAME="Node02_Prof"
export WAS_PROFILE_DIR="/var/apps/was8nd/profiles"
export CELL_NAME="Cell01Node02"
export HOST="localhost"
export NODE_NAME="Cell01Node02"
export START_PORT="10200"
export DMGR_ADMIN_USER="wasadmin"
export DMGR_ADMIN_PASSWORD="wasadmin"
export DMGR_SOAP_PORT="10003"
export DMGR_HOST="localhost"
${WAS_BINARY_DIR}/bin/manageprofiles.sh -create -profileName ${PROFILE_NAME} -profilePath ${WAS_PROFILE_DIR}/${PROFILE_NAME} -templatePath ${WAS_BINARY_DIR}/profileTemplates/managed -cellName ${CELL_NAME} -hostName ${HOST} -nodeName ${NODE_NAME} -startingPort ${START_PORT} -dmgrHost ${DMGR_HOST} -dmgrPort ${DMGR_SOAP_PORT} -dmgrAdminUserName ${DMGR_ADMIN_USER} -dmgrAdminPassword ${DMGR_ADMIN_PASSWORD}

#Deployment Manager

export WAS_BINARY_DIR="/opt/IBM/WebSphere/AppServer"

export PROFILE_NAME="Dmgr01_Prof"

export WAS_PROFILE_DIR="/var/apps/was8nd/profiles"

export CELL_NAME="Cell01"

export HOST="localhost"

export NODE_NAME="Cell01Dmgr01"

export START_PORT="10000"

export DMGR_ADMIN_USER="wasadmin"

export DMGR_ADMIN_PASSWORD="wasadmin"

${WAS_BINARY_DIR}/bin/manageprofiles.sh -create -profileName ${PROFILE_NAME} -profilePath ${WAS_PROFILE_DIR}/${PROFILE_NAME} -templatePath ${WAS_BINARY_DIR}/profileTemplates/management -serverType DEPLOYMENT_MANAGER -cellName ${CELL_NAME} -hostName ${HOST} -nodeName ${NODE_NAME} -startingPort ${START_PORT} -isDefault -enableAdminSecurity true -adminUserName ${DMGR_ADMIN_USER} -adminPassword ${DMGR_ADMIN_PASSWORD}

#Node Agent 01

#Use a unique name even though you plan to federate the custom profile or stand alone profile into a deployment manager cell.

export WAS_BINARY_DIR="/opt/IBM/WebSphere/AppServer"

export PROFILE_NAME="Node01_Prof"

export WAS_PROFILE_DIR="/var/apps/was8nd/profiles"

export CELL_NAME="Cell01Node01"

export HOST="localhost"

export NODE_NAME="Cell01Node01"

export START_PORT="10100"

export DMGR_ADMIN_USER="wasadmin"

export DMGR_ADMIN_PASSWORD="wasadmin"

export DMGR_SOAP_PORT="10003"

export DMGR_HOST="localhost"

${WAS_BINARY_DIR}/bin/manageprofiles.sh -create -profileName ${PROFILE_NAME} -profilePath ${WAS_PROFILE_DIR}/${PROFILE_NAME} -templatePath ${WAS_BINARY_DIR}/profileTemplates/managed -cellName ${CELL_NAME} -hostName ${HOST} -nodeName ${NODE_NAME} -startingPort ${START_PORT} -dmgrHost ${DMGR_HOST} -dmgrPort ${DMGR_SOAP_PORT} -dmgrAdminUserName ${DMGR_ADMIN_USER} -dmgrAdminPassword ${DMGR_ADMIN_PASSWORD}

#Node Agent 02

#Use a unique name even though you plan to federate the custom profile or stand alone profile into a deployment manager cell.

export WAS_BINARY_DIR="/opt/IBM/WebSphere/AppServer"

export PROFILE_NAME="Node02_Prof"

export WAS_PROFILE_DIR="/var/apps/was8nd/profiles"

export CELL_NAME="Cell01Node02"

export HOST="localhost"

export NODE_NAME="Cell01Node02"

export START_PORT="10200"

export DMGR_ADMIN_USER="wasadmin"

export DMGR_ADMIN_PASSWORD="wasadmin"

export DMGR_SOAP_PORT="10003"

export DMGR_HOST="localhost"

${WAS_BINARY_DIR}/bin/manageprofiles.sh -create -profileName ${PROFILE_NAME} -profilePath ${WAS_PROFILE_DIR}/${PROFILE_NAME} -templatePath ${WAS_BINARY_DIR}/profileTemplates/managed -cellName ${CELL_NAME} -hostName ${HOST} -nodeName ${NODE_NAME} -startingPort ${START_PORT} -dmgrHost ${DMGR_HOST} -dmgrPort ${DMGR_SOAP_PORT} -dmgrAdminUserName ${DMGR_ADMIN_USER} -dmgrAdminPassword ${DMGR_ADMIN_PASSWORD}

Windows equivlent’s

IBMIM -skipInstall /tmp/iimRegistry3 -record c:\scripts\was8nd_silent.xml

IBMIM --launcher.ini silent-install.ini -input c:\scripts\was8nd_silent.xml -log c:\scripts\was8nd_silent_log.xml -acceptLicense

IBMIM --launcher.ini silent-install.ini -input "C:\Program Files (x86)\IBM\WebSphere\AppServer\uninstall\uninstall.xml" -log c:\scripts\was8nd_uninstall_log.xml

If you use Programs files, it is a virtual folder and so makes it hard to run command lines in windows 7 from %comspec% cmd prompts. Best to use the following:

IBMIM --launcher.ini silent-install.ini -input "C:\was8nd\AppServer\uninstall\uninstall.xml" -log c:\scripts\was8nd_uninstall_log.xml

C:\was8nd\AppServerbin\versionInfo.bat

C:\was8nd\AppServerbin\manageprofiles.bat -listProfiles

C:\was8nd\AppServerbin\manageprofiles.bat -delete -profileName Dmgr01

@REM Windows
echo Deployment Manager
set WAS_BINARY_DIR=C:\was8nd
set PROFILE_NAME=Dmgr01_Prof
set WAS_PROFILE_DIR=C:\was8nd\profiles
set CELL_NAME=Cell01
set HOST=localhost
set NODE_NAME=Cell01Dmgr01
set START_PORT=10000
set DMGR_ADMIN_USER=wasadmin
set DMGR_ADMIN_PASSWORD=wasadmin
%WAS_BINARY_DIR%\bin\manageprofiles.bat -create -profileName %PROFILE_NAME% -profilePath "%WAS_PROFILE_DIR%\%PROFILE_NAME%" -templatePath "%WAS_BINARY_DIR%\profileTemplates\management" -serverType DEPLOYMENT_MANAGER -cellName %CELL_NAME% -hostName %HOST% -nodeName %NODE_NAME% -startingPort %START_PORT% -isDefault -enableAdminSecurity true -adminUserName %DMGR_ADMIN_USER% -adminPassword %DMGR_ADMIN_PASSWORD%

@REM Windows
echo Node Agent 01
echo Use a unique name even though you plan to federate the custom profile or stand alone profile into a deployment manager cell.
set WAS_BINARY_DIR=C:\was8nd
set PROFILE_NAME=Node01_Prof
set WAS_PROFILE_DIR=C:\was8nd\profiles
set CELL_NAME=Cell01Node01
set HOST=localhost
set NODE_NAME=Cell01Node01
set START_PORT=10100
set DMGR_ADMIN_USER=wasadmin
set DMGR_ADMIN_PASSWORD=wasadmin
set DMGR_SOAP_PORT=10003
set DMGR_HOST=localhost
%WAS_BINARY_DIR%\bin\manageprofiles.bat -create -profileName %PROFILE_NAME% -profilePath "%WAS_PROFILE_DIR%\%PROFILE_NAME%" -templatePath "%WAS_BINARY_DIR%\profileTemplates\managed" -cellName %CELL_NAME% -hostName %HOST% -nodeName %NODE_NAME% -startingPort %START_PORT% -dmgrHost %DMGR_HOST% -dmgrPort %DMGR_SOAP_PORT% -dmgrAdminUserName %DMGR_ADMIN_USER% -dmgrAdminPassword %DMGR_ADMIN_PASSWORD%

@REM Windows
echo Node Agent 02
echo Use a unique name even though you plan to federate the custom profile or stand alone profile into a deployment manager cell.
set WAS_BINARY_DIR=C:\was8nd
set PROFILE_NAME=Node02_Prof
set WAS_PROFILE_DIR=C:\was8nd\profiles
set CELL_NAME=Cell01Node02
set HOST=localhost
set NODE_NAME=Cell01Node02
set START_PORT=10200
set DMGR_ADMIN_USER=wasadmin
set DMGR_ADMIN_PASSWORD=wasadmin
set DMGR_SOAP_PORT=10003
set DMGR_HOST=localhost
%WAS_BINARY_DIR%\bin\manageprofiles.bat -create -profileName %PROFILE_NAME% -profilePath "%WAS_PROFILE_DIR%\%PROFILE_NAME%" -templatePath "%WAS_BINARY_DIR%\profileTemplates\managed" -cellName %CELL_NAME% -hostName %HOST% -nodeName %NODE_NAME% -startingPort %START_PORT% -dmgrHost %DMGR_HOST% -dmgrPort %DMGR_SOAP_PORT% -dmgrAdminUserName %DMGR_ADMIN_USER% -dmgrAdminPassword %DMGR_ADMIN_PASSWORD%

&nbsp;

IBMIM -skipInstall /tmp/iimRegistry3 -record c:\scripts\was8nd_silent.xml

IBMIM --launcher.ini silent-install.ini -input c:\scripts\was8nd_silent.xml -log c:\scripts\was8nd_silent_log.xml -acceptLicense

IBMIM --launcher.ini silent-install.ini -input "C:\Program Files (x86)\IBM\WebSphere\AppServer\uninstall\uninstall.xml" -log c:\scripts\was8nd_uninstall_log.xml

If you use Programs files, it is a virtual folder and so makes it hard to run command lines in windows 7 from %comspec% cmd prompts. Best to use the following:

IBMIM --launcher.ini silent-install.ini -input "C:\was8nd\AppServer\uninstall\uninstall.xml" -log c:\scripts\was8nd_uninstall_log.xml

C:\was8nd\AppServerbin\versionInfo.bat

C:\was8nd\AppServerbin\manageprofiles.bat -listProfiles

C:\was8nd\AppServerbin\manageprofiles.bat -delete -profileName Dmgr01

@REM Windows

echo Deployment Manager

set WAS_BINARY_DIR=C:\was8nd

set PROFILE_NAME=Dmgr01_Prof

set WAS_PROFILE_DIR=C:\was8nd\profiles

set CELL_NAME=Cell01

set HOST=localhost

set NODE_NAME=Cell01Dmgr01

set START_PORT=10000

set DMGR_ADMIN_USER=wasadmin

set DMGR_ADMIN_PASSWORD=wasadmin

%WAS_BINARY_DIR%\bin\manageprofiles.bat -create -profileName %PROFILE_NAME% -profilePath "%WAS_PROFILE_DIR%\%PROFILE_NAME%" -templatePath "%WAS_BINARY_DIR%\profileTemplates\management" -serverType DEPLOYMENT_MANAGER -cellName %CELL_NAME% -hostName %HOST% -nodeName %NODE_NAME% -startingPort %START_PORT% -isDefault -enableAdminSecurity true -adminUserName %DMGR_ADMIN_USER% -adminPassword %DMGR_ADMIN_PASSWORD%

@REM Windows

echo Node Agent 01

echo Use a unique name even though you plan to federate the custom profile or stand alone profile into a deployment manager cell.

set WAS_BINARY_DIR=C:\was8nd

set PROFILE_NAME=Node01_Prof

set WAS_PROFILE_DIR=C:\was8nd\profiles

set CELL_NAME=Cell01Node01

set HOST=localhost

set NODE_NAME=Cell01Node01

set START_PORT=10100

set DMGR_ADMIN_USER=wasadmin

set DMGR_ADMIN_PASSWORD=wasadmin

set DMGR_SOAP_PORT=10003

set DMGR_HOST=localhost

%WAS_BINARY_DIR%\bin\manageprofiles.bat -create -profileName %PROFILE_NAME% -profilePath "%WAS_PROFILE_DIR%\%PROFILE_NAME%" -templatePath "%WAS_BINARY_DIR%\profileTemplates\managed" -cellName %CELL_NAME% -hostName %HOST% -nodeName %NODE_NAME% -startingPort %START_PORT% -dmgrHost %DMGR_HOST% -dmgrPort %DMGR_SOAP_PORT% -dmgrAdminUserName %DMGR_ADMIN_USER% -dmgrAdminPassword %DMGR_ADMIN_PASSWORD%

@REM Windows

echo Node Agent 02

echo Use a unique name even though you plan to federate the custom profile or stand alone profile into a deployment manager cell.

set WAS_BINARY_DIR=C:\was8nd

set PROFILE_NAME=Node02_Prof

set WAS_PROFILE_DIR=C:\was8nd\profiles

set CELL_NAME=Cell01Node02

set HOST=localhost

set NODE_NAME=Cell01Node02

set START_PORT=10200

set DMGR_ADMIN_USER=wasadmin

set DMGR_ADMIN_PASSWORD=wasadmin

set DMGR_SOAP_PORT=10003

set DMGR_HOST=localhost

%WAS_BINARY_DIR%\bin\manageprofiles.bat -create -profileName %PROFILE_NAME% -profilePath "%WAS_PROFILE_DIR%\%PROFILE_NAME%" -templatePath "%WAS_BINARY_DIR%\profileTemplates\managed" -cellName %CELL_NAME% -hostName %HOST% -nodeName %NODE_NAME% -startingPort %START_PORT% -dmgrHost %DMGR_HOST% -dmgrPort %DMGR_SOAP_PORT% -dmgrAdminUserName %DMGR_ADMIN_USER% -dmgrAdminPassword %DMGR_ADMIN_PASSWORD%

Silent WebSphere Install

Leave a Reply Cancel reply

You must be logged in to post a comment.

WebSphere Application Server 8.5.5.x – Advanced Security Course

The WebSphere Application Server 8.5.5.x – Advanced Security Concepts course provides the student with a detailed example-based guide which takes the student through how to configure Global Security for a Standalone Repository for the express purpose of connecting WAS to Microsoft AD, and enabling Full Single Sign on. This course covers how to set up Windows 2012 Server as a Primary Domain Controller and enabled a Windows 8.1 workstation as part of the full-enabling and testing of a fully functioning SSO solution. Included in this course are Jython and shell scripts and even a Java Web Application that is used to prove that SSO is indeed working as intended

WebSphere Message Broker 8 Administration

Here the student learns through examples, one step at a time, the power of WebSphere Message Broker 8.0 an advanced ESB product from IBM.

WAS 8.5.5.x Essential Security Course

Only $149.99 Learn how to configure SSL for both WAS and IBM HTTP Server. Learn SSL insights not previously made available. Implement LDAP configurations using open source products. Automate Global Security configuration using Jython

WAS 8.5.5 Application Client Cookbook

This course was produced because I had many members of the public asking for support on how to connect an Application Client (Java client) to a secure WebSphere Application Server.

2015 ALL Courses – Bargain Bucket

This page provides the facility to purchase an elite membership, which grants you full access to all products published before and during 2015. You get perpetual access and access to the current courses.

WebSphere 8.5.5 Automation Course

WAS 8.5.5 Automation Course Do you need to save time automating manual WAS tasks? Have you ever wondered how to automate IBM Installation Manager? Ever needed to automate the installation of WAS 8.5.5.x and automate Upgrades and Roll-backs? The WebSphere Application Server 8.5.5.x Automation Course provides the student with a full set of guides and a set of commercial-grade automation scripts with detailed worked-examples.

All 2014 Courses – Bargain Box

This page provides the facility to purchase an elite membership, which grants you full access to all products published before 2015. You get perpetual access and access to the current courses. As of 2014, there are 9 courses.

WebSphere Application Server 8.5 Administration course

WAS 8.5 Administration Course This course provides the student with the necessary skills to handle all sorts of administrative tasks on WebSphere Application Server Network Deployment version 8.5. The course material is practical and “hands-on” and covers a wide range of topics derived from industry experience. We have designed this course to include all the necessary instructions to install the product, try out various administrative tasks and can be used easily to refresh your knowledge after the course has been attended. The course also contains over 900 pages of “How To” guides and more than 300 Power Point slides along with Labs, resources and questions and answers.

WebSphere Portal 8 Administration Basics Course

IBM Portal 8 Administration Course

WebSphere 8.5 Performance Tuning Course

WAS 8.5 Performance Tuning Course This course provides students with the tools and techniques to tune the performance of WebSphere Application Server Network Deployment Version 8.5 (WAS ND 8.5) As typical of all our middleware courses, the course material follows a “Do-it-yourself” approach and provides all the necessary instructions and sample code to setup your lab, try out tuning tasks and learn. In short, this course is a highly practical course which teaches performance tuning by example. Something unique about this course is the 145 slide Power Point pack which covers WebSphere Performance Tuning best practices and theory.

Leave a Reply Cancel reply

Article Categories