Skip to Content
avatar image
Former Member

logon method configuration on Inventory Manager 4.0

Hi guys,

If I need to configure the inevntory manager 4.0 app logon_method as USER_AUTH_GLOBAL, the only thing I need to put on the javaBE.ini is the communication user (global) and password on the referenced section? ... and another question....if is a pool connection for log on to the application what user should I used to enter to the application itself and perform the transmit? I'm a little confused... I'm wondering if this log on method is like I have one user on the backend for connection purpose and several user on the mobile devices different from backen's user???...

@Bill Froelich Former Member @Mark Pe @Manju Venkatesha Former Member

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Best Answer
    Sep 10, 2014 at 02:08 PM

    As far as I know, this is what you call a service login hence the installer will ask you what is your "Service User" or something like that. Each user has their own login tied to their roles but the system login is for the server.

    I don't use the Global_Logon yet but hopefully the memo or text in the javaBE.ini helps out. I only use the USER_AUTH. You may ask other users if they used that as global. I am speculating it is what it state it is in the text below. This is a special use case where users only have 1 user name and password and only have X amount of allowed connection. So in theory you will have a store that does inventory and all of them uses one userID (ex: "Clerk"). The benefit to this is you only have one user id the trade off is you do not know who did what (ex: you have a store with 10 employees. You gave them one userID to do the physical counting. Each of your employee uses the same or different devices (up to X connection) and counts the inventory. If something goes wrong you would not know who counted what or received what). This has to be the accepted business work flow or use case. A good test case or use case for this is a demo environment or training environment (you only give one userID and password).

    ~~~~~~~~from javaBE.ini~~~~~~~~~~


    ;  USER_AUTH if standard UID/Password authentication is used

    USER_AUTH_GLOBAL if pooled connections using single UID/Password is used

    ;  USER_AUTH_GROUP if UID/Password authentication with SAP Message Server

    ;   (load balancing) is used

    ;  USER_AUTH_SSO if SSO2 ticket authentication with SAP Portal Server is used

    ;  USER_AUTH_CUSTOM for a custom login module setup



    ;  referenced when LOGON_METHOD=USER_AUTH_GLOBAL

    uses a pool of connections to the SAP backend all utilizing a single

    ;    UID/password





    Add comment
    10|10000 characters needed characters exceeded

    • Other SAP consultants, partners or customer do it this way.

      They will have a kiosk mode design (Depending on how the users answers the form - screen certain logic occurs). They will enable screens (enable rule) depending on how the kiosk design is made.

      So in theory, you could have a user auth (or global auth) mode with a super user (global user) with all access to all the screens. Depending on how the user answered the questions (or password) from the main screen (custom screen) or form on the screen, certain levels or screen turns on or off (Enable rule or execution rule). All of these screens are tied to either custom actions or transactions. So certain users can do certain actions/transaction and the super user or manager can do all of them. In the form, they may ask who the user is and add password (this password will get check if it matches the local table via rules) and stuff and it can be checked against a table. In the backend, when they transmit the transaction, those detail gets transmitted in the backend. This is fully custom.

      These type of customization are seen on our larger customers (big oil companies or power companies). They have the cool apps as they have paid for it.