Sunday, 4 September 2016

Tinkering with WebSphere Application Server v9 - Part Two

Following on from my earlier post: -


I've made much better progress with WAS 9, which is nice :-)

So here's my installation response file: -

installWAS9.rsp 

<?xml version='1.0' encoding='UTF-8'?>
<agent-input>
  <server>
    <repository location='/tmp/im' temporary='true'/>
    <repository location='/tmp/was' temporary='true'/>
    <repository location='/tmp/java' temporary='true'/>
  </server>
  <profile id='IBM Installation Manager' installLocation='/opt/IBM/InstallationManager/eclipse' kind='self'>
    <data key='eclipseLocation' value='/opt/IBM/InstallationManager/eclipse'/>
    <data key='user.import.profile' value='false'/>
    <data key='cic.selector.os' value='linux'/>
    <data key='cic.selector.arch' value='x86_64'/>
    <data key='cic.selector.ws' value='gtk'/>
    <data key='cic.selector.nl' value='de,no,fi,ru,hr,fr,hu,sk,sl,sv,ko,el,en,pt_BR,it,iw,zh,es,cs,ar,zh_HK,zh_TW,th,ja,pl,da,tr,nl'/>
  </profile>
  <profile id='IBM WebSphere Application Server V9.0' installLocation='/opt/IBM/WebSphere/AppServer'>
    <data key='cic.selector.arch' value='x86_64'/>
  </profile>
  <install>
    <offering id='com.ibm.cic.agent' version='1.8.5000.20160506_1125' profile='IBM Installation Manager' features='agent_core,agent_jre' installFixes='none'/>
    <offering profile='IBM WebSphere Application Server V9.0' id='com.ibm.websphere.BASE.v90' version='9.0.0.20160526_1854' features='core.feature,ejbdeploy,thinclient,embeddablecontainer,samples'/>
    <offering profile='IBM WebSphere Application Server V9.0' id='com.ibm.java.jdk.v8' version='8.0.3000.20160526_1317' features='com.ibm.sdk.8'/>
  </install>
  <preference name='com.ibm.cic.common.core.preferences.eclipseCache' value='/opt/IBM/IMShared'/>
</agent-input>


from which I installed the IBM Installation Manager (IIM), WAS and Java binaries: -

/tmp/im/tools/imcl -input installWAS9.rsp -acceptLicense
Installed com.ibm.cic.agent_1.8.5000.20160506_1125 to the /opt/IBM/InstallationManager/eclipse directory.
Installed com.ibm.websphere.BASE.v90_9.0.0.20160526_1854 to the /opt/IBM/WebSphere/AppServer directory.
Installed com.ibm.java.jdk.v8_8.0.3000.20160526_1317 to the /opt/IBM/WebSphere/AppServer directory.

and then verified: -

/opt/IBM/InstallationManager/eclipse/tools/imcl listInstalledPackages -long -features

/opt/IBM/InstallationManager/eclipse : com.ibm.cic.agent_1.8.5000.20160506_1125 : IBM® Installation Manager : 1.8.5 : 
/opt/IBM/WebSphere/AppServer : com.ibm.java.jdk.v8_8.0.3000.20160526_1317 : IBM SDK, Java Technology Edition, Version 8 : 8.0.3.0 : 
/opt/IBM/WebSphere/AppServer : com.ibm.websphere.BASE.v90_9.0.0.20160526_1854 : IBM WebSphere Application Server  : 9.0.0.0 : ejbdeploy,embeddablecontainer,samples,thinclient


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

<snip>
Name                  IBM WebSphere Application Server
Version               9.0.0.0
ID                    BASE
Build Level           gm1621.04
Build Date            5/26/16
Package               com.ibm.websphere.BASE.v90_9.0.0.20160526_1854
Architecture          x86-64 (64 bit)
Installed Features    WebSphere Application Server traditional
                      EJBDeploy tool for pre-EJB 3.0 modules
                      Embeddable EJB container
                      Sample applications
                      Stand-alone thin clients and resource adapters

</snip>

before creating a standard application-server profile: -

/opt/IBM/WebSphere/AppServer/bin/manageprofiles.sh -create -profileName AppSrv01 -nodeName localhostNode01 -hostName localhost -adminUserName wasadmin -cellName localhostNode01Cell -enableAdminSecurity true -serverName server1 -profilePath /opt/IBM/WebSphere/AppServer/profiles/AppSrv01 -templatePath /opt/IBM/WebSphere/AppServer/profileTemplates/default -applyPerfTuningSetting standard -adminPassword passw0rd

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

from which I started the server1 instance: -

/opt/IBM/WebSphere/AppServer/profiles/AppSrv01/bin/startServer.sh server1

ADMU0116I: Tool information is being logged in file
           /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/logs/server1/startServer.log
ADMU0128I: Starting tool with the AppSrv01 profile
ADMU3100I: Reading configuration for server: server1
ADMU3200I: Server launched. Waiting for initialization status.
ADMU3000I: Server server1 open for e-business; process id is 12356


and then ran the Installation Verification Test (IVT): -

/opt/IBM/WebSphere/AppServer/profiles/AppSrv01/bin/ivt.sh server1 AppSrv01

Server name is:server1
Profile name is:AppSrv01
Profile home is:/opt/IBM/WebSphere/AppServer/profiles/AppSrv01
Profile type is:default
Cell name is:localhostNode01Cell
Node name is:localhostNode01
Current encoding is:UTF-8
Server port number is:9080
IVTL0010I: Connecting to the localhost WebSphere Application Server on port: 9080
IVTL0015I: WebSphere Application Server localhost is running on port: 9080 for profile AppSrv01
Testing server using the following URL:http://localhost:9080/ivt/ivtserver?parm2=ivtservlet
IVTL0050I: Servlet engine verification status: Passed 
Testing server using the following URL:http://localhost:9080/ivt/ivtserver?parm2=ivtAddition.jsp
IVTL0055I: JavaServer Pages files verification status: Passed 
Testing server using the following URL:http://localhost:9080/ivt/ivtserver?parm2=ivtejb
IVTL0060I: Enterprise bean verification status: Passed
IVTL0035I: The Installation Verification Tool is scanning the /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/logs/server1/SystemOut.log file for errors and warnings.
[04/09/16 05:30:15:728 BST] 00000001 WSKeyStore    W   CWPKI0041W: One or more key stores are using the default password.
[04/09/16 05:30:26:054 BST] 00000001 SibMessage    W   [:] CWSJY0003W: MQJCA5001: WMQ messaging : '9.0.0.0-p900-L160509.1'. 
[04/09/16 05:30:28:515 BST] 0000004d AuthConfigFac W   SECJ8032W: AuthConfigFactory implementation is not defined, using the default JASPI factory implementation class: com.ibm.ws.security.jaspi.ProviderRegistry.
IVTL0040I: 3 errors/warnings are detected in the /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/logs/server1/SystemOut.log file
IVTL0070I: The Installation Verification Tool verification succeeded.
IVTL0080I: The installation verification is complete.


ending with a spot of functional testing: -









and a bit of remote admin: -

/opt/IBM/WebSphere/AppServer/profiles/AppSrv01/bin/wsadmin.sh 

Realm/Cell Name: <default>
Username: wasadmin
Password:         
 WASX7209I: Connected to process "server1" on node localhostNode01 using SOAP connector;  The type of process is: UnManagedProcess
WASX7031I: For help, enter: "print Help.help()"
wsadmin>
wsadmin>print AdminTask.listNodes()
localhostNode01
wsadmin>quit

before shutting down the JVM: -

/opt/IBM/WebSphere/AppServer/profiles/AppSrv01/bin/stopServer.sh server1 -user wasadmin -password passw0rd

ADMU0116I: Tool information is being logged in file
           /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/logs/server1/stopServer.log
ADMU0128I: Starting tool with the AppSrv01 profile
ADMU3100I: Reading configuration for server: server1
ADMU3201I: Server stop request issued. Waiting for stop status.
ADMU4000I: Server server1 stop completed.


Next, I'll be integrating with DB2 and MQ, before deploying a business application stack such as IBM Operational Decision Manager to WAS 9 ….


3 comments:

Saurav said...

Thank you! this is very helpful post... i was stuck from 2 days to install websphere..
This post made it with ease... thank you! :)

Saurav said...

Can you please write a blog for how to uninstall these all packages? It will be really helpful like this too..

Dave Hay said...

Hi Saurav, thanks for the comments. The easiest way to uninstall packages such as WAS is to use Installation Manager.

You can either use the GUI ( IBMIM ) or the command-line ( imcl ).

As an example, this will uninstall EVERYTHING apart from IM itself: -

/opt/ibm/InstallationManager/eclipse/tools/imcl uninstallAll

Cheers, Dave

Note to self - use kubectl to query images in a pod or deployment

In both cases, we use JSON ... For a deployment, we can do this: - kubectl get deployment foobar --namespace snafu --output jsonpath="{...