Regarding multiple user functionality in SAP MI 2.5 SP14

[Former Member]

Hi,

We have a business need where in the mobile device needs to be used by different technicians at different shifts.

Does SAP MI support multiple user scenario on the mobile device for File I/O.

How does SAP MI maintain data for different users on the device using File I/O.

I assume that on every sync with backend, all the data on the device is erased and new data is loaded. Is my assumption correct.

Regards

Raja Sekhar

[Former Member]

Hi Raja,

Did you ever figure it out? We have the same scenario that 3 users will be using a pda and same application. If you have any tips, please let me know. Any advices would be highly appreciated.

Regards,

Dai

[Former Member]

Hi Raja

MAM3.0 ur looking for will support multiple users and

any enhancements u do in that will also be supported

bye

sid

[Former Member]

Hi,

Please let me know how to configure the location for storing the user's data. After xml file is generated from the syncbo definition, we create an application with that xml file.

How do we do the settings for data storage location multi user scenario.

Regards

Raja Sekhar

[Former Member]

hello raja,

the metadata is created in the shared location. while the

user's data are stored in the separataed location. there's

an API,

SyncBoDataFacade dataFacade = runtime.getSyncBoDataFacade(VisibilityType);

the VisibilityType serves as the flag or your user data

location. VisibilityType has only 2 values: USER_SHARED and SEPARATED.

however, this method is already deprecated and the default

getSyncBoDataFacade() method is recommended. this will return

you the data facade for the separated location. thus by

default, all user's data are separated.

for details, please see the MI javadocs at

https://media.sdn.sap.com/javadocs/NW04/SPS15/me/index.html

regards

jo

[Former Member]

Hello Jo,

What if i want to share data between different users?

And i dont want to use deprecated method?

Message was edited by: Abhijit Shingate

[Former Member]

Does anyone know to how to setup a second user to a same device?

Do I just create new user with existing application? Is just that simple? Please advice. Thanks.

Dai

[Former Member]

Hi Dai,

Yes. Just click on 'New user'. However, the user will not be able to access the application of the previous users. You will have to explicity assign them to him in the webconsole.

Regards,

Rahul

[Former Member]

Hi dai

Just Create a new user in the client and assign the application to the user he will get the new aplication .

Note:If the application is already assigned to that user in other client then no need to reassign . all the required data will be retained in the new client.

bye

sid

[Former Member]

hello raja,

a unique conversationId is generated from the deviceId, the

user and the application infos. thus every user using the

same application will have his/her <i>separate</i> data

location which is only available to that user. and every

application has as well a <i>shared</i> data location which

can be accessed by all users assigned with that application.

now, knowing the data location concepts, depending on your

application design, the data could either be saved in the

separate location or in the shared location. generally, meta

data is in the shared and the application data is in the separate

location. when each user's data are in the separate locations,

other users won't have access to other user's data.

thus, multiple user scenario is supported. but take note

that you should check on your application if it supports

multi-user scenario as described above.

regards

jo

[kishorg]

Hi Raja,

<<Does SAP MI support multiple user scenario on the mobile device for File I/O.>>

yes .

<<How does SAP MI maintain data for different users on the device using File I/O.

>>

All data for the mobile device will come under the directory <b><Drive>:\Program Files\SAP Mobile Infrastructure\data</b>

if u r using file system , then u can see different folders inside this after synchronization.

in the MI server , associated with one user and one application there will be mobile ids and Conversation ID.

in the data folder in client (if u r using file system) , for one application , there will be atleast

4 folders .

1)LastSuccessfulSync

2)MI<2853484152454429> - contains the MIAUTH details

3)one folder (conversation id) for storing the metadata informations.(same as that in

4) for storing the data associated with that application

(this will also with another conversation id)

with different users with same application , we will have different conversation IDs. so the data will be in diff folders).

<< assume that on every sync with backend, all the data on the device is erased and new data is loaded. Is my assumption correct. >>

this is not exactly wrong.

i think for all sync, data associated with the MIAUTH will pass all the time.(for authentication )

only the delta of the application data is passed for all other synchronizations... this will be there in the

Sync folders (out).

Regards

Kishor Gopinathan