Skip to Content

Changing a LoginModule

Hi All,

Let me start by saying my knowledge of NWDI is limited, but I have a scenario that I will appreciate if you can help me with.

I have a custom build in-house SSO solution in place, we are testing Biller Direct and one of the issues is that we want to intergrate BD to use the in-house SSO solution. For that we need to develop a new LoginModule.

I understand that the right tool to use in NWDI/NWDS (please correct me if I'm wrong). As this is a test scenario I will like to know if we can use our current sandbox J2EE engine 7.02 and add the DI usage type to it, or do we need a clean install?...  I can see that the packages are part of the NWCE  now, I haven't been able to find the SCA's on their own to implement them via JSPM/SDM. Is this the right approach?

Regards, Juan

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

3 Answers

  • Best Answer
    Feb 18, 2013 at 12:32 PM

    You need NWDI when you have to customize a WDJ app. In all other cases, the usage of NWDI is defined by a corporate guideline (here we have the loophole), and specially when it comes to "pure" Java development, NWDI is not needed and normally only adds headaches.

    You should use NWDS as it comes with the necessary wizards and templates, but NWDI for developing a logon module in sandbox is way too much. It may proof useful when it comes to later usages in teams and WDJ development, but even when you'll have later to transport the logon module: this is something done manually.

    Developing a new Logon Module is Java development. Look at the example here: http://help.sap.com/saphelp_nw70/helpdata/en/3f/1be040e136742ae10000000a155106/frameset.htm

    Add comment
    10|10000 characters needed characters exceeded

    • Hi Tobias/Ervin

      Thanks for the info!..  I wanted to avoid using NWDI if possible as we are using standard SAP software and theres no need in the immediate future to develop any Java code. What I undestood is that i can use standalone NWDS to create a new login module to adapt it to our bespoke SSO.

      Regards, Juan

  • Feb 18, 2013 at 12:03 PM

    HI,

    normally NWDI should be able to serve any kind of developments, independently of its release. Meaning that if your current 702 system is not too overloaded (sorry, I have few knowledge on BD) then it should do the trick if you add DI usage type to your existing 702 system.

    The SCAs to be used are:

    DI_CMS, DI_CBS and DI_DTR

    Then of course you have to configure NWDI once these SCs are deployed.

    For "installation / upgrade / usage types" I recommend to post a question in the corresponding forum, as there might be issues from the usage types point of view we are not aware of here in this NWDI forum.

    I hope this helps.

    Best Regards

    Ervin

    Add comment
    10|10000 characters needed characters exceeded

  • Feb 18, 2013 at 10:43 AM

    Anyone?

    Add comment
    10|10000 characters needed characters exceeded