cancel
Showing results for 
Search instead for 
Did you mean: 

Agentry client branded url/connection cached on iOS?

Former Member
0 Kudos

Hi All,

We're in the middle of an upgrade project to move from Agentry 6.0.x to SMP3 with our 10 Work Manager for Maximo 7.5.2 apps and we're experiencing an intermittent issue where the branded iOS clients that we've created seem to be able to use the same url.

So the scenario is:

  • user opens App1, logs in and transmits successfully.
  • The same user then opens App2, logs in and the transmit fails with an Error 13.

In the logs we can see that for both transmits the login queries for App1 are running (there are security group restrictions for each app in the queries). The problem only happens rarely and closing all Agentry apps through iOS multitasking seems to resolve it.

Has anyone seen this before?

Client version is Agentry v7.11.0.68

Server version is SMP 3.0 SP10 PL0

Thanks,

John

Accepted Solutions (0)

Answers (1)

Answers (1)

mark_pe
Active Contributor
0 Kudos

John,

Are the App1 and App2 really on the same URL (Are they connecting both to the same backend)?

For branding, you can have the means to edit and package the installation for your Agentry Client.

The most common scenario/technique are as follows:

1. Brand Client with Agentry (have details in it).

2. User Transmit to get data in it.

3. Continue with this branded client (with initial sync - normally this is to have the data in it).

- At this point there are details of the initial transmit in the branded client (Ex: Username/Password or let us assume your URL).

4. The popular technique here by SAP consultants is to go into the Agentry.db and use SQLLite to edit and remove the data you want to be removed and repackage it (branded). This needs to be unencrypted to work.


Reference  KBA # 2339702 - Incorrect logon displayed by Agentry branded client in poor signal condition

Proof of concept:

You said: "  intermittent issue where the branded iOS clients that we've created seem to be able to use the same url.

So the scenario is:

  • user opens App1, logs in and transmits successfully.
  • The same user then opens App2, logs in and the transmit fails with an Error 13.

"

From what we are saying above.

- You created your iOS Client branding with a URL in it

- Remove the URL after your initial sync (open the Agentry.db)

- Rebrand it again

You should not have issue with your second App2 having or using the other URL.

Some other people in this forum may have some other ideas.

Best Regards,

SAP Mobile Support Team