Skip to Content
author's profile photo Former Member
Former Member

Can a Deployable Proxy be called from Login Module?

Is it possible to call a deployed proxy from a customized login module. We have created both but have been unable call it fromt the logon module. We have tried this code:

javax.naming.Context context = new javax.naming.InitialContext(); service = ( context.lookup("java:comp/env/A3ServiceProxy");

But receive the error:

NamingException: Object not found in lookup of A3ServiceProxy.

Any help would be much appreciated...

Add a comment
10|10000 characters needed characters exceeded

Related questions

1 Answer

  • author's profile photo Former Member
    Former Member
    Posted on Nov 08, 2005 at 04:02 PM

    Hi Tom,

    the naming convention for accessing deployable proxies is "/wsclients/proxies/<provider name>/<ApplicationName>/<ProxyName>"

    for details have a look at

    NameNotFoundException during JNDI lookup for Deployable WebService Proxy

    best regards,


    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Thanks to all for your help. We tried each of the suggestions without total success. I'm sure most of the problem has been rookie mistakes.

      Anyway here is how we solved this issue:

      1. Develop your Custom Login Module according to the help documents:

      2. Create a Standalone Proxy project not Deployable (We could never get the deployable to work in this scenario).

      2. Include the Standalone Proxy jar in the build path of the Login Module project.

      3. Open the server/provide.xml file of the Login Module Library:

      a. Go to the Jars tab and add the Standalone Proxy jar.

      b. Change to the References Tab, click Add, choose

      select library/interface/service, then check

      webservices and webservices_lib.

      4. Deploy the Login Module Library project.

      Note – Make sure to follow the directions in the help link shown above for all of the steps on the Login Module creation and deployment.

      A neat trick we discovered after deployment of the Login Module Library to avoid a restart of the J2EE server is this:

      1. Pull up the Visual Administrator.

      2. Under the Cluster Tab->Select your Server->Services->Security Provider

      3. Go To the Runtime Tab->Policy Configuration Tab->Under Components select the application (We are using the Ticket Login Module Stack).

      4. Then modify the Flag setting for your Login Module ( I would switch to Optional and then back to Requisite).

      5. Now retest and your login module change should be live.

      Hope this helps anyone coming behind. We found it difficult to find people who had specifically incorporated a web service into their login module on a SAP Portal.

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.