Adapt the path and the user as necessary.
Copy the file in the appropriate location (ie : /var/svc/manifest/local/squashtm.xml

Import it into the smf system and enable it:

$ sudo /usr/sbin/svccfg import var/svc/manifest/local/squashtm.xml
$ sudo /usr/sbin/svcadm enable squash-tm

You can then check the log file and see that it’s coming up:

$ tail -f /var/svc/log/application-squash-tm\:default.log
[ Nov 21 10:22:20 Enabled. ]
[ Nov 21 10:22:20 Executing start method ("java -Xmx512m -server -Dfelix.config.properties=file:../conf/felix.config.properties -Dfelix.system.properties=file:../conf/felix.system.properties -jar /opt/squash-tm/bin/org.apache.felix.main-3.2.1.jar") ]
[ Nov 21 10:22:20 Ignoring duplicate environment variable "PATH=/usr/sbin:/usr/bin". ]
Auto-deploy install: org.osgi.framework.BundleException: Bundle symbolic name and version are not unique: org.apache.felix.framework:3.2.1
2011-11-21 10:22:23.512::INFO:  Logging to STDERR via org.mortbay.log.StdErrLog
2011-11-21 10:22:23.514:org.squashtest.csp.core.jetty.start.osgi.Activator:INFO:  Using custom XML configuration file:/opt/squash-tm/bin/../conf/services/squash-jetty.xml
2011-11-21 10:22:23.523:org.squashtest.csp.core.jetty.start.osgi.Activator:INFO:  Starting Jetty 6.1.9 ...
2011-11-21 10:22:23.524:org.squashtest.csp.core.jetty.start.osgi.Activator:INFO:  Created Jetty logging folder /opt/squash-tm/bin/logs
2011-11-21 10:22:23.949::INFO:  Redirecting stderr/stdout to /opt/squash-tm/bin/logs/2011_11_21.stderrout.log

Use the Solaris svcs command to check the server’s status:

$ svcs -l squash-tm
fmri         svc:/application/squash-tm:default
name         Squash TM Server
enabled      true
state        online
next_state   none
state_time   Sun Nov 21 10:22:20 2011
logfile      /var/svc/log/application-squash-tm:default.log
restarter    svc:/system/svc/restarter:default
contract_id  2139
dependency   require_all/none svc:/milestone/multi-user-server (online)