Deployment-Solaris WO5.3.3

1

Setup WebObjects 5.3.3 on Solaris 10 x86

2

Rev 1 1.01.2008

3

Johann Werner (werner at isd dot uni-stuttgart dot de)

4

based on description of Francois Bientz for setup on FreeBSD

5

6

Rev 2 28.04.2008

7

John Bruce (john at kinrossgroup dot com)

8

added intial SMF scripts for wotaskd & javamonitor

9

10

That's the very first time I am using Solaris so I don't guarantee that my instructions are complete nor comply to standard Solaris naming/best-practice/whatsoever conventions. Feel free to comment/correct it!

11

12

What I used to test this setup:

13

14

Parallels Desktop

15

Solaris 10 8/07 x86 (Entire Solaris Software Group installation)

16

Access to an OS X Server 10.4.x machine that has the WO 5.3.3 files

17

18

= WebObjects 5.3.3 installation =

19

20

This section discusses how you "install" WO 5.3.3 on Solaris to use it as pure application server. You will be able to connect to WO apps by direct connect or use that machine from another machine that runs Apache with WOAdaptor.

21

22

Under Solaris create the following directory where all WO related files will be contained:

/opt/Apple

Inside of this directory create:

/opt/Apple/Logs

/opt/Apple/Library/Frameworks

36

/opt/Apple/Library/PrivateFrameworks

37

/opt/Apple/Library/WebObjects

38

/opt/Apple/Local/Library/WebObjects/Applications

39

/opt/Apple/Local/Library/WebObjects/Extensions

Then copy from the OS X Server machine these files from /System/Library/Frameworks

JavaDirectToWeb.framework

48

JavaDTWGeneration.framework

49

JavaEOAccess.framework

50

JavaEOApplication.framework

51

JavaEOCocoa.framework

52

JavaEOControl.framework

53

JavaEODistribution.framework

54

JavaEOGeneration.framework

55

JavaEOInterface.framework

56

JavaEOInterfaceCocoa.framework

57

JavaEOInterfaceSwing.framework

58

JavaEOProject.framework

59

JavaEORuleSystem.framework

60

JavaEOTool.framework

61

JavaFoundation.framework

62

JavaJDBCAdaptor.framework

63

JavaJNDIAdaptor.framework

64

JavaWebObjects.framework

65

JavaWebServicesClient.framework

66

JavaWebServicesGeneration.framework

67

JavaWebServicesSupport.framework

68

JavaWOExtensions.framework

69

JavaWOJSPServlet.framework

JavaXML.framework

to /opt/Apple/Library/Frameworks

75

76

Next copy from the OS X Server machine these files from /System/Library/PrivateFrameworks

EOPlaceholders.framework

81

JavaMonitor.framework

to /opt/Apple/Library/PrivateFrameworks

86

87

Copy from the OS X Server machine these files from /System/Library/WebObjects

JavaApplications

WODocumentRoot

to /opt/Apple/Library/WebObjects

97

98

Finally you have to copy these files from /Library/WebObjects/Extensions

axis-ant.jar

axis.jar

commons-discovery.jar

commons-logging.jar

jaxrpc.jar

log4j-1.2.8.jar

saaj.jar

wsdl4j.jar

to /opt/Apple/Local/Library/WebObjects/Extensions

114

115

== Create startup scripts for wotaskd and javamonitor ==

116

117

To be able to use the machine as an application server wotaskd has to run. To automatically start wotaskd on startup create the file /etc/rc3.d/S110.wotaskd

#!/bin/sh

NEXT_ROOT=/opt/Apple

case "$1" in

start)

export NEXT_ROOT

${NEXT_ROOT}/Library/WebObjects/JavaApplications/wotaskd.woa/wotaskd &

echo -n ' wotaskd'

;;

stop)

lsof -i tcp:1085 |grep LISTEN | sort -u | awk '{print"kill -9 " $2}' | sh

;;

*)

echo ""

echo "Usage: `basename $0` { start | stop }"

echo ""

exit 64

;;

esac

Then

chmod \+x /etc/rc3.d/S110.wotaskd

If you need to start JavaMonitor too on that machine (remember: only **one** JavaMonitor per subnet) create /etc/rc3.d/S150.javamonitor

#!/bin/sh

NEXT_ROOT=/opt/Apple

case "$1" in

start)

export NEXT_ROOT

${NEXT_ROOT}/Library/WebObjects/JavaApplications/JavaMonitor.woa/JavaMonitor -WOPort 56789 &

165

echo -n 'JavaMonitor'

166

;;

167

stop)

168

lsof -i tcp:56789 |grep LISTEN | sort -u |awk '{print"kill -9 "$2}' | sh

;;

*)

echo ""

echo "Usage: `basename $0` { start | stop }"

echo ""

exit 64

;;

esac

Then

chmod \+x /etc/rc3.d/S150.javamonitor

To be done: Starting wotaskd and JavaMonitor under a specific user/group. As it is shown here the two apps will run with root priviliges. Another approach would be to put them into a Solaris Zone.

189

Also to be done: Instead of using init.d starting these services by SMF.

190

191

=== Using SMF To Manage wotaskd & JavaMonitor ===

192

193

If you are running WO in a non global Zone the **lsof** command will not work as the ##/devices## directory is missing. An alternative to the above scripts are the [[Deployment-Solaris WO5.3.3^wotaskd.smf]] and [[Deployment-Solaris WO5.3.3^javamonitor.smf]] smf scripts attached to this page. I've tried then on a test server and they work for me but I'm a total SMF novice so **use these files at your own risk**.

194

195

Import the files with:

sudo svccfg import wotaskd.smf

200

sudo svccfg import javamonitor.smf

They should start the wotaskd and javamonitor services but if not they can be enabled with:

sudo svcadm enable svc:/webobjects/wotaskd:default

209

sudo svcadm enable svc:/webobjects/javamonitor:default

To confirm they are working kill the running java processes and they should restart. Also you can check the logs usually in ##/var/svc/logs##.

214

215

= Installing JDBC drivers =

216

217

If you want to access a database from your WO apps you have to install appropriate JDBC drivers. In this guide I will use FrontBase drivers as an example.

218

219

Download the database specific drivers from www.frontbase.com (called "WebObjects 5 Plugin" on the download page) and extract the archive. Then you should have two files:

FrontBasePlugIn.framework

frontbasejdbc.jar

The first file is the one you have to add to your WO project. If you have WOnder you can exchange it with the one that comes with WOnder as it is an improved version (though I did not check for differences :)).

Put that file into

/opt/Apple/Local/Library/Frameworks

The second file has to be put into the extensions directory of java

/usr/java/jre/lib/ext

Reboot and you should be able to connect to a FB database from WO.

246

247

= Compiling WOAdaptor and Setting up Apache =

248

249

On Solaris 10 8/07 there is preinstalled Apache in versions 1.3 and 2.0. In this how-to we will compile an adaptor for Apache 2.0. It took me quite long to get the compile process right on Solaris so I changed some things and won't refer to the adaptor files in WOnder CVS. Instead get this [[SolarisAdaptor archive>>Deployment-Solaris WO5.3.3^SolarisAdaptor.zip]].

Put it e.g. into

/tmp

Then unzip it with

unzip SolarisAdaptor.zip

Next type in these commands

cd SolarisAdaptor

./makeAdaptor.sh

The file makeAdaptor.sh contains:

#!/bin/sh

/usr/apache2/bin/apxs -c -i -a -DSINGLE_THREADED_ADAPTOR mod_WebObjects.c appcfg.c cfgparse.c config.c hostlookup.c

282

list.c listing.c loadaverage.c loadbalancing.c log.c MoreURLCUtilities.c nbsocket.c PB.project Platform.c random.c

283

request.c response.c roundrobin.c shmem.c strdict.c strtbl.c transaction.c transport.c wastring.c womalloc.c

284

WOURLCUtilities_3.c WOURLCUtilities.c xmlcparser.c xmlctokenizer.c xmlparse.c

It uses the apache extension tool to compile all source files, links them together and installs them in the right location for apache 2. It even inserts the LoadModule directive into your httpd.conf file! What a luxury ;)

289

You notice the "-DSINGLE//THREADED//ADAPTOR". You can change it to --DMULTIPLE//THREADED//ADAPTOR though I don't know if it works and exactly what advantages you will get from (besides having multiple threads).--

290

291

The next step is to put the WO config file into the right location:

cp webobjects.conf /etc/apache2/

That config file has been altered in three ways:

300

301

* the LoadModule directive is commented out as it was automatically added to the main config file by apxs

302

* the WebObjectsDocumentRoot points to the standard apache2 location /var/apache2/htdocs

303

Change it if you have moved your htdocs to another place

304

* the WebObjectsAlias has been changed to /Apps/WebObjects

305

Feel free to modify the alias to any string you want. It has to be different from "cgi-bin" as it does not work. I didn't investigate on that. Note that you have to set the appropriate setting in JavaMonitor too. Go to JavaMonitor and click on the "Site" tab. On top there is a text field "URL to Adaptor". Put in the URL of your webserver with the changed WO alias.

306

307

Then lastly add as the last line of your current apache configuration file:

Include /etc/apache2/webobjects.conf