Thursday, July 01, 2010

Authenticate Web Services deployed in standalone (separate) container from OWSM installed in SOA

We have seen earlier that we use interceptor if we have to authenticate our webservice which are deployed in the same contianer in which owsm is deployed.


Now we will how can we authenticate a web service which is deployed in other container through SOA OWSM .

AS we have seen agent

agent.componentType can be one of the following
# serveragent - manages webservice providers
# clientagent - manages webservice clients.
# OC4JServerInterceptor - Used an an interceptor for webservice providers on OC4J
# OC4JClientInterceptor - Used an an interceptor for webservice providers on OC4J

We have seen the use case of a intercetptor now we will see how to use serveragent


Now let suppose we have to authenticate a web-service deployed in weblogic container.

then take the EAR/WAR file deployed in the container which has the web service and place it in some folder.


Now Create the Server Agent using OWSM console in SOA installation and copy the agent id.

NOw go to the following location

SOA_HOME\owsm\bin

and open the agent.properties file

and there specify the compoent id over there


Also Modify the following properties in agent.properties along with component id:

agent.componentType=serveragent

webservice.application.input= Give the path where you have stored EAR/WAR file.

webservice.application.webapp.name=Provide the name of the EAR/WAR file.

webservice.application.contexturi=Give the Context root of your web application.


Check the size of the EAR/WAR file..


Now go to the command console and navigate till SOA_HOME\owsm\bin and issue a command wsmadmin installAgent.



Now if you will check the Size of the EAR/WAR file it will increase.

Now just deploy the EAR file in the SOA container and check whether the policies defined in Server Agent are executed or not from the OWSM console.

No comments: