Hi,
What is the best and accurate way(command) to check the installed JES 2005 Q4 Product version on the solaris platform.
I wanted to check the installed application server, web server, message queue, portal server , access manager, directory server, meta directory, web reverse proxy, directory proxy.
Thanks in advance.
Each product will have their own best way for determining the product
version. For example with Message Queue you can run 'imqcmd -version'.
Otherwise you can always look at the versions of the packages installed on
your system. Some examples from my system:
$ pkgparam -v SUNWiqr DESC VERSION SUNW_PRODVERS
DESC='Sun Java(tm) System Message Queue Root Package'
VERSION='3.7,REV=2006.06.18.22.34'
SUNW_PRODVERS='3.7.0.1'
$ pkgparam -v SUNWasu DESC VERSION SUNW_PRODVERS
DESC='Application Server (usr)'
VERSION='8.2,REV=2006.08.16.09.11'
SUNW_PRODVERS='8.2'
Other packages you can query for JES 4 (2005Q4):
Web Server: SUNWwbsvr
Portal Server: SUNWps
Access Manager: SUNWamsvc
Directory Server: SUNWdsvu
Directory Proxy: SUNWdps
Joe
Hi,
I am getting two different version for the different commands.
pkginfo -l SUNWmsgmf
PKGINST: SUNWmsgmf
NAME: Sun Java System Messaging Server Sieve Filter User Interface
CATEGORY: application
ARCH: sparc
VERSION: 6.0,REV=2003.10.29
BASEDIR: /opt/SUNWmsgsr
/opt/SUNWmsgsr/lib/version
Sun Java(tm) System Messaging Server 6.1 (built Apr 28 2004)
libimta.so 6.1 (built 13:10:36, Apr 28 2004)
Which is the right version ?
Much Appreciated..
The prodreg command doesn't show the version.
/usr/bin/prodreg browse -u "Java Enterprise System" -u "SunONEMessageQueue"
BROWSE #+/-/.UUID# NAME
======== ======== ==================================== == ===================
1 - root1 System Registry
4 -Java Enterprise System1
6-SunONEMessageQueue 1
61.SUNWiqr1
62.SUNWiqu1
63.SUNWiqlpl1
64.SUNWiqdoc1
65.SUNWiquc1
66.SUNWiqum1
67.SUNWiqjx1
68.SUNWiqfs1
69.SUNWiqcrt1
70.SUNWiqcdv1
71.SUNWiqlen1
thank you
> Hi,
>
> I am getting two different version for the different
> commands.
>
> pkginfo -l SUNWmsgmf
>
>PKGINST: SUNWmsgmf
> NAME: Sun Java System Messaging Server Sieve
> Filter User Interface
> CATEGORY: application
>ARCH: sparc
> RSION: 6.0,REV=2003.10.29
>BASEDIR: /opt/SUNWmsgsr
> /opt/SUNWmsgsr/lib/version
> Sun Java(tm) System Messaging Server 6.1 (built Apr
> 28 2004)
> libimta.so 6.1 (built 13:10:36, Apr 28 2004)
>
> Which is the right version ?
>
> Much Appreciated..
I suggest you to trust /opt/SUNWmsgsr/lib/version instead of pkginfo. Unfortunately packages revisions are not as accurate as they should be.
best regards,
Aleksandar Bilanovic
> The prodreg command doesn't show the version.
>
> /usr/bin/prodreg browse -u "Java Enterprise System"
> -u "SunONEMessageQueue"
> BROWSE #+/-/.UUID
try to export DISPLAY and to run prodreg in GUI mode. Versions should be in left panel when you choose certain component.
best regards,
Aleksandar Bilanovic
For some products the SUNW_PRODVERS field may contain a more
accurate version. This is because patches can't update VERSION, but
can update SUNW_PRODVERS. Some products (like Messaging Server)
have shipped feature updates as patches (which are freshbitted onto the
previous version of the package to generate a new package). So you
may find that VERSION is 6.0, but SUNW_PRODVERS is 6.1. Try:
pkgparam -v SUNWmsgmf VERSION SUNW_PRODVERS
And SUNW_PRODVERS may match /opt/SUNWmsgsr/lib/version. If it
doesn't I'd trust /opt/SUNWmsgsr/lib/version like Aleksandar says.
Note this isn't true for all packages. Some packages don't use
SUNW_PRODVERS this way.
Joe
> Hi,
>
> I am getting two different version for the different
> commands.
>
> pkginfo -l SUNWmsgmf
>
>PKGINST: SUNWmsgmf
> NAME: Sun Java System Messaging Server Sieve
> Filter User Interface
> CATEGORY: application
>ARCH: sparc
> VERSION: 6.0,REV=2003.10.29
>BASEDIR: /opt/SUNWmsgsr
> /opt/SUNWmsgsr/lib/version
> Sun Java(tm) System Messaging Server 6.1 (built Apr
> 28 2004)
> libimta.so 6.1 (built 13:10:36, Apr 28 2004)
>
> Which is the right version ?
>
> Much Appreciated..
So far i have found the commands/files to check the version for the below mentioned JES components..
Portal Server - /opt/SUNW/ps/lib/PSversion.properties
Message queue - /usr/bin/imqadmin -version
Messaging server - /opt/SUNWmsgsr/lib/version
What is the command/file to check the version for the below mentioned JES components?
Web server
Application server
Access manager
Directory server
Directory proxy server
calendar server
instant messaging server
identity server
Administartion server
Thank you very much for the reply.
> So far i have found the commands/files to check the
> version for the below mentioned JES components..
>
> Portal Server -
> /opt/SUNW/ps/lib/PSversion.properties
>
> Message queue - /usr/bin/imqadmin -version
>
> Messaging server - /opt/SUNWmsgsr/lib/version
>
> What is the command/file to check the version for the
> below mentioned JES components?
>
> Web server
> Application server
> Access manager
> Directory server
> Directory proxy server
> calendar server
> instant messaging server
> identity server
> Administartion server
>
> Thank you very much for the reply.
Hello,
for AM and AS you can check version as follows:
/opt/SUNWappserver/sbin/asadmin version
/opt/SUNWam/bin/amadmin --version
and for DS/DPS I would like to know which version of JES are you using (if you are using jes5 it's DS/DPS 6.0.. and if you are JES2,3,4 it's 5.2...)
for other components i can tell you only if it's for JES4, since i don't have JES5 comms installed here right now.
best regards,
Aleksandar Bilanovic
Hello,
credit for CS/DS goes to Rastislav Kanocz and Nemanja Lukic
for DS:
/usr/ds/v5.2/bin/slapd/server/ns-slapd -version
Sun Microsystems, Inc.
Sun Java(TM) System Directory Server/5.2_Patch_4 B2005.230.0405
for CS:
/opt/SUNWics5/cal/bin/csstart version
Build date is: Oct 15 2003
Version is: 2005Q4
for IM:
/opt/SUNWiim/sbin/imadmin version
7.0,REV=2004.11.24.05.19.40
for Administartion server, DPS and Identity I don't know.
p.s. Am I going to get those duke stars or not ? :)
best regards,
Aleksandar Bilanovic
Hi,
I am getting this error
/usr/ds/v5.2/bin/slapd/server/ns-slapd -version
ld.so.1: /usr/ds/v5.2/bin/slapd/server/ns-slapd: fatal: libsh.so: open failed: No such file or directory
/opt/SUNWics5/cal/bin/csstart version
ld.so.1: /opt/SUNWics5/cal/lib/csstart: fatal: libcore_store10.so: open failed: No such file or directory
Killed
/opt/SUNWiim/sbin/imadmin version
Configuration file ./../config/iim.conf is missing, exiting
any clue?
PS: Yes.
> Hi,
>
> I am getting this error
>
> /usr/ds/v5.2/bin/slapd/server/ns-slapd -version
>
> ld.so.1: /usr/ds/v5.2/bin/slapd/server/ns-slapd:
> fatal: libsh.so: open failed: No such file or
> directory
>
> /opt/SUNWics5/cal/bin/csstart version
> ld.so.1: /opt/SUNWics5/cal/lib/csstart: fatal:
> libcore_store10.so: open failed: No such file or
> directory
> Killed
>
> /opt/SUNWiim/sbin/imadmin version
> onfiguration file ./../config/iim.conf is missing,
> exiting
>
> any clue?
>
> PS: Yes.
for first two try with zeroing LD_LIBRARY_PATH:
LD_LIBRARY_PATH="" /opt/SUNWics5/cal/bin/csstart version
or
LD_LIBRARY_PATH= /opt/SUNWics5/cal/bin/csstart version
or
unset LD_LIBRARY_PATH
and then commands
or
export LD_LIBRARY_PATH=""
and then commands
same goes for DS
and for IM, it look that you are missing config for iim. I don't know you scenario but maybe you should run configuration for IM, (DISPLAY and run /opt/SUNWiim/configure). again i don't know what exact your deployment is ....
best regards,
Aleksandar Bilanovic
> hi
>
> what is the command to check the installed
> version details for these two products?
>
> Directory Proxy Version 5.2 Patch 4
>
>
> Web ServerVersion 6.1 SP5
>
>
> hanks in advance
DPS:
/var/opt/mps/serverroot/bin/dps/server/bin/ldapfwd -v
Sun ONE Directory Proxy Server Version 5.2_Patch_4
Built 20050705.172444 on i386-solaris.
System has 2046M memory and 65536 file descriptors.
WS:
LD_LIBRARY_PATH=/usr/lib/lwp:/opt/SUNWwbsvr/bin/https/lib:/usr/jdk/entsys-j2se/ jre/lib/i386/server:/usr/jdk/entsys-j2se/jre/lib/i386:/usr/jdk/entsys-j2se/jre/l ib/i386/native_threads:/opt/SUNWhvra/framework/lib32:/opt/SUNWhvra/utils/lib:/us r/lib/mps/secv1:/usr/lib/mps:/usr/lib/mps/sasl2 /opt/SUNWwbsvr/bin/https/bin/webservd -v
best regards,
Aleksandar Bilanovic
> Still am getting the same error..I am trying to
> resolve it.
>
> Thanks for your help..
O.k. in that case try to determine what is correct LD_LIBRARY_PATH for given application. for example i was getting:
/opt/SUNWwbsvr/bin/https/bin/webservd -v
ld.so.1: webservd: fatal: libldap50.so: open failed: No such file or directory
Killed
pgrep webservd
2593
2611
2610
2595
2594
2609
pargs -e 2593 | grep LD_LIBRARY_PATH
envp[4]: LD_LIBRARY_PATH=/usr/lib/lwp:/opt/SUNWwbsvr/bin/https/lib:/usr/jdk/entsys-j2se/ jre/lib/i386/server:/usr/jdk/entsys-j2se/jre/lib/i386:/usr/jdk/entsys-j2se/jre/l ib/i386/native_threads:/opt/SUNWhvra/framework/lib32:/opt/SUNWhvra/utils/lib:/us r/lib/mps/secv1:/usr/lib/mps:/usr/lib/mps/sasl2
so try to do the same for other applications, export LD_LIBRARY_PATH that you get from pargs -e and run appropriate command to determine version.
best regards,
Aleksadar Bilanovic
If you have used JES Installer to install JES Products, the Installer does generate a Summary file that contains the installed Products with the associated version.
On Solaris Platform, this summary file is located under :
/var/sadm/install/logs
On linux platform, this summary file is located under :
/var/opt/sun/install/logs
Follows a sample of content of this summary file :
Installation Summary Report
Install Summary
Java Enterprise System 5 : Installed
Sun Java(TM) System Web Server 7.0 : Installed
Sun Java(TM) System High Availability Session Store 4.4 : Installed
Java DB : Installed, Configure After Install
Sun Java(TM) System Message Queue 3.7 UR2 : Installed
Sun Java(TM) System Application Server Enterprise Edition 8.2 : Installed
Sun Java(TM) System Directory Preparation Tool : Installed
Sun Java(TM) System Directory Server Enterprise Edition 6.0 : Installed
Sun Java(TM) System Access Manager 7.1 : Installed
Service Registry 3.1 : Installed, Configure After Install
Sun Java(TM) System Portal Server 7.1 : Installed
Sun Java(TM) System Portal Server Secure Remote Access 7.1 : Installed
Sun Cluster 3.1 8/05 : Installed, Configure After Install
Sun Cluster Agents 3.1 : Installed, Configure After Install
Sun Cluster Geographic Edition 3.1 2006Q4 : Installed, Configure After Install
Sun Java(TM) System Web Proxy Server 4.0.4 : Installed
All Shared Components : Installed, Configure After Install
Sun Java(TM) System Monitoring Console 1.0 : Installed, Configure After Install
LDAP
/{DS Install Root}/bin/slapd/server/ns-slapd -version
LDAP Proxy
/{DS Install Root}/bin/dps/server/bin/ldapfwd -version
App Server
/opt/SUNWappserver/sbin/asadmin version
Web Server
/opt/SUNWwbsvr/https-{any instance}/start -version
Access Manger
<access-manager-install-dir>/bin/amadmin --version
Access Manger Web Policy Agent
grep amAgent in policy agent logs for "Version:". Version is printed in logs each time webserver is rebooted.
/var/opt/SUNWam/agents/debug/_opt_IBMIHS_{app}_conf/
Identity Manger
Make sure the environment variable WSHOME is set. If not then set as shown below -
#WSHOME=/var/opt/SUNWappserver/domains/domain1/applications/j2ee-modules/idm ; export WSHOME
To check the installed Version execute the following command
# $WSHOME/bin/lh console
Configurator> version
