Just finished my kit.

http://solaris-fr.org/home/lib/exe/fetch.php?media=contribs%3Andowas.tgz
README included. See copy at the end of this mail.

Documentation in french (to be finished) :
http://solaris-fr.org/home/contribs/smf/was



Nicolas

P.S.:
Based on Albert Leigh proposition
See http://blogs.sun.com/sunabl/entry/a_service_manifest_for_websphere


README copy



========================        NDOwas kit


This kit is provided to help integrating WebSphere Application Server  
(was)
into Solaris Service Management Facility (SMF).

This is version 1.0, based on my poor knowledge of was and my  
particular need.
Don't hesitate to improve and re-distribute it.

This kit is freely distributable under the CDDL License.


Labege le 11 decembre 2007

Nicolas Dorfsman    / SunContributorAgreement #OS0170
Membres du GUSES / http://www.guses.org
ndo at unikservice.com

*    INSTALLATION

- Check /usr/local exists or symlinks to some existing directory
- Execute install script


*    CONFIGURATION

   Three instances are created by default :

STATE          STIME    FMRI
disabled       14:39:59 svc:/application/was61:manager
disabled       14:40:00 svc:/application/was61:server
disabled       14:40:01 svc:/application/was61:node

         **  Choose the type of service you want to run and configure  
it thru svccfg.
         The start/stop methode is using was/profiles was/name and was/ 
service like this:

PROFILES_DIR=`getproparg was/profiles`
PROFILE_NAME=`getproparg was/name`
SERVICE=`getproparg was/service`
#
#
WAS_BIN="${PROFILES_DIR}/${PROFILE_NAME}/bin"
START_NODE="${WAS_BIN}/start${SERVICE}.sh"
STOP_NODE="${WAS_BIN}/stop${SERVICE}.sh"


e.g. for node (should be the same for appserver or manager) :

[root at mazone /]$ svccfg
svc:> select was61:node
svc:/application/was61:node>editprop

a editor will open and content will look like :

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
select svc:/application/was61:node

# Property group "method_context"
# delprop method_context
# addpg method_context framework
# setprop method_context/group = astring: *(was)*      <== group id  
for execution

# setprop method_context/limit_privileges = astring: (:default)
# setprop method_context/privileges = astring: (:default)
# setprop method_context/project = astring: (:default)
# setprop method_context/resource_pool = astring: (:default)
# setprop method_context/supp_groups = astring: (:default)
# setprop method_context/use_profile = boolean: (false)
# setprop method_context/user = astring: (wasadmin)    <== user id for  
execution

# setprop method_context/working_directory = astring: (:default)

# Property group "was"
# delprop was
# addpg was application
# setprop was/name = astring: (mynode)   <=== name of the was profile
# setprop was/service = astring: (Node)

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

customize properties as you need. For example, if your profile name is  
"BestApp", put:

setprop was/name = astring: "BestApp"

Save/Quit the editor and then :

svc:/application/was61:node>quit
[root at mazone /]$ svcadm refresh was61:node

         **  Check the websphere directories in service properties

[root at mazone /]$ svcprop -p was/profiles was61

    This property is set on was61 service (not on instance). So you
could modify it on the service for any instance (select was61 under  
svccfg)
or for one instance in particular (select was61:instance)


Then...you could enable your service !


Reply via email to