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: -


<?xml version='1.0' encoding='UTF-8'?>
    <repository location='/tmp/im' temporary='true'/>
    <repository location='/tmp/was' temporary='true'/>
    <repository location='/tmp/java' temporary='true'/>
  <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='' value='gtk'/>
    <data key='' 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 id='IBM WebSphere Application Server V9.0' installLocation='/opt/IBM/WebSphere/AppServer'>
    <data key='cic.selector.arch' value='x86_64'/>
    <offering id='' 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='' version='' features='core.feature,ejbdeploy,thinclient,embeddablecontainer,samples'/>
    <offering profile='IBM WebSphere Application Server V9.0' id='' version='8.0.3000.20160526_1317' features=''/>
  <preference name='' value='/opt/IBM/IMShared'/>

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

/tmp/im/tools/imcl -input installWAS9.rsp -acceptLicense
Installed to the /opt/IBM/InstallationManager/eclipse directory.
Installed to the /opt/IBM/WebSphere/AppServer directory.
Installed to the /opt/IBM/WebSphere/AppServer directory.

and then verified: -

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

/opt/IBM/InstallationManager/eclipse : : IBM® Installation Manager : 1.8.5 : 
/opt/IBM/WebSphere/AppServer : : IBM SDK, Java Technology Edition, Version 8 : : 
/opt/IBM/WebSphere/AppServer : : IBM WebSphere Application Server  : : ejbdeploy,embeddablecontainer,samples,thinclient


Name                  IBM WebSphere Application Server
ID                    BASE
Build Level           gm1621.04
Build Date            5/26/16
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


before creating a standard application-server profile: -

/opt/IBM/WebSphere/AppServer/bin/ -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/ server1

ADMU0116I: Tool information is being logged in file
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/ 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 : ''. 
[04/09/16 05:30:28:515 BST] 0000004d AuthConfigFac W   SECJ8032W: AuthConfigFactory implementation is not defined, using the default JASPI factory implementation class:
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: -


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

before shutting down the JVM: -

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

ADMU0116I: Tool information is being logged in file
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 ….

No comments: