Since I am currently not aware of third party products shipping an SMF service for their application (which does not mean much, ie. they could well exist) I just make two generic statements:
1) If for that application a standard Sun Cluster agent exists, then the instructions for installing this data service would include to disable the SMF on the cluster nodes (like on pre Solaris 10 systems the legacy runlevel script would need to get deactivated).
2) If for that application no standard Sun Cluster agent exists, then one would have the ability to leverage the new proxy SMF resource types coming with Sun Cluster 3.2. They would use the SMF manifest to start and stop the application. Note that by using this resource type you would not have any application fault monitoring.
Details to 2) can be found at
http://blogs.sun.com/SC/entry/making_smf_services_highly_available and
http://docs.sun.com/app/docs/doc/819-2974/6n57pdk2b?a=view
Greets
Thorsten
Message was edited by:
Thorsten.Frueauf
Hi
I use one of 3 solutions if I have to integrate an application without cluster agent:
1) If there is a chance I will need the same application unclustered somewhere, then I create an SMF Manifest and integrate the service via the SMFproxy into the cluster
2) If I need a probe for the service, and have Suncluster 3.2 with clustered Zones, then I again create an SMF Service, but control it via sczsmf in a zone, this allows you to specify a probe script.
2) Otherwise I use a simple wraper script which implements start/stop/probe and create a GDS.