You are on page 1of 8

Anonymous Invocation of BSSV Deployed to Weblogic Running on Windows

This document describes how to remove security policy attached to a web service (JAX-RPC and JAX-WS) deployed
to Weblogic 10.3.5 running on Windows. If the Weblogic is running on Linux then you dont need to follow this
document. (In case of JAX-RPC web service a patch (Bug # 12761125) from Weblogic needs to be installed before
performing the following steps. The patch needs to be installed for Weblogic running on both Linux and Windows.)

1. Log into Weblogic admin console. Expand Environment from the left side of the admin console and click
on the Server option. From the list of servers click the one where the BSSV package is deployed. In my
case it is WSWLS035. The server need not be running at this point of time .

2. In the next screen go to Server Start under the tab Configuration.


Anonymous Invocation of BSSV Deployed to Weblogic Running on Windows

3. Now in the Change Center from the top left corner click on Lock & Edit. Copy the entire entry from
Class Path and paste it on notepad and save it.

4. Then from Weblogic admin console delete the Class Path entry and hit Save.
Anonymous Invocation of BSSV Deployed to Weblogic Running on Windows

5. In the next screen click Activate Changes from Change Center.

6. Now if the managed server (WSWLS035 in my case) is in stopped state then start it or if the server is in
running state then stop it and start it. Before proceeding with the next steps make sure that the server is
running.
Anonymous Invocation of BSSV Deployed to Weblogic Running on Windows

7. Click on the server and go to Deployment tab. Make sure that the deployment is active. Click on the
deployment.

8. In the next screen you will see list of services that are part of the deployment. Click on the service from
which you want to remove the security policy. I have selected the AddressBookManagerService.
Anonymous Invocation of BSSV Deployed to Weblogic Running on Windows

9. In the next screen go to Configuration->WS-Policy tab. You will see the service endpoint and the policy
attached to it. Click on the service endpoint (AddressBookManagerPort).

10. In the Change Center click on Lock & Edit. Select the security policy from Chosen Endpoint Policies
use the arrow button to move it to the left side, Available Endpoint Policies and click OK.
Anonymous Invocation of BSSV Deployed to Weblogic Running on Windows

11. Now you will be asked for saving the deployment plan. Click OK on this screen.

12. In the next screen click Activate Changes. This may take 2mintues or more.

Now the web service from which we have removed the policy can be invoked without passing username and
password (Anonymous Access) in the SOAP header. But the remaining web services with security policy to work we
need to add the entry back to Server Start->Classpath that we took a backup and removed in step 3 and restart
the managed server. The following steps will describe the same.
Anonymous Invocation of BSSV Deployed to Weblogic Running on Windows

13. Go to managed servers Server Start->Classpath as described in step 1 and 2. In Change Center hit
Lock & Edit. Copy the Class Path entry that we saved in step 3 and paste back to Class Path on
Weblogic Admin Console. And hit Save.

14. In the next screen Activate Changes from Change Center.

Restart the server. Now both the web services with security policy attached and without security policy will work.

To attach a policy back to web service you have to follow the same procedure except in step 10 you have to add a
policy to the web service endpoint instead of removing.
Anonymous Invocation of BSSV Deployed to Weblogic Running on Windows

How to Test it:

1. Use solution ID: E1: BSSV: How To Test a Business Service deployed to a WebLogic Business
Services Server using SOAPUI (Doc ID 1122313.1) for your reference.

2. Get your WSDL URL

a. Admin Console::Environment::Servers::YOURBSSVINSTANCE::Deployments Tab

b. Expand the plus sign for your server name

c. Click on the Web Service that you just configured (e.g. AddmressbookManager)

d. Click on the Testing Tab

e. Expand the plus sign under Name column

f. Click on the ?WSDL Link. This will open the WSLD without changing the port
number or https:// in the URL.

g. Use this WSDL in your soapUI test.

3. You do not need to pass the Security info in Soap Header. You can pass <soapenv:Header/>

You might also like