WSA not working on WebSphere

Hello,

Trying to deploy a wsm and associated wsdl on a wsa running remotely on WebSphere. The admin server cannot connect to the wsa..

Please find two scenarios where the WebSphere App Server is remote to the Openedge install and another where they are local to the same machine

---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Scenario 1

A  Suse Linux 32 bit VMWare Image and a AIX 64 Bit Machine

1. Suse- WebSphere Application Server V7.0.0.7 Base Trial

2. AIX- OpenEdge 10.0B

S1.1. Created a new wsa1 instance of WSA in Machine 1. by copying in the ubroker.properties file the default WSA entries

S1.2. Made a copy of the servlets/wsa directory of the $DLC Directory from 2. to 1. and changed the web.xml in servlets/wsa.web.xml

S1.3.  Also Copied the ubroker.properties file from $DLC/properties folder from Machine 2. to 1

S1.4. Please find the ubroker.properties file for WSA.wsa1 entries which is in Machine 2.

The logFile is created where the wsa web application runs i.e in Machine 1.

[WSA.wsa1]

    actionalEnabled=0

    actionalGroup=OpenEdge

    adminAuth=0

    adminEnabled=0

    adminRoles=PSCAdmin,PSCOper

    adminSoapAction=urn:services-progress-com:wsa-admin:01

    appAuth=0

    appProtocol=0

    debugClients=

    enableWsdl=1

    enableWsdlListings=1

    httpErrorPage=httperror.html

    location=local

    logAppend=1

    logEntries=

    logEntryTypes=WSADefault

    logFile=/usr/wrk/wsa1.log

    loggingLevel=4

    logMsgThreshold=-1

    logThreshold=0

    noWsdlPage=

    numLogFiles=3

    proxyHost=

    proxyPassword=

    proxyPort=0

    proxyUsername=

    webAppEnabled=1

    webServerAuth=0

    workDir=$WRKDIR

    wsaUrl=http://172.16.99.7:9080/wsa/wsa1

    wsdlAuth=0

    wsdlListingPage=WSDLListing.html

In The machine for the WebSphere Application Server Machine 1, the ubroker.properties file may consists of **ONLY** the WSA.wsa1 entries

S1.5. Changes made to the web.xml in Machine 1. after copying the $DLC/servlets/wsa folder from Machine 2.

S1.5.A.

<init-param>

<param-name>InstallDir</param-name>

<param-value><<Any Directory>></param-value>

</init-param>

S1.5.B.

<init-param>

<param-name>instanceName</param-name>

<param-value><<Web Services Adapater Instance Name as in the ubroker.properties file of both 1. and 2)>></param-value>

</init-param>

S1.5.C.

<init-param>

      <param-name>propertyFileName</param-name>

      <param-value><<Path to ubroker.properties file in Machine 1.>></param-value>

    </init-param>

S1.5.D.

    <init-param>

      <param-name>deploymentDir</param-name>

      <param-value><<any directory name>></param-value>

</init-param>

S1.5.E.

Commented out all security constraints tags

S1.5.F. Check for the WSA instance name in all servlet mappings to be wsa1

S1.6.  tar and scp  the $DLC/java libraries from Machine 2. to Machine 1., uncompress the java folder in the Directory mentioned in 4.A

S1.7. Make the build.xml in the wsa folder of the copied servlets directory in machine 1

<?xml version="1.0"?>

<project name="wsa" default="all" >

<target name="all" depends="makewar"/>

  <target name="makewar">

    <tstamp/>

    <echo message="Creating the wsa.war file..."/>

    <war warfile="wsa.war" webxml="WEB-INF/web.xml" >

      <fileset dir="." includes="*.xsd,*.jar,*.html"/>

      <zipfileset dir="WEB-INF/lib" includes="*.jar" prefix="WEB-INF/lib"/>

    </war>

  </target>

</project>

S1.8. Use ant by setting the JAVA_HOME, ANT_HOME and PATH in Machine 1 to build the wsa.war

or use the  wsa_ant within the AppSrvr/bin folder of WebSphere Install

S1.9. Deploy the war file to WAS using the admin console as a new application using automatically generate bindings, mapping app to server1 and changing app name to wsa.

S1.10. Start the wsa application

S1.11. Check whether the web services adapter is reached by the Admin Server on the remote machine 2.

$DLC/bin/./wsaman -host 172.16.99.7 -i wsa1 -q

Not connected

But wsa app on WAS is up and running with no errors

Scenario 2

OpenEdge 10.2B as well as WebSphere Application Server ND V7.0.0 on the same machine... CentOS 32 bit machine

Only changes to Scenario one is the ubroker.properties file remains in a single location with the installed directory pointing to the local install directory. Also there is no need to tar the java folders as such.

WAS ND topology consists of a federated app server,  HTTP Server and a deployment Manager

$DLC/bin/./wsaman -host 172.16.99.7 -i wsa1 -q

Not connected

But wsa app on WAS is up and running with no errors