Google Postini Directory Sync Configuration Guide - Manual (Page 55)

IBM Lotus Domino Directory Server 55
• Create a server configuration document
• Download Apache Xerces v1.4.4, Apache SOAP v2.3.1, Java J2SE SDK
v1.4.2 Update 10
• Install these libraries on your DSML Server
• Download Apache Xerces v2.7.1 and rename xml-apis.jar to
XMLParserAPIs.jar
• Install this library on your DSML Server
• Install WebSphere Application Server on your DSML Server
• Copy soap.jar and soap.war files into your installation
• Create DSMLv2.xsd and place the file in your schemas directory
• Create soap-env.xsd and place the file in your schemas directory
• Edit the server.xml file
• Place .jar files in your app directory
• Install SOAP into WebSphere Application Server
• Stop and restart WebSphere Application Server
• Unpack DSML.zip
• Modify deployDSMLSoap.xml
• Install DSML into SOAP on WebSphere server
• Configure CLASSPATH on your DSML Server
• Collect LDAP information from your directory server
• Create batchrequest.dsml file
Troubleshooting
If an error occurs when you attempt to verify the installation, check the error
message against the error messages below to find the source of the problem.
Exception in thread “main” java.lang.NoClassDefFoundError: com/ibm/ldap/
dsmlClient/DsmlSoapClient
Cause: .jar files for IBM DSML are not in your CLASSPATH. Refer to section 2.9
for information about setting your CLASSPATH
[SOAPException: faultCode=SOAP-ENV:Client; msg=Error opening socket:
java.net.ConnectException: Connection refused: connect;
targetException=java.lang.IllegalArgumentException: Error opening socket:
java.net.ConnectException: Connection refused: connect]
Cause: WebSphere Express is not running. Refer to section 2.4 and section 2.7 to
verify the WebSphere is running and SOAP is installed.