Skip to main content

Steps for patching IBM process manager 9.1

IBM Process Manager patching steps:


Stop PM - If your PM was setup to use EGO then use EGO to stop or use root id to stop process manager. During the patching PM should be stopped.
[root@localhost ~]# . /sas/pm/jfd/conf/profile.js
[root@localhost ~]# cd /sas/pm/jfd
[root@localhost jfd]# jadmin stop
Shutting down jfd ...
jfd is being shut down.

Checking whether the jfd is stopped. It will take atlest 5 minutes to stop. In my first check it is not stopped but in second check it is stopped.

[root@localhost jfd]# ps -ef | grep jfd
root      1336 12194  0 12:00 pts/11   00:00:00 grep jfd
lsfadmin 43550     1  0 11:39 ?        00:00:04 /sas/pm/jfd/9.1/linux2.6-glibc2.3-x86_64/etc/jfd
lsfadmin 43604 43550  0 11:39 ?        00:00:00 /sas/pm/jfd/9.1/linux2.6-glibc2.3-x86_64/etc/eem.local
[root@localhost jfd]# ps -ef | grep jfd
root      1336 12194  0 12:00 pts/11   00:00:00 grep jfd

Copy Work directory:
[root@localhost jfd]# cp -a work work.20150619

I am copying orignal file from source and placing it under a folder named as pm_patch.

Backup original jfd :
[root@localhost jfd]# cp -a /sas/pm/jfd/9.1/linux2.6-glibc2.3-x86_64/etc/jfd /sas/pm_patch/jfd.original

Copy patch. Verify md5 sum and permission:
[root@localhost jfd]# ls /sas/pm_patch/*
/sas/pm_patch/74837.057.649.checksum_2_.md5  /sas/pm_patch/74837.057.649.readme_4_.txt  /sas/pm_patch/jfd.original
/sas/pm_patch/74837.057.649.jfd_2_           /sas/pm_patch/jfd.20150616

In above folder /sas/pm_patch/74837.057.649.jfd_2_ is the patch I am going to apply. So I am copying it to the jfd directory.

[root@localhost jfd]# cp -a /sas/pm_patch/74837.057.649.jfd_2_ /sas/pm/jfd/9.1/linux2.6-glibc2.3-x86_64/etc/jfd
cp: overwrite `/sas/pm/jfd/9.1/linux2.6-glibc2.3-x86_64/etc/jfd'? y

It will ask whether to overwrite, type y

[root@localhost log]# ls -l  /sas/pm/jfd/9.1/linux2.6-glibc2.3-x86_64/etc/jfd
-rwxr-xr-x 1 lsfadmin sas 9521256 Aug 1 11:12 /sas/pm/jfd/9.1/linux2.6-glibc2.3-x86_64/etc/jfd

Checking md5, md5sum is the command to get the check sum. Compare the original and copy like below:
[root@localhost jfd]# md5sum /sas/pm/jfd/9.1/linux2.6-glibc2.3-x86_64/etc/jfd
c74e5fb318441b2da3f504486e205de1  /sas/pm/jfd/9.1/linux2.6-glibc2.3-x86_64/etc/jfd
[root@localhost jfd]# more /sas/pm_patch/74837.057.649.checksum_2_.md5
c74e5fb318441b2da3f504486e205de1  jfd

Clean log and start PM:
[root@localhost jfd]# cd log
[root@localhost log]# ls
eem.localjobs.log.localhost  jfd.log.localhost  jfd.log.localhost.bkup
[root@localhost log]# mv jfd.log.localhost jfd.log.localhost.1
[root@localhost log]# jadmin start
Starting up jfd ...

Verify log and Flow Manager.
[root@localhost log]# grep daemon jfd.log.dc4coj
2015 Aug 1 12:06:13 3828 3828 5 Process Manager daemon started.

Comments

Post a Comment

Popular posts from this blog

Insufficient authorization to access PIPE error in SAS EG

Issue: When I tried to run SAS code in SAS Enterprise Guide it throws following errors: ERROR: Insufficient authorization to access PIPE. ERROR: Error in the FILENAME statement. Screenshot of error: Solution: This error occurs when you try to run OS commands in SAS code. To run the OS commands in SAS code you need to enable XCMD option. You check it in SAS Management Console by following below steps.   Open SMC -> Expand Servers -> Expand   In SASApp , expand Logical Workspace Server -> right click on Workspace Server. Click properties -> option tab -> advanced options -> launch properties. Check whether Allow XCMD is checked. The issue arises if the Allow XCMD is not checked. In above image, Allow XCMD option is not checked. It should be checked to run OS commands from SAS code. In Unix /Linux machines, this XCMD option can be enabled by using system option XCMD in sasv9 config file or workspaceserver.sh script f...
2 comments
Read more

The authentication server is not SETUID ROOT error in SAS

Question: When validating the SAS Server from SAS Management Console, I received the following error: The authentication server is not SETUID ROOT.  So, I ran the setuid.sh utility and restarted the services many times. I just checked the elssrv sasauth sasperm setuid bit. There were no error in sasauth-debug.log, sasauth-access.log, sasauth-error.log.  Any suggestions? Answer: Please do the following:    1) Run /<SASConfig>/Lev<X>/ObjectSpawner/ObjectSpawner.sh stop  2) Edit /<SASConfig>/Lev<X>/ObjectSpawner/ObjectSpawner.sh and add the code shown below right after SCRIPT=`basename $0`:  if [ -n ""$TKPATH"" ]; then  unset TKPATH  fi   if [ -n ""$TK_PATHLIST"" ]; then  unset TK_PATHLIST  fi    3) Run /<SASConfig>/Lev<X>/ObjectSpawner/ObjectSpawner.sh start  The above code change in ObjectSpawner.sh should fix the issue.
1 comment
Read more

SAS - CLI error trying to establish connection

Issue: User asked me to make a database connectivity to SQL Server. They provided following details SQL server hostname and ip address Database/DSN name Username Password I made entry in ODBC.ini file. You know, SQL Server entries were made in ODBC.ini and Oracle entries were made in TNS.ora file. Everything went fine, took back up of odbc.ini, made entry and saved the file. So to test this connection I ran the libname statement in SAS Enterprise Guide 6.1. It throwed following error. Error Message: My DB team showed that they are able to login   14 GOPTIONS ACCESSIBLE; 15 LIBNAME test ODBC DATASRC=SGE_DS SCHEMA=VST USER=sales PASSWORD=XXXXXXXXX; ERROR: CLI error trying to establish connection: [SAS/ACCESS to SQL Server][ODBC SQL Server Legacy Driver][SQL Server]Login failed for user 'sales'. Solution: First I suspected that Login failed for user 'sales' meant the password provided by DB team was wrong. They responded that they were able to login wi...
3 comments
Read more