logon method configuration on Inventory Manager 4.0

[Former Member]

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???...

[mark_pe · Accepted solution]

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~~~~~~~~~~

[LOGON_METHOD]

;  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

LOGON_METHOD=USER_AUTH

[GLOBAL_LOGON]

;  referenced when LOGON_METHOD=USER_AUTH_GLOBAL

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

;    UID/password

UID=

UPASSWORD=

SHAREDCONNECTION=100

~~~~~~~~~~~end~~~~~~~~~~~~~~~~~~~~

[Former Member · Accepted solution]

Hi

In fact that is my Business use case: I have one user per store (manager) for several stores and one user for central warehouse. So I will have:

UserA -> Central Warehouse (10 pooled connections active)

UserB -> Store 1 (5 pooled connections active)

UserC -> Store 2 (5 pooled connections active)

and so on (we have more stores and warehouses but I just want to give the context of the Business Use Case)... But now I have one doubt: If I use USER_AUTH_Global as a logon method for IM 4.0, would the mobile app only use one user as a unique manager for all the connection pooled??? can only be fixed one user at the javaBE.ini under UID parameter?  I'm asking this because the when i see the [global_logon] section on javaBE.ini, I only see one UID and UPASSWORD parameter, like if the app only works with ONE user for the connection pooled... and We need to make connection pools with several users (at least one per store and/or warehouse)... I don't know if I'm still confused or I did not undestand at all...

BR,

MC

[mark_pe · Accepted solution]

I am assuming you will have one Agentry server for Central Warehouse (it will have its own JavaBE.ini), one server for Store1 (it has it's own JavaBE.ini) and once server for Store2 (has it's own JavaBE.ini)?  Each area (Central Warehouse, Store1 and Store2) will have their own mobile devices right (each devices will not connect to the other stores)?  So if I have a mobile device in a store (ex: Target or Walmart) in my town, those devices will not be used in the Central warehouse, right? The manager is not roaming to the different stores (like a district manager and carrying the same device to all the stores and central warehouse)?

So you will have:

UserA -> Central Warehouse (10 pooled connection active) - up to 10 devices (has its own server + its own javaBE.ini + 1 global user = warehouse)

UserB -> Store 1 (5 pooled connections active) - up to 5 devices (has its own server + its own javaBE.ini + 1 global user = store1)

User C - Store  2 (5 pooled connection active) - up to 5 devices (has its own server + its own javaBE.ini + 1 global user = store2)

If you need to make each user to be unique then you need to authenticate base on user instead of global (in your test case it may only be that you have 2 mobile users as well as 2 SAP backend users - 1 for the manager and one for the user) but you may get already connected to the server if more than 1 of that user is already logged in.  Again this is a very special case and may require testing (I have not played with global setting in production nor I have data from production environment to compare).

This is how I am reading your statement above.

Again I have not played with User_auth_global but I guess if you have different servers and javaBE.ini then you will be okay.

This is how I am reading it.

Regards,

Mark

[Former Member · Accepted solution]

Hi

Regarding your question: "Each area (Central Warehouse, Store1 and Store2) will have their own mobile devices right (each devices will not connect to the other stores)?" the answer is yes: each store and/or warehouse will have their own mobile devices sets... eventually a device on a store could return to central warehouse but that situation is not that common... but now the scenario you have suggested will not work for me because, I have over 15 stores + 1 central warehouse + several alternative distribution center (acts like plants on SAP ERP)... I can't have 18+ servers.... In fact I have just one server for SMP 3.0 production environment (with a good sizing to support the operation)... That's led me to a situation where I won't have separated javaBE.ini, just one ... and as you answered previously and I understood: the  User_auth_global accepts one and only one user for pooled connections... So with this I won't be able to configure separate user to the áreas.... 

Any other suggestion???

BR,

MC

[mark_pe · Accepted solution]

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.

Mark