WebSphere Cloud

I will be back

2013-10-07T11:51:00.002-04:00

I joined IBM China Global Delivery Center for more than one year since 2012, I will be back and continue to work on my blog

Start/stop Weblogic without entering username and password

2012-02-25T12:44:00.001-05:00

Recently I am working on installing Oralce Fusion middleware products which require WebLogic Application Server.

During start/stop Weblogic Application Server, we have to manually entering the username and password.To try to avoid doing this, we can add boot.properties file in security directory

1) go to server instance security directory, for example, ${Weblogic_Home}/user_projects/domains/testdomain/servers/AdminServer/security.

Note: must be server instance directory, if the boot.properties created at other directory, it will not work.

2) create a file named boot.properties as following:
username=weblogic
password=123456789

Note: no single or double quote for the values, or it will not work

3) start the weblogic server using command start_Weblogic,sh and then the username and password fields will be encrypted automatically.

For IBM WebSphere Application Server, if we enabled global security, we also need to change file names soap.client.props in WAS instance directory to avoid entering the username and password.

1) go to WAS instance property directory, for example, <WAS Instance>/properties
2) open file soap.client.props and update the following fields and then save it.

com.ibm.SOAP.securityEnabled=true

com.ibm.SOAP.loginUserid=wasuser
com.ibm.SOAP.loginPassword=12345678

3) To encrypt the password, we have to run the following commands

../bin/PropFilePasswordEncoder.sh soap.client.props com.ibm.SOAP.loginPassword

4) then the password will be encrypted.

now you do not need to put username and password any longer.

WebSphere launchClient.sh shows Out Of Memory Error.

2012-02-25T12:15:00.000-05:00

One of my applications is using WebSphere Application Server launchClient script to run some functions.However, launchClient script can not be run properly because of the Out of memory issue(PermGen Space).

Checking WAS instance SystemOut.log and verbose gc logs,and no any errors in the log files, which shows launchClient script did not interact with the WAS instance yet.

solution:

add the options "-JVMOptions" to specify the perm size value

launchClient.sh -profileName AppSrv01 -JVMOptions "-XX:MaxPermSize=256M"

then the issue was solved.

WebSphere Application Server -- ORA-03120 error solution

2012-01-19T23:48:00.000-05:00

WAS server 6.1.0.27 running on Solaris
Back-end Database: Oracle 9i -9.2.0.4.0

Application running on WAS is writing the XML response to table CLOB field but the following error shows in the SystemOut.log:

writeClob failed on com.xxxx.xxx.

Checked the application log and found ORA-03120 error (Integer Overflow):

Queried Oracle DBA and DBA did not notice any error on Database side. The application running on Production environment has no this kind of error.
Compared the SystemOut.log on Prod Server and Test Server and found that Test Server is using Oracle JDBC driver 11.2.0.1.0 (ojdbc5.jar) but Prod Server is using Oracle JDBC driver 10.2.0.2.0 (ojdbc14.jar). then the root cause should be on Oracle JDBC driver.
Checked Test Server environment and found both ojdbc14.jar and ojdbc6.jar are at /IBM/WebSphere/AppServer/oracleDriver directory, which is ${ORACLE_JDBC_DRIVER_PATH}. Although the classpath in WAS JDBC Provider was specified as " ${ORACLE_JDBC_DRIVER_PATH}/ojdbc14.jar", the Server still using JDBC driver 11.2.0.1.0 to connect to remote Oracle 9i Database.
To let the server use the old Oracle JDBC driver 10.2.0.2.0, we have to log on to WAS admin console, go to "Servers"->"Application servers"->"server1". Expand "Java and Process Management", click "Process Definition"->"Java Virtual machine", put "${ORACLE_JDBC_DRIVER_PATH}/ojdbc14.jar" into classpath. Then save it and restart the server.
After server is restarted, we can see the server is using old Oracle JDBC driver 10.2.0.2.0 and the ORA-03120 error is gone.

WebSphere Business Monitor 7 - Archive Monitor Module Instance Data

2012-01-15T00:59:00.000-05:00

After a long time running, the instance data in a monitor module may reach thousands of records. It will take a lot of Database server disk space and will also downgrade the query performance. The following UNIX shell script shows how to archive the instance data with retention period of 3 month:

IBM provide a jython script in the directory /IBM/WebSphere/MonServer/scripts.wbm/instances to use for archive the data, refering to the following URL for the script usage:

http://publib.boulder.ibm.com/infocenter/dmndhelp/v7r0mx/topic/com.ibm.btools.help.monitor.ref.doc/ref/instdata_archive_script.html

#!/usr/bin/ksh

classDir=/IBM/WebSphere/MonServer/plugins
wsadminDir=/IBM/wbmProfiles/WBMProd01/bin
scriptDir=/IBM/WebSphere/MonServer/scripts.wbm/instances
archiveDir=/IBM/delta
currentMonth=`date +%m`
currentYear=`date +%Y`
currentDate=`date +%d`

pre3Month=`expr $currentMonth - 3`

if [ "$pre3Month" -le "0" ]; then
   pre3Month=`expr $pre3Month + 12`
   currentYear=`expr $currentYear - 1`
fi

#acquire the date 3 month ago
previousDate=$currentYear-$pre3Month-$currentDate

#define a startTime, The date is better before the monitor module version date.
startTime="2011-8-1T00:00:00"
endTime="$previousDate"T00:00:00
classPath=$classDir/com.ibm.wbimonitor.lifecycle.spi.jar:$classDir/com.ibm.wbimonitor.archive.jar

echo "Achive the instance for monitor model MO_Monitoring"

$wsadminDir/wsadmin.sh -wsadmin_classpath $classPath -lang jython -f $scriptDir/instanceArchive.jy MO_Monitoring 2011-08-10T13:00:33 $archiveDir $startTime $endTime

echo "Done"

WebSphere Partner Gateway - Resend a file using script

2012-01-13T20:40:00.001-05:00

This post will show how to resend a file using jacl script in IBM WebSphere Partner Gateway (WPG), WPG is an AS2 file exchange software developed by IBM. Some times we have to resend a failed file to AS2 partners. This action can be down from hubadmin console but if we know how to resend a file using jacl script, we can schedule the task. the following scripts are working with WPG6.0, not test on other WPG version.

To resend a failed file, we have to know he failed file name, VUID and resend id.

1) we can get VUID from the back-end Database table LG_ACTIVITY_DTL table using the SQL statment, and then insert the failed file name, VUID and generated RESENDID into table LG_RESEND

CONNECT TO BCGAPPS USER username USING password

INSERT INTO LG_RESEND(RESENDID,VUID,UPDATEDATE) SELECT INTEGER(SUBSTR(CAST(TIMESTAMP(GENERATE_UNIQUE()) AS VARCHAR(27)),21)),VUID FROM LG_ACTIVITY_DTL WHERE ORIGINALFILENAME='test.txt' AND HDRFLG=1;

Note: RESENDID can not be duplicated.

2) Check the record with bad filename\VUID\RESENDID are insert into table LG_RESEND

3) run the following JACL statement to resend the file.

set id "BCGInt:code=com.ibm.bcg.resend.ResendEngine,name=Resend_Inbound,type=Document Aquisition"
$AdminControl invoke $id startResend

then the command can be put into one shell script and then schedule a job. check the records in the table LG_RESEND are gone.

IBM BPM7.5 Advanced Architecture

2012-01-12T14:32:00.000-05:00

The following architecture diagram shown here provides a good introduction to the makeup of BPM Advanced. It highlights the tools and capabilities that originate from earlier version of WebSphere Lombardi Edition and WebSphere Process Server.

This includes the process center, process designer, integration designer and process server. The Process Center provides governance over the entire life cycle of a business process, from initial modeling all the way through to deployment in production. The Process Center also maintains the central BPM repository containing all the process applications artifacts, including assets shared across multiple process applications. The Process Designer, is used to model, develop and test process applications. The Integration Designer, is used to develop SOA based services that can be called from process applications. The Process Server is the runtime environment for process applications. It provides a rich and diverse set of functionality for business processes. Some of the key capabilities include Service Component Architecture (SCA), Business Process Execution Language (BPEL), Enterprise Service Bus (ESB) and Business Process Modeling Notation (BPMN). In IBM BPM V7.5, process designers can express business rule logic in a more natural language manner that reduces the need for specialized training. It helps increase efficiency with a federated view for performing tasks, managing work items, tracking performance and responding to events. Process applications are designed to scale from first projects to enterprise-wide solutions with processes that run consistently, reliably, securely, and with transactional integrity. IBM BPM V7.5 provides centralized deployment and tracking of process application versions to any IBM Business Process Manager test or production server or cluster, with optional one-click migration of in-flight processes. Integration Designer makes it easier for service and integration developers to build reusable SOA services, orchestrating services, and access back-end systems. There is complete BPM life cycle governance enabled by a unified BPM asset repository and control center that makes is easy to share and version processes and service assets. Built-in playback feature allows teams to instantly step through and review the current process design by actually executing it with a single click. There are also powerful features for team-oriented development of multiple projects, including concurrent editing with merge-less development, simplified snapshot version handling, and back-in-time views.

IBM BPM7.5.1 database compare with WPS7

2012-01-04T12:29:00.001-05:00

The following Database need to be created for IBM BPM7.5.1

1) BPMDB (Process Server DB)
2) CMNDB (Common DB)
3) BPCDB (Business Process Choreographer DB)
4) BSPACEDB (Business Space DB)
5) OBSRVDB (Business Process Observing Reporting DB)
6) PDWDB (Performance Datawarehouse DB)
7) MEDB (Messaging Engine database)
8) CEIDB (Common Event Service DB)

BPMDB is a new Database for BPM7.5.1, which is used by BPM advanced Process Center.
CMNDB is same database with WPSDB in WPS7.
BPCDB is same database with BPEDB in WPS7
BSPACEDB is same database with BSPACEDB in WPS7
OBSRVDB is same database with OBSRVDB in WPS7, this database can be removed if the same tables are created in CMNDB.
PDWDB is a new Database for BPM7.5.1, which is used for BPM Performance Datawarehouse
MEDB is same database with MEDB in WPS7. Compared with MEDB in WPS7, two new SIBus DDL files are created. One is for MEPDW (Peformance Datawarehouse SIB Bus) and another is MEPRS(Process Server SIBBus)
CEIDB is same database with CEIDB in WPS7.

Install IBM BPM Advanced Process Server 7.5.1 on AIX 7 silently

2012-01-03T11:07:00.020-05:00

BPM, Business Process Management, is a product released by IBM to replace WebSphere Process Server after IBM purchased the company Lombardi and integrated its distinguished business process solution. In this post, I will show how to install BPM Advanced Server 7.5.1 on AIX7; however, this process does not include install Lombardi business process center.

The steps show how to install IBM BPM 7.5.1 silently with non-root user, for example, wpsuser.

1. PRELIMINARY WORK

1) Create a file system called /IBM or another name with 20G disk space

2) Set the limits for non-root user which is used to install BPM

wpsuser:
        fsize = -1
        core = -1
        cpu = -1
        data = -1
        rss = 65536
        stack = 65536
        nofiles = 20000

3) Install DB2 database 9.5 FP4 or later version (DB2 9.7)

4) Download the following installation files from IBM passport advantage

PS_Adv_V751_AIX_1_of_2.tar.gz

PS_Adv_V751_AIX_2_of_2.tar.gz

2. Install Software

1) unzip the installation files PS_Adv_V751_AIX_1_of_2.tar.gz and PS_Adv_V751_AIX_2_of_2.tar.gz to the temp directory, for example /IBM/software/BPM751

2) After unpacking the zip file, go to directory .responsefiles/BPM, we will see the file template_response.xml. Before we change this file, we should backup it.

3) update the file like the following



       <repository location='/IBM/software/BPM751/IM' temporary='true'/>



     <repository location="/IBM/software/BPM751/repository/">

note: the above settings specify the software repository directory



<profile kind='self' installLocation='/IBM/InstallationManager/eclipse' id='IBM Installation Manager'>

       <data key='eclipseLocation' value='/IBM/InstallationManager/eclipse'/>

</profile>



<preference value="/IBM/InstallationManager/eclipseCache" name="com.ibm.cic.common.core.preferences.eclipseCache" />

note: the above settings specify the IBM Installation Manager directory

<profile installLocation='/IBM/WebSphere/BPMProcServer' id='IBM Business Process Manager Advanced - Process Server'>

       <data key='eclipseLocation' value='/IBM/WebSphere/BPMProcServer' />

       <data key="cic.selector.nl" value="en" />

       <data key='user.import.profile' value='false'/>

       <data key='user.select.64bit.image,com.ibm.websphere.ND.v70' value='true'/>

<install>

       <offering profile="IBM Business Process Manager Advanced - Process Server" id="com.ibm.websphere.ND.v70" features='core.feature,samples,import.productProviders.feature,import.configLauncher.feature,consoleLanguagesSupport.feature,runtimeLanguagesSupport.feature'/>

       <offering profile="IBM Business Process Manager Advanced - Process Server" id="com.ibm.websphere.XML.v10" />

       <offering profile="IBM Business Process Manager Advanced - Process Server" id="com.ibm.websphere.SCA.v10" />

       <offering profile="IBM Business Process Manager Advanced - Process Server" id="com.ibm.ws.WBPMPS" features='wps.client.feature,wps.server.feature'/>

</install>

note: the above settings specify the IBM Business Process Manager Advanced - Process Server directory. Specify " user.select.64bit.image,com.ibm.websphere.ND.v70" as "true" if we want to install 64 bit Business Process Manager. specify the correct features you want to install

4) Save the changes of template_response.xml

5) Go to directory /IBM/software/BPM751/IM, run the following command to install BPM751 package.

/IBM/software/BPM751/IM/userinstc -acceptLicense input /IBM/software/BPM751/responsefiles/BPM/template_response.xml -log /home/wpsuser/silent_install.log

6) Go to wpsuser home directory /home/wpsuser to check silent_install.log, the log should have no errors like the following:

<?xml version="1.0" encoding="UTF-8"?>

<result>

</result>

7) You can also check a log like YYYYMMDD_HHMM.xml file in the directory /home/wpsuser/var/ibm/InstallationManager/logs to see the installation process.

If your server did not connect to internet, you may see the "connection warning" but it can be ignored.

8) After a while, the installation process will be finished.

Installed com.ibm.cic.agent_1.5.0.20110909_1200 to the /IBM/InstallationManager/eclipse directory.

Installed com.ibm.websphere.ND.v70_7.0.19.20110814_1205 to the /IBM/WebSphere/BPMProcServer directory.

Installed com.ibm.websphere.XML.v10_1.0.9.20110429_1452 to the /IBM/WebSphere/BPMProcServer directory.

Installed com.ibm.websphere.SCA.v10_1.0.1011.20110506_0159 to the /IBM/WebSphere/BPMProcServer directory.

Installed com.ibm.ws.WBPMPS_7.5.1000.20111111_2245 to the /IBM/WebSphere/BPMProcServer directory

9) Go to directory /IBM/WebSphere/BPMProcServer/bin, run versionInfo.sh to check the version information, we should see:

Installation
--------------------------------------------------------------------------------
Product Directory        /IBM/WebSphere/BPMProcServer
Version Directory        /IBM/WebSphere/BPMProcServer/properties/version
DTD Directory            /IBM/WebSphere/BPMProcServer/properties/version/dtd
Log Directory            /IBM/WebSphere/BPMProcServer/logs
Backup Directory         /IBM/WebSphere/BPMProcServer/properties/version/nif/backup
TMP Directory            /tmp

Product List
--------------------------------------------------------------------------------
BPMPS                    installed
SCA                      installed
ND                       installed
XML                      installed

Installed Product
--------------------------------------------------------------------------------
Name                     IBM Business Process Manager Advanced V7.5 - Process Server
Version                  7.5.1.0
ID                       BPMPS
Build Level              o1145.08
Build Date               11/11/11
Architecture             PPC64

Installed Product
--------------------------------------------------------------------------------
Name                     SCA Feature Pack
Version                  1.0.1.11
ID                       SCA
Build Level              cf111118.05
Build Date               5/6/11
Architecture             PPC64

Installed Product
--------------------------------------------------------------------------------
Name                     IBM WebSphere Application Server - ND
Version                  7.0.0.19
ID                       ND
Build Level              cf191132.09
Build Date               8/13/11
Architecture             PPC64

Installed Product
--------------------------------------------------------------------------------
Name                     XML Feature Pack
Version                  1.0.0.9
ID                       XML
Build Level              cf091117.04
Build Date               4/29/11
Architecture             PPC64

--------------------------------------------------------------------------------
End Installation Status Report
--------------------------------------------------------------------------------

10) Strongly recommend to install the following ifixes using Installation Manager after you finish BPM installation

7.5.1.0-WS-ATLAS-IFJR41201.zip

7.5.1.0-WS-ATLAS-IFJR41203.zip

7.5.1.0-WS-BPM-IFJR41195.zip

was.7.0.0.19.fixes.for.bpm.7.5.1.0.zip

check the following link for the recommended ifixes

http://www-01.ibm.com/support/docview.wss?uid=swg27023411

The above are the steps for installation BPM Advanced Process Server 7.5.1. I will show how to create profiles in another post soon.

Happy New Year - 2012

2012-01-02T16:19:00.001-05:00

Hi all:

2012 is coming, wish all you have a wonderful new year. In 2012, I will keep working on IBM WebSphere technology and implement new BPM 7.5 upgrade. Also, I will begin to touch Oracle Fusion Middleware, mostly on OAM/OIM. And, if possible, I will study WebSphere Cloud technology in 2012.

Happy New Year !!!

Change the unix password remotely on Windows platform (cygwin)

2011-08-17T14:59:00.001-04:00

For a user who maintains WebSphere products on many UNIX servers, it is a boring thing to change the password every 90 or 120 days.

Here is an example to change the password remotely on windows platform using cygwin

1) install cygwin using setup.exe , which can be found at the link: http://www.cygwin.com/
2) run setup.exe and make sure you select "expect" and "ssh" packages.
3) after installing cygwin, click "cygwin" on the windows desktop and you will enter cygwin interface.
4) create an expect shell script like following:

         #!/usr/bin/expect

         set hostname unixhost1
         set user user1
         set password oldpassword
         set newpass newpassword

         spawn ssh -l $user $hostname

         expect "assword:"
         send "$password\r"

          expect "#"
          send "passwd\r"
          expect "Old password:"
          send "$password\r"
          expect "New password:"
          send "$newpass\r"
          expect "gain:"
          send "$newpass\r"
          expect "#"
          send "exit\r"

4) run the script and you can change the user password on the host you specified in the script.

wsadmin faces the soap timeout issue

2011-08-03T05:42:00.000-04:00

When you execute a wsadmin script which will take a long time and you may see the timeout issue:

WASX7015E: Exception running command: "AdminTask.extractConfigProperties ('-interactive')"; exception information:
com.ibm.websphere.management.exception.ConnectorException
org.apache.soap.SOAPException: [SOAPException: faultCode=SOAP-ENV:Client; msg=Read timed out; targetException=java.net.SocketTimeoutException: Read timed out]

the solution for this issue is:

change the field "com.ibm.SOAP.requestTimeout" in the soap.client.properties in the profile directory to a value you want to specify or "0" (which means no timeout). the default value is "180" seconds.

Configure IHS Web Server on WAS or WPS

2011-08-03T04:46:00.003-04:00

After installing IHS Web Server, we need to create a web server on WAS so that the application deployed on WAS server can be mapped to web server.

-          Logon to server WAS_HostServer with user “wasuser”, the user is used to run WebSphere Application Server instances

-          Go to directory /IBM/WebSphere/AppServer/bin

-          Download the file “configurewebserver1.sh” from IHS_HostServer, the file is at /IBM/HTTPServer/Plugins/bin
-          Edit the last line configurewebserver1.sh like this:

./wsadmin.sh $PROFILE_NAME_PARAMETER $WSADMIN_USERID_PARAMETER $WSADMIN_PASSWORD_PARAMETER -f $WAS_HOME/bin/configureWebserverDefini

tion.jacl webserver1 IHS '/IBM/HTTPServer' '/IBM/HTTPServer/conf/httpd.conf' 80 MAP_NONE '/IBM/HTTPServer/Plugins' unmanaged webserver1-node blue-devweb01.mtsallstream.com aix 8008 ihsadmin $IHS_ADMIN_PASSWORD_PARAMETER

I recommend to use "MAP_NONE" to replace "MAP_ALL".

-          Run the shell script

configurewebserver1.sh cellName userid userpassword ihsadmin

userid and userpassword should be specified if global security is enabled.

-          logon to administrative console, then synchronize the nodes

-          Go to servers->server Types-> web servers, if the web server is running on IHS_Host, then the server status is running

-          if webserver1 status is stopped, we can start the web server1 through administrative console if http admin process is running on blue-devweb01.

-          Make the ihsadmin username and password is entered. Click “webserver1”, then click “Remote Web server management” at the right side. assure the port number, username and password are correct

-          Then select “webserver1” and click “Start” button to start web server, the server should be started.

-          Select “webserver1” and click “Generate Plug-in”, and then select “webserver1” again and click “Propagate Plug-in”. we may see the following error:

"PLGC0049E: The propagation of the plug-in configuration file failed for the Web servers xxxxxxxxxx

-          the reason why it happened it because the permission issue

-          logon to server IHS_Host with user “wasuser”

-          go to directory /IBM/HTTPServer/Plugins/config/webserver1

-          make sure plugin-cfg.xml permission is 755 or 664

-          go to directory /IBM/HTTPServer/conf

-          edit the conf file admin.conf as following:

User wasuser

Group wasgroup

-          switch to root user

-          Go to directory /IBM/HTTPServer/bin

-          restart admin process: ./adminctl stop and ./adminctl start

-          the issue should be solved.

Install IBM IHS on AIX System (1)

2011-08-03T04:36:00.005-04:00

1) Create logical file system /IBM (or other name)

2) Download the following installation files from IBM WebSite

- C1G2NML.tar.gz (WebSphere Supplements installation media)

3) Download the following FixPack files from IBM website.

Fixpacks
7.0.0-WS-IHS-AixPPC32-FP0000017.pak

7.0.0-WS-PLG-AixPPC32-FP0000017.pak

4) install IHS silently with root user

- Log on the server as root

- In /IBM/IHS7

gunzip C1G2NML.tar.gz

tar –xvf C1G2NML.tar

- Go to directory /IBM/IHS7/IHS

- Run command “cp responsefile.txt responsefile.txt.bak”

- Edit responsefile.nd.txt and set the following value

-OPT silentInstallLicenseAcceptance="true"

-OPT allowNonRootSilentInstall=false

-OPT installLocation="/IBM/HTTPServer"

-OPT createAdminAuth="true"

-OPT adminAuthUser="ihsadmin"

-OPT adminAuthPassword="ihsadmin"

-OPT adminAuthPasswordConfirm="ihsadmin"

-OPT runSetupAdmin="true"

-OPT createAdminUserGroup=true

-OPT setupAdminUser="ihsadmin"

-OPT setupAdminGroup="ihsgroup"

-OPT washostname="remote_was_host"

Uncomment the following options

-OPT disableOSPrereqChecking="true"

And comment all others options

-          Run the following command to install IHS7.0 server

./install -options "responsefile.txt" -silent

See the log files in wpsuser home directory /home/wpsuser/ihslogs) for the installation status.

-          After installation, go to directory /IBM/HTTPServer/bin, and check IHS version using “versionInfo.sh”, we will see the version of HTTP Server is 7.0.0.0, go to directory /IBM/HTTPServer/Plugins/bin, and check WebSphere Plugins version using “versionInfo.sh”, we will see the version of WebSphere Plugins version is 7.0.0.0

5)     Install Update Installer 7.0.0.17 on the server

-    Go to Directory /IBM/UPDI/

-    Run the command “gunzip 7.0.0.17-WS-UPDI-AixPPC32.tar.gz” and “tar –xvf 7.0.0.17-WS-UPDI-AixPPC32.tar”

-    Go to Directory /IBM/cd_software/UPDI/UpdateInstaller

-    Run the command “cp responsefile.updiinstaller.txt responsefile.updiinstaller.txt.bak”

-    Edit the file “responsefile.updiinstaller.txt” and set the following value

-OPT silentInstallLicenseAcceptance="true"

-OPT installLocation="/IBM/WebSphere/UpdateInstaller"

Uncomment the following options

-OPT disableOSPrereqChecking="true"

-OPT disableEarlyPrereqChecking="true"

Comment all other options

-          Run the command “./install -options "responsefile.updiinstaller.txt" –silent” to install update installer

Or run this command to install:

./install -silent -OPT silentInstallLicenseAcceptance=true -OPT allowNonRootSilentInstall=true -OPT disableOSPrereqChecking=true -OPT installLocation=/IBM/WebSphere/UpdateInstaller

-          Go to Directory /IBM/WebSpehre/UpdateInstaller to check Update Installer version, it should be “7.0.0.17

6)     Install IHS and WebSphere Plugins fixpacks using Update Installer

-    Go to Directory /IBM/WebSphere/UpdateInstaller/responsefiles

-    Run the command “cp install.txt installIHS.txt” and “cp install.txt installPLG.txt”

-    Edit installIHS.txt as the following:

-W maintenance.package="/IBM/fixpack/7.0.0-WS-IHS-AixPPC32-FP0000017.pak"

-W product.location="/IBM/HTTPServer"

-    Edit installPLG.txt as the following:

-W maintenance.package="/IBM/fixpack/7.0.0-WS-PLG-AixPPC32-FP0000017.pak"

-W product.location="/IBM/HTTPServer/Plugins"

- Go to Directory /IBM/WebSphere/UpdateInstaller/bin, run the following command to apply the fixpacks

./update.sh -options responsefiles/installIHS.txt –silent

./update.sh -options responsefiles/installPLG.txt –silent

Monitor /IBM/WebSphere/UpdateInstaller/logs/tmp/updatelog.txt for updating status.

-    Go to Directory /IBM/HTTPServer/bin and /IBM/HTTPServer/Plugins/bin, run the command “versionInfo.sh” to check that both version should be 7.0.0.17.

-    After installation, go to /IBM, run the following command to grant the permission
“chmod –fR 755 /IBM/HTTPServer”, “chown –fR wasuser:wasgroup /IBM/HTTPServer”

-    Go to /IBM/HTTPServer/conf, edit httpd.conf and update the following values

User wasuser

Group wasgroup

- Go to /IBM/HTTPServer/bin, and run “adminctl start” and “apachectl –k start” to start IHS server.

WebSphere Process Server 7.0 silent installation (4)

2011-07-23T08:32:00.005-04:00

WPS_Response.xml file:

<?xml version="1.0" encoding="UTF-8"?>
<agent-input clean='true' >
<server>
<repository location='/IBM/cd_software/WPS7/repository/repository.config'/>
<repository location='/IBM/cd_software/WPS7/WAS_SYNC/repository.config'/>
<repository location='/IBM/fixpack/sca.1.0.1.11.fp/repository.config'/>
<repository location='/IBM/fixpack/xml.1.0.0.9.fp/repository.config'/>
<repository location='/IBM/fixpack/xml.1.0.import/import/repository.config'/>

<repository location='/IBM/fixpack/was.7.0.import/repository.config'/>
<repository location='/IBM/fixpack/wps.7003.repository/repository.config'/>
<repository location='/IBM/fixpack/7.0.0.3.wps.fixes/repository.config'/>
<repository location='/IBM/fixpack/sca.1.0.import/import/repository.config'/>
</server>
<profile kind='self' installLocation='/IBM/InstallationManager/eclipse' id='IBM Installation Manager'>
<data key='eclipseLocation' value='/IBM/InstallationManager/eclipse'/>
</profile>

<preference value="/IBM/InstallationManager/eclipseCache" name="com.ibm.cic.common.core.preferences.eclipseCache" />
<profile installLocation='/IBM/WebSphere/ProcServer' id='IBM WebSphere Application Server - ND'>
<data key='eclipseLocation' value='/IBM/WebSphere/ProcServer'/>
<data key="cic.selector.nl" value="en" />
<data key="user.cic.imported,com.ibm.websphere.ND.70" value="WAS" />
</profile>
<import profile="IBM WebSphere Application Server - ND" type="WAS" />
<install>
<offering profile="IBM WebSphere Application Server - ND" id="com.ibm.websphere.XML.v10" />
<offering profile="IBM WebSphere Application Server - ND" id="com.ibm.websphere.SCA.v10" />
<offering profile="IBM WebSphere Application Server - ND" id="com.ibm.ws.WPS" />
</install>
<preference value="30" name="com.ibm.cic.common.core.preferences.connectTimeout" />
<preference value="30" name="com.ibm.cic.common.core.preferences.readTimeout" />
<preference value="0" name="com.ibm.cic.common.core.preferences.downloadAutoRetryCount" />
<preference value="false" name="offering.service.repositories.areUsed" />
<preference value="false" name="com.ibm.cic.common.core.preferences.ssl.nonsecureMode" />
<preference value="false" name="com.ibm.cic.common.core.preferences.http.disablePreemptiveAuthentication" />
<preference value="true" name="com.ibm.cic.common.core.preferences.preserveDownloadedArtifacts" />
<preference value="false" name="PassportAdvantageIsEnabled" />
<preference value="false" name="com.ibm.cic.common.core.preferences.searchForUpdates" />
<preference value="true" name="com.ibm.cic.common.core.preferences.import.enabled" />
</agent-input>

Next steps are to ask DBA to create the database and create WPS profiles.

WebSphere Process Server 7.0 silent installation (3)

2011-07-23T08:25:00.006-04:00

2)     Install IBM Installation Manager

-    Go to Directory /IBM/cd_software/IM

-    Run the command to unzip the file “agent.installer.aix.motif.ppc_1.4.4000.20110525_1254.zip”

/IBM/WebSphere/ProcServer/java/bin/jar –xvf agent.installer.aix.motif.ppc_1.4.4000.20110525_1254.zip

chmod –fR 755 *

-    Copy install.xml to install.xml.bak

-    Edit the file install.xml as the following

<?xml version="1.0" encoding="UTF-8"?>

<agent-input clean='true' temporary='true'>

<profile kind='self' installLocation='/IBM/InstallationManager/eclipse' id='IBM Installation Manager'>

<data key='eclipseLocation' value='/IBM/InstallationManager/eclipse'/>

</profile>

<server>

<repository location='.'/>

</server>

<install>

<offering profile='IBM Installation Manager' features='agent_core,agent_jre' id='com.ibm.cic.agent' version='1.4.4000.20110525_1254'

/>

</install>

</agent-input>

-    Run the following command to install IBM Installation Manager
./userinstc -acceptLicense

check the directory /was/home/wpsuser/var/ibm/InstallationManager/logs/index.xml to see if any errors.
Note: do not remove the directory /var/ibm/InstallationManager

3)     Install WebSphere Process Server 7.0.0.3 on AIX OS

-    Go to Directory /IBM/fixpack

Unzip sca.1.0.1.11.fp.zip to directory sca.1.0.1.11.fp

Unzip sca.1.0.import.zip to directory sca.1.0.import

Unzip xml.1.0.0.9.fp.zip to directory xml.1.0.0.9.fp

Unzip xml.1.0.import.zip to directory xml.1.0.import

Create a directory named 7.0.0.3.wps.fixes, and move the file 7.0.0.3.wps.fixes.zip to this directory and unzip it

Create a directory named wps.7003.repository, and move the file wps.7003.repository.zip to this directory and unzip it

Create a directory named was.7.0.import directory, and move the file was.7.0.import.zip to this directory and unzip it

-    Create a response xml file called WPS_Response.xml at /IBM/cd_software/WPS7. the xml is following

<?xml version="1.0" encoding="UTF-8"?>

<agent-input clean='true' >

<server>

<repository location='/IBM/cd_software/WPS7/repository/repository.config'/>

<repository location='/IBM/cd_software/WPS7/WAS_SYNC/repository.config'/>

<repository location='/IBM/fixpack/sca.1.0.1.11.fp/repository.config'/>

<repository location='/IBM/fixpack/xml.1.0.0.9.fp/repository.config'/>

<repository location='/IBM/fixpack/xml.1.0.import/import/repository.config'/>

<repository location='/IBM/fixpack/was.7.0.import/repository.config'/>

<repository location='/IBM/fixpack/wps.7003.repository/repository.config'/>

<repository location='/IBM/fixpack/7.0.0.3.wps.fixes/repository.config'/>

<repository location='/IBM/fixpack/sca.1.0.import/import/repository.config'/>

</server>

<profile kind='self' installLocation='/IBM/InstallationManager/eclipse'id='IBM Installation Manager'>

<data key='eclipseLocation' value='/IBM/InstallationManager/eclipse'/>

</profile>

<preference value="/IBM/InstallationManager/eclipseCache" name="com.ibm.cic.common.core.preferences.eclipseCache" />

<profile installLocation='/IBM/WebSphere/ProcServer' id='IBM WebSphere Application Server - ND'>

<data key='eclipseLocation' value='/IBM/WebSphere/ProcServer'/>

<data key="cic.selector.nl" value="en" />

<data key="user.cic.imported,com.ibm.websphere.ND.70" value="WAS" />

</profile>

<import profile="IBM WebSphere Application Server - ND" type="WAS" />

<install>

<offering profile="IBM WebSphere Application Server - ND" id="com.ibm.websphere.XML.v10" />

<offering profile="IBM WebSphere Application Server - ND" id="com.ibm.websphere.SCA.v10" />

<offering profile="IBM WebSphere Application Server - ND" id="com.ibm.ws.WPS" />

</install>

<preference value="30" name="com.ibm.cic.common.core.preferences.connectTimeout" />

<preference value="30" name="com.ibm.cic.common.core.preferences.readTimeout" />

<preference value="0" name="com.ibm.cic.common.core.preferences.downloadAutoRetryCount" />

<preference value="false" name="offering.service.repositories.areUsed" />

<preference value="false" name="com.ibm.cic.common.core.preferences.ssl.nonsecureMode" />

<preference value="false" name="com.ibm.cic.common.core.preferences.http.disablePreemptiveAuthentication" />

<preference value="true" name="com.ibm.cic.common.core.preferences.preserveDownloadedArtifacts" />

<preference value="false" name="PassportAdvantageIsEnabled" />

<preference value="false" name="com.ibm.cic.common.core.preferences.searchForUpdates" />

<preference value="true" name="com.ibm.cic.common.core.preferences.import.enabled" />

</agent-input>

-    Go to the directory /IBM/InstallationManager/eclipse/tools, and run the following command to install WPS v7.0.0.3

./imcl -acceptLicense -s -sVP -input /IBM/cd_software/WPS7/WPS_Response.xml -log /IBM/cd_software/WPS7/wps_install.log

Monitor the process to see if any error happens.

The logs should show:
Installed com.ibm.websphere.XML.v10_1.0.9.20110429_1452 to the /IBM/WebSphere/ProcServer directory.

Installed com.ibm.websphere.SCA.v10_1.0.1011.20110506_0159 to the /IBM/WebSphere/ProcServer directory.

Installed com.ibm.ws.WPS_7.0.3.20100824_2115 to the /IBM/WebSphere/ProcServer directory.

Installed 7.0.0.3-WS-WBI-IFJR37642_0.0.0.20100831_1725 to the /IBM/WebSphere/ProcServer directory.

Installed 7.0.0.3-WS-WBI-IFJR37645_0.0.0.20100901_1340 to the /IBM/WebSphere/ProcServer directory.

Run “versionInfo.sh”, we should see the following:

Installed Product

--------------------------------------------------------------------------------

Name                     SCA Feature Pack

Version                  1.0.1.11

ID                       SCA

Build Level              cf111118.05

Build Date               5/6/11

Architecture             PPC32

Installed Product

--------------------------------------------------------------------------------

Name                     IBM WebSphere Application Server - ND

Version                  7.0.0.17

ID                       ND

Build Level              cf171115.15

Build Date               4/16/11

Architecture             PPC32

Installed Product

--------------------------------------------------------------------------------

Name                     IBM WebSphere Process Server

Version                  7.0.0.3

ID                       WBI

Build Level              of1034.05

Build Date               8/24/10

Architecture             PPC32

Installed Product

--------------------------------------------------------------------------------

Name                     XML Feature Pack

Version                  1.0.0.9

ID                       XML

Build Level              cf091117.04

Build Date               4/29/11

Architecture             PPC32

WebSphere Process Server 7.0 silent installation (2)

2011-07-23T08:23:00.001-04:00

2)     Install Update Installer 7.0.0.17 on AIX OS

-    Go to Directory /IBM/cd_software/UPDI/

-    Run the command “gunzip 7.0.0.17-WS-UPDI-AixPPC32.tar.gz” and “tar –xvf 7.0.0.17-WS-UPDI-AixPPC32.tar”

-    Go to Directory /IBM/cd_software/UPDI/UpdateInstaller

-    Run the command “cp responsefile.updiinstaller.txt responsefile.updiinstaller.txt.bak”

-    Edit the file “responsefile.updiinstaller.txt” and set the following value

-OPT silentInstallLicenseAcceptance="true"

-OPT installLocation="/IBM/WebSphere/UpdateInstaller"

Uncomment the following options

-OPT allowNonRootSilentInstall="true"

-OPT disableOSPrereqChecking="true"

-OPT disableEarlyPrereqChecking="true"

Comment all other options

-          Run the command “./install -options "responsefile.updiinstaller.txt" –silent” to install update installer

Or run this command to install:

./install -silent -OPT silentInstallLicenseAcceptance=true -OPT allowNonRootSilentInstall=true -OPT disableOSPrereqChecking=true -OPT installLocation=/IBM/WebSphere/UpdateInstaller

-          Go to Directory /IBM/WebSpehre/UpdateInstaller to check Update Installer version, it should be “7.0.0.17

3)     Install WAS fixpacks using Update Installer

-    Go to Directory /IBM/WebSphere/UpdateInstaller/responsefiles

-    Run the command “cp install.txt installfix.txt”

-    Edit installfix.txt as the following:

-W maintenance.package="/IBM/fixpack/7.0.0-WS-WAS-AixPPC32-FP0000017.pak;/IBM/fixpack/7.0.0-WS-WASSDK-AixPPC32-FP0000017.pak;/IBM/fi

xpack/7.0.0.17-WS-WAS-IFPM34365.pak"

-W product.location="/IBM/WebSphere/ProcServer"

Uncoment the following options

-OPT checkFilePermissions="true"

-OPT disableNonBlockingPrereqChecking="true"

-OPT rootUserHasRunSlibcleanCommandSuccessfully="true"

- Go to Directory /IBM/WebSphere/UpdateInstaller/bin, run the following command to apply the fixpacks

./update.sh -options responsefiles/installfix.txt –silent

Monitor /IBM/WebSphere/UpdateInstaller/logs/tmp/updatelog.txt for updating status.

- Go to Directory /IBM/WebSphere/ProcServer/bin, run the command “versionInfo.sh”, the version should be 7.0.0.17.

WebSphere Process Server 7.0 silent installation (1)

2011-07-23T08:21:00.002-04:00

This following steps show how to install WPS 7.0 silently on AIX OS

1. Preliminary Tasks
1) Create a file system called /IBM with the space of 20G
2) download the following installation files from IBM website.
- WPS_v7_AIX32_Install.tar (WebSphere Process Server 7. installation media)
- agent.installer.aix.motif.ppc_1.4.4000.20110525_1254.zip (Installation Manager 1.4.4)
- 7.0.0.17-WS-UPDI-AixPPC32.tar.gz (WebSphere Update Installer 7.0.0.17)
fixpacks:
-          7.0.0-WS-WAS-AixPPC32-FP0000017.pak
-          7.0.0-WS-WASSDK-AixPPC32-FP0000017.pak
-          7.0.0.3.wps.fixes.zip
-          sca.1.0.1.11.fp.zip
-          sca.1.0.import.zip
-          was.7.0.0.17.fixes.zip
-          was.7.0.import.zip
-          wps.7003.repository.zip
-          xml.1.0.0.9.fp.zip
-          xml.1.0.import.zip
-          7.0.0.17-WS-WAS-IFPM34365.pak

2. Install Software

1) Install WebSphere Application Server 7.0 on AIX

- Log on the server as wpsuser

- In /IBM/cd_software/WPS7: tar –xvf WPS_v7_AIX32_Install.tar

- Go to directory /IBM/cd_software/WPS7/WAS.

- Run command “cp responsefile.nd.txt responsefile.nd.txt.bak”

- Edit responsefile.nd.txt and set the following value

-OPT silentInstallLicenseAcceptance="true"

-OPT installType="installNew"

-OPT profileType="none"

-OPT installLocation="/IBM/WebSphere/ProcServer"

Uncomment the following options

-OPT allowNonRootSilentInstall="true”

-OPT disableOSPrereqChecking="true"

-OPT disableNonBlockingPrereqChecking="true"

-OPT checkFilePermissions="true"”

-OPT feature="noFeature"

And comment all others options

-          Run the following command to install WAS7.0 server

./install -options "responsefile.nd.txt" –silent

See the log files in wpsuser home directory (/was/home/wpsuser/waslogs) for the installation status.

-          After installation, go to directory /IBM/WebSphere/ProcServer/bin, and check WAS version using “versionInfo.sh”, we will see the following:

--------------------------------------------------------------------------------

IBM WebSphere Application Server Product Installation Status Report

--------------------------------------------------------------------------------

Report at date and time July 4, 2011 6:48:00 PM CDT

Installation

--------------------------------------------------------------------------------

Product Directory        /IBM/WebSphere/ProcServer

Version Directory        /IBM/WebSphere/ProcServer/properties/version

DTD Directory            /IBM/WebSphere/ProcServer/properties/version/dtd

Log Directory            /IBM/WebSphere/ProcServer/logs

Backup Directory         /IBM/WebSphere/ProcServer/properties/version/nif/backup

TMP Directory            /tmp

Product List

--------------------------------------------------------------------------------

ND                       installed

Installed Product

--------------------------------------------------------------------------------

Name                     IBM WebSphere Application Server - ND

Version                  7.0.0.7

ID                       ND

Build Level              wps0946.04

Build Date               11/18/09

Architecture             PPC32

--------------------------------------------------------------------------------

End Installation Status Report

--------------------------------------------------------------------------------

WebSphere Application Server 7 Federated Repository Configuration - Microsoft AD configuration

2011-06-23T11:49:00.001-04:00

Some people are confusing how to configure the Federated Repository to Connect to Microsoft Active directory LDAP server. IBM docs do not provide a clean configuration steps.

Here are the steps what I configured Federated Repository to connect to Microsoft Active Directory LDAP

1) Log on to Admin Console and go to Security-Global Security

2) select "Federated Repositor" from drop down list and click "Configure..." button

3) Specify a Primary administrative user name. Note: this user name should not be same user in Microsoft AD LDAP

4) Click "Add Base Entry to Realm..." button in this page

5) click "Add Repository" button

6) enter the Repository Identifier, host name, port, binging user, and password, Then click "Apply"

7) click "LDAP entity types" link

8) then click "PersonalAccount" link, and set the Search base like "DC=mydomain,DC=com", then click "Ok"

9) this step is very import, find the file named wimconfig.xml at the directory <ProfileDir>/Config/cells/<NodeName>/wim/config, add the highlighted entry in the correct section

Most Microsoft active directory use sAMAccountName to authenticate the user, so we need to map sAMAccountName attribute to uid in order to search the user.

After changing the file, we need to restart the server. and then we should be able to find the active directory user from the console.

Using API to get WebSphere Application Server Information–get WAS Applications information

2011-06-20T17:36:00.001-04:00

Using WebSphere Application Server MBean to get the application status

private void getApplicationStatus() throws MalformedObjectNameException, NullPointerException, ConnectorException, AttributeNotFoundException, InstanceNotFoundException, MBeanException, ReflectionException{

String queryString="WebSphere:type=Application,*";
ObjectName queryAppObj=new ObjectName(queryString);
Set s=adminClient.queryNames(queryAppObj,null);
Iterator itApp=s.iterator();
while(itApp.hasNext()){
String appStr=itApp.next().toString();
int appNameidx=appStr.indexOf("name");
int appProcessidx=appStr.indexOf("process");
int startAppNameidx=appStr.indexOf("=",appNameidx);
int startAppProcessidx=appStr.indexOf("=",appProcessidx);
int endAppNameidx=appStr.indexOf(",",appNameidx);
int endAppProcessidx=appStr.indexOf(",",appProcessidx);
String appName=appStr.substring(startAppNameidx+1,endAppNameidx);
String processName=appStr.substring(startAppProcessidx+1,endAppProcessidx);

System.out.println(appName+"@"+processName+" is running");
}
}

However, the above procedure can only get the applications which are running on the server. If the application is stopped, this procedure will not get them.

The following procedure can get all applications deployed on the server. the procedure will get all WAS servers if there is a cluster in the environment.

private void getApplicationList() throws Exception {

ArrayList appList=new ArrayList();
Hashtable props=new Hashtable();
AppManagement appM = AppManagementProxy.getJMXProxyForClient(adminClient);
ConfigService configService=new ConfigServiceProxy(adminClient);
Vector v=null;
Object[] appObj=null;
Session session=new Session();
ObjectName[] servers=configService.resolve(session,"Server");

for (ObjectName server:servers) {
String[] serverConfig=server.getKeyProperty("_Websphere_Config_Data_Id").split("/");
String serverName=server.getKeyProperty("_Websphere_Config_Data_Display_Name");
props.put(AppConstants.APPDEPL_LOCALE, Locale.getDefault());
String scope="WebSphere:cell="+serverConfig[1]+",node="+serverConfig[3]+",server="+serverName;
v=appM.listApplications(scope,props,session.getSessionId());
appObj=v.toArray();
for (Object app:appObj){
System.out.println(app.toString()+" is deployed "+serverName);
}
}
}

Using API to get WebSphere Application Server Information--get WAS Server information

2011-06-14T06:08:00.001-04:00

Following the last post, after we connect to the server, we can get the server information

public static void getWASServerList() throws MalformedObjectNameException, InstanceNotFoundException, ReflectionException, ConnectorException,AttributeNotFoundException, MBeanException, ConfigServiceException{

ArrayList serverList=new ArrayList();
String queryString="WebSphere:type=Server,*";

long jvm_heapsize;
long jvm_usedmem;
long jvm_cpuusage;
ObjectName queryServerObj=new ObjectName(queryString);
Set s=adminClient.queryNames(queryServerObj,null);
Properties prop=new Properties();
Iterator itrServer=s.iterator();
ConfigService configService=new ConfigServiceProxy(adminClient);
Session session=new Session();
while (itrServer.hasNext()){
String serverStr=itrServer.next().toString();
ObjectName sobj=new ObjectName(serverStr);
List attrList=adminClient.getAttributes(sobj,new String[]{"name","serverVersion","state","processType","nodeName"});

//*********************************************************
//* this Command is used to get the server name, WAS server version, WAS server state, and server Process Type, and the node name server belongs to
//***********************************************************

String serverName=((Attribute)attrList.get(0)).getValue().toString();
String serverVersion=((Attribute)attrList.get(1)).getValue().toString();
String serverStatus=((Attribute)attrList.get(2)).getValue().toString();
String serverType=((Attribute)attrList.get(3)).getValue().toString();
String nodeName=((Attribute)attrList.get(4)).getValue().toString();

System.out.println("get Perf Information");
System.out.println("------------------");

//*************************************************
//Following codes are used to get WAS server dynamic heap size utilization information
//******************************************************

if (serverType.equals("DeploymentManager")){
jvm_heapsize=0;
jvm_usedmem=0;
jvm_cpuusage=0;
} else {
String PMIQueryString="WebSphere:type=Perf,process="+serverName+",node="+nodeName+",*";
ObjectName PMIObject=new ObjectName(PMIQueryString);
Set perf=adminClient.queryNames(PMIObject,null);
ObjectName perfObj=(ObjectName)perf.iterator().next();

String JVMQueryString="WebSphere:type=JVM,process="+serverName+",node="+nodeName+",*";
ObjectName JVMObject=new ObjectName(JVMQueryString);
Set jvm=adminClient.queryNames(JVMObject,null);
ObjectName jvmMBean=(ObjectName)jvm.iterator().next();
String[] signature = new String[] {"javax.management.ObjectName","java.lang.Boolean"};
Object[] params = new Object[] {jvmMBean, new Boolean(false)};
WSStats jvmStats = (WSStats) adminClient.invoke(perfObj, "getStatsObject", params, signature);
WSRangeStatistic jvmStatistic_Heapsize = (WSRangeStatistic)jvmStats.getStatistic(WSJVMStats.HeapSize);
WSCountStatistic jvmStatistic_UsedMem=(WSCountStatistic)jvmStats.getStatistic(WSJVMStats.UsedMemory);
WSCountStatistic jvmStatistic_CPUUsage=(WSCountStatistic)jvmStats.getStatistic(WSJVMStats.cpuUsage);

jvm_heapsize=jvmStatistic_Heapsize.getCurrent();
jvm_usedmem=jvmStatistic_UsedMem.getCount();
jvm_cpuusage=jvmStatistic_CPUUsage.getCount();
}

//*******************************************************************
//*Following codes to get the server static heap size config
//***************************************************************************

ObjectName[] servers=configService.resolve(session,"Server="+serverName);
Object attr=configService.getAttribute(session,servers[0],"processDefinitions");
int initHeapSizeidx=attr.toString().indexOf("initialHeapSize");
int maxHeapSizeidx=attr.toString().indexOf("maximumHeapSize");
int startInitHeapSizeidx=attr.toString().indexOf("=",initHeapSizeidx);
int startMaxHeapSizeidx=attr.toString().indexOf("=",maxHeapSizeidx);
int endInitHeapSizeidx=attr.toString().indexOf(",",initHeapSizeidx);
int endMaxHeapSizeidx=attr.toString().indexOf(",",maxHeapSizeidx);
String InitHeapSize=attr.toString().substring(startInitHeapSizeidx+2,endInitHeapSizeidx);
String MaxHeapSize=attr.toString().substring(startMaxHeapSizeidx+2,endMaxHeapSizeidx);

System.out.println(serverName+" "+serverStatus +" "+serverType +" "+InitHeapSize+" "+MaxHeapSize+" "+Float.toString((float)jvm_heapsize/1024)+" "+Float.toString((float)jvm_usedmem/1024)+" "+Long.toString(jvm_cpuusage));
}
}

Using API to get WebSphere Application Server Information--Connect to WebSphere Application Server

2011-06-14T06:00:00.001-04:00

In general, we connect to WebSphere Application Server Instance using jython or jacl scripts . IBM WebSphere Application Server also provide various APIs to let the user to connect to the server instance and get the server information. The following is the code to use API to connect to WAS server application.

import com.ibm.websphere.management.AdminClient;
import com.ibm.websphere.management.AdminClientFactory;
import com.ibm.websphere.management.Session;
import com.ibm.websphere.management.configservice.ConfigService;
import com.ibm.websphere.management.configservice.ConfigServiceHelper;
import com.ibm.websphere.management.configservice.ConfigServiceProxy;
import com.ibm.websphere.management.exception.ConfigServiceException;
import com.ibm.websphere.management.exception.ConnectorException;
import com.ibm.websphere.management.exception.AdminException;
import com.ibm.websphere.management.application.*;
import com.ibm.websphere.pmi.*;
import com.ibm.websphere.pmi.stat.*;

public static void connectToServer(){

Properties props = new Properties();
props.put("type", "SOAP");
props.put("host", hostName);
props.put("port", "8880");
props.put("username", "username");
props.put("password", "password");

//***********************************************************
// if global security enabled. you need the following configurations
//***********************************************************

props.put(AdminClient.CONNECTOR_SECURITY_ENABLED, "true");
props.put("com.ibm.ssl.keyStoreFileBased", "true");
props.put("com.ibm.ssl.trustStoreFileBased", "true");
props.put("com.ibm.ssl.keyStore", keyStoreFile);
props.put("javax.net.ssl.keyStore", keyStoreFile);
props.put("com.ibm.ssl.keyStorePassword", keyPassword);
props.put("javax.net.ssl.keyStorePassword", keyPassword);
if (keyStoreFile.endsWith(".p12") || keyStoreFile.endsWith(".P12"))
{
props.put("com.ibm.ssl.keyStoreType", "PKCS12");
props.put("javax.net.ssl.keyStoreType", "PKCS12");
} else
{
props.put("com.ibm.ssl.keyStoreType", "JKS");
props.put("javax.net.ssl.keyStoreType", "JKS");
}
props.put("com.ibm.ssl.trustStore", trustStoreFile);
props.put("javax.net.ssl.trustStore", trustStoreFile);
props.put("com.ibm.ssl.trustStorePassword", trustPassword);
props.put("javax.net.ssl.trustStorePassword", trustPassword);
if (trustStoreFile.endsWith(".p12") || trustStoreFile.endsWith(".P12"))
{
props.put("com.ibm.ssl.trustStoreType", "PKCS12");
props.put("javax.net.ssl.trustStoreType", "PKCS12");
} else
{
props.put("com.ibm.ssl.trustStoreType", "JKS");
props.put("javax.net.ssl.trustStoreType", "JKS");
}
try
{
adminClient = AdminClientFactory.createAdminClient(props);
System.out.println("Connect to "+hostName+":"+portNumber+" Successfully");
}
catch (ConnectorException e)
{
System.out.println("Failed to Connect to "+hostName+":"+portNumber);
System.out.println("Exception creating admin client: " + e);
e.printStackTrace();
System.exit(-1);
}
}

it is better to use IBM WebSphere Application java to run the application. I see some exceptions if we use SUN Java.

WPS - trace for Web Service request

2011-03-06T17:09:00.001-05:00

Web Service is very important part in SOA world for WebSphere, both WAS and WPS. Sometimes, you need to check the contents of web service request and web service reply. the following trace will show these contents in trace.log

com.ibm.ws.webservices.trace.MessageTrace=all

enable it in runtime and you will see the following:

[3/6/11 22:05:13:697 EST] 000088de MessageTrace 3 WSWS3569I: Inbound HTTP SOAP request:
Content-Type: text/xml; charset=utf-8
Message contents:

<?xml version="1.0" encoding="UTF-8"?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://
www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><soapenv:Body><processTicket xmlns="http://RSDWorld
/IF_RSD"><ticket xmlns="">xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx</soapenv:Body></soapenv:Envelope>

and

[3/6/11 22:05:14:198 EST] 000088de MessageTrace 3 WSWS3572I: Outbound HTTP SOAP response:
Content-Type: text/xml; charset=utf-8
Message contents:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/
" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><soapenv:Header/><soapenv:Body>xxxxxxxxxxxxxxxxxxxx
</soapenv:Body></soapenv:Envelope>

this trace works for both WAS and WPS

WAS7 - "enum cannot be resolved to a type” error when deploying the module on WAS7

2011-03-02T09:10:00.001-05:00

When deploying an EAR file including source code, you may see the error "enum cannot be resolved to a type" error and the EAR file failed to deploy.

for solve this issue:

(1) In RAD, select the EAR project, then click "Project"->"Properties", click "Java Compiler" , make sure "Compiler compliance level" is 1.6

(2) export the EAR file with the option "Export source files"

when deploying the EAR file from WebSphere Administrative console, you have to specify the "JDK Compliance Level" as "6.0" , see the following screenshot

After specified the JDK Compliance level correctly, the error should be gone.

WPS - Uninstall WPS6.1 silently in AIX

2011-02-28T06:10:00.001-05:00

Compared with uninstalling WPS6.0, it is much easier to uninstall WPS6.1 silently on AIX.

IBM introduced more parameters for uninstall scripts. You can follow the steps

(1) stop All WPS6.1 processes.

(2) logon the WPS server with the user "root"

(3) go to the directory /IBM/WebSphere/ProcServer/uninstall.wbi

(4) run the following command:

./uninstall -OPT isUmbrellaUninstall="true" -OPT removeProfilesOnUninstall="true" -silent

the output should like this:

I       Process Type: uninstall
I       Install Type: nonOS400
I       Install Mode: silentMode
I       #Received OPT Properties
#Mon Feb 28 10:38:27 EST 2011
isUmbrellaUninstall=true
removeProfilesOnUninstall=true

INSTCONFPARTIALSUCCESS: The profiles no longer exist, but errors occurred. For more information, consult /IBM/WebSphere/ProcServer/logs/manageprofiles/deleteAll.log.

you may see some alerts, but when you check the log file, you will see the the profile already removed.

<logger>com.ibm.wsspi.profile.WSProfileCLI</logger>
<level>INFO</level>
<class>com.ibm.wsspi.profile.WSProfileCLI</class>
<method>invokeWSProfile</method>
<thread>11</thread>
<message>Returning with return code: INSTCONFSUCCESS</message>
</record>

and if you check the unistall log files at the directory /IBM/WebSphere/ProcServer/logs/uninstall, you will see uninstall is successful.

(Feb 28, 2011 10:49:00 AM), Process, com.ibm.ws.install.ni.ismp.actions.ISMPLogSuccessMessageAction, msg1, INSTCONFSUCCESS

At the same time, on AIX, you can run "lslpp -l |grep -i websphere" to check if the WebSphere package already removed

(5) remove the WebSphere directories.