SMP 3.0 - Agentry - SSO

Hi All,
We are trying to implement SSO (using network/LDAP userID and Password) for Agentry Application in our SMP 3.0 Landscape.
We have configured JavaBE.ini to connect with the Enterprise Portal which connects with LDAP. I have also implemented SAP Note: 2043172.
The whole process seems to work when I enter the right network user ID and password.
But when I enter the right userID but wrong password, I get the below error:
User ID may not be empty. Please Re-enter.
Or
Could not login user XXXXXX - IO Exception SSO server response code of error: 401
I am not sure which scenario throws which error.
I just wanted to understand these errors more, so I can make my solution better. Like what does really mean - 'User ID may not be empty. Please Re-enter'
Second Question: In JavaBE.ini - the user under [SERVICE_LOGON] section - Does this user need to exist in LDAP and SAP System both? I think yes. Just confirming.
And I am not sure if I phrase this question the right way or not - Does Agentry Server holds the SSO Cookie for a user? Or does it request from EP every time the user tries to login?
Regards
Ankur Malhotra
Tags edited by: Michael Appleby

Ankur
Please can you say how you resolved the com.syclo.agentry.AgentryException: Could not login user XXXXXX - IO Exception SSO server response code of error: 401 I am experiencing the same error after following the SAP Work Manager Installation Guide to enable SSO with a portal to retrieve a logon ticket to allow connection to the ERP backend. startup.log for Agentry shows the above message. The "IO Exception" almost suggests a setting in javaBE.ini tells java to read from a file, but the file is empty or does not exist, but this is just a complete guess. Your experience would be much appreciated.
Thanks
James

Similar Messages

SMP 3.0: Agentry - Pending transaction

Hi Experts.
I am doing modifications of SAP Work Manager 6.1 in Agentry.
In the MainObject, the WorkOrder collection is located, which has a sub collection called Components.
In the Transmit action there is a subaction that will loop over the WorkOrder collection, furthermore for each
WorkOrder another subaction will loop over the Components collection.
For each Component satisfying some conditions an Edit transaction with an Update Step, will trigger a backend
call for that Component. This part works fine.
If I supply some invalid data for a Component and do a transmit, then the Update step will fail. If I do another transmit
without doing any changes, the Update Step will be executed again and fail. So far so good.
Now I delete the Component with invalid data, to try to get the Transmit working again. I do this via a Delete transaction
with the checkbox "Discard pending" set to true. I would expect this to also delete the pending transaction.
But even if I can verify, that the Component Object has been deleted in the Components collection, the pending transaction
will still be executed every time I do a transmit.
I cannot get the pending transaction deleted.
The only workaround is to delete the parent object, which is the entire Work Order Object. But this is much more than I want to delete
if only a single Component object is invalid.
I hope someone can help me with this.
Thanks.
Søren Hansen

Just to close the loop in this discussion. The result of the OSS ticket is the creation of this SAP note:
SAP Note # 2142877: SAP Work Manager - Transaction Failure Handling cannot be turned on in SMP 3.0 Agentry production publish (via Cockpit) but it can in SMP 3.0 development publish via Agentry.ini.
As stated the Agentry.ini is deprecated in SMP 3.0 for Production Publish.
SMP 3.0 - Agentry.ini (Configuration file) deprecated in SMP Production mode
The Development publish still uses Agentry.ini but in production publish the SMP Cockpit is used but the internal coding does not work with the Agentry.ini enabling of the error handling. So any application that was designed in Agentry 6.0.X before that uses error handling needs to follow the same way the SAP note # 2142877 was done above.
Just adding some references in SCN for quick check by users.
Soren also has a write up in the SMP develoment center listed below as the result of this action:
SMP 3.0: Agentry Transaction Failure Handling
I just want to add some closure on the discussion on what happened - just in case some other users bump into this discussion online.
Best Regards,
Mark Pe
SAP Senior Support Engineer

SMP 2.3 Agentry update versions problem

Hi,
please I experienced issue when deploying new version of Agentry application to SMP 2.3. On devices we have stable old version. When we deploy new version through SCC on SMP and then we try to transmit device , it freezes on "Sending client info" . But in SCC it is running normally (e.g. when we reinstall client on device or reset ATE, it downloads new version with no problems).
Our steps are::
Deploy version 1
Make initial sync.
Deploy version 2
Make delta sync.
Expected result: new ersion is downloaded with delta sync correctly (currently we get freeze on “sending client info”).
Thank you for any help
Martin

Hi Steve,
we use Agentry_6.0.30 and I am talking about Application Logic release.
Thank you

SMP 3.0: Agentry use of source=INI in JavaBE.ini

Hi Experts.
Is it still possible to use the JavaBE.ini for parameter configuration in Agentry 7.0 (on SMP 3.0) ?
We will for sure use source=SAP for productions servers, but for local development environments
it would be more flexible to use local configuration.
Does anybody know if an export program exist, to export parameters from SAP to an INI file ?
Thanks.
Søren Hansen

Hi Bill.
Seems like it is working. I have posted some details in SMP 3.0: Setup local Agentry development environment with source=INI in JavaBE.ini
I have not been able to find a standard program to export the parameter values, but found it fairly simple to create one myself.
I will update above document with any findings, but I was able to start up the server, and do a full initial synch via that procedure.
Søren Hansen

SMP 3.0 Agentry Client Communication Error

Hi,
We have installed SMP 3.0 server and SAP WM 6.1 in cloud server. The server certificate is generated with FQDN. Within the cloud server we are able to access the WM 6.1 app in ATE by using https://FQDN:8081/SAPWM
For accessing the app from internet we have public DNS which maps to the host. The url: https://publicdns:8081/SAPWM" is accessible in the browser we get the " I am here" message. We have put the certificate in Trusted root.
But in the Agentry client when provide the server "url: https://publicdns:8081/SAPWM" we are getting communication error.
Error Log
Requesting Public Key from Server
Connect to server 'ABCD', certificate is for 'xyz.com', so it is not valid
Communications error (14)
Connection failed
Ending transmission
From the error message we understand that the URL host and the certificate host are not matching so this is causing the error.
Please let us know how we can resolve this issue.
Appreciate your help.
Regards
Zak
Tags edited by: Michael Appleby

Zak,
You will need to regenerate the certificate for the SMP 3.0 server in the cloud to use the public dns name instead of the FQDN.
Instructions for this can be found in the following document.
http://scn.sap.com/docs/DOC-55932
Good luck!
--Bill

SMP 3.0 Agentry: Where to put data table files?

Hi,
we are using several file system data tables in our application which load their data from a file named "datatables.txt".
In SMP 2.3 this file was placed inside the "tables" directory of the Agentry server. In SMP 3.0 we tried the com.sap.mobile.platform.server.agentry.application directory without success. What ist the right place for that file now?
Thanks
Christoph

Christoph,
Yes, I would recommend logging a support ticket related to this so it can be reviewed and hopefully migrated to the new application specific directory.
--Bill

SMP Cloud and Agentry

Hi experts,
I have an SMP cloud trial account and I was wondering if I can upload/publish an Agenrty project to this account? When creating a new app in the Applications Management Cockpit, there is no option for Agentry type of application.
Regards,
Denis

SMP cloud doesn't currently have Agentry Support.

SAP Moble Platform 3.0 with Agentry 7.0 application configuration

Hi,
we try to migrate from SMP 2.3 to SMP 3.0.
We installed the MobilePlatform3 as development server and the SDK 3.0 SP04 PL01.
After that we import the 2.3 project in the new eclips with the agentry editor plugin for 7.0.3. We checked if all transmit configurations are set to WebSockets over HTTPS as connect type.
After that we create a application for Agnetry Apps in the management cockpit and found the agentry.ini in this directory: "SMPHome Directory/\Server\configuration\com.sap.mobile.platform.server.agentry.application. We publish the agentry app to this agentry.ini and see the BACK END configuration in the management cockpit. As authentication we use "no authentication challenge".
Afte restart the SMP server we see in the logs no errors. In the agentry server log we see that the application was loaded. We test the agentry server in the browser with this adress https://{servername}:8081/{sub-url} prüfen and get the "I am here!" message
Now we try to connect from the ATE (version 7.0.3.605)(installed on the same server like the smp) to the agentry server with this adress:"{servername}:8081" and get this error:
Unexpected disconnection from server (11)
Connection failed
Ending transmission
if we try only the server without the port we get this message:
Requesting Public Key from Server
The printer queue is full.
Communications error (14)
Connection failed
Ending transmission
We check the smp3 server logs and the agentyr logs but nothing is in. We set the log level to debug but nothing.
We dont know where we could search for the error. What can we do or where is the error in our configuration.
Thanks,
André
Message was edited by: Michael Appleby

Hi Stephen i do not know how to upload a file to the forum so here is the the startup.log file:
17:55:56 09/03/2014: Starting Agentry (64-bit Windows)
17:55:57 09/03/2014: Reading system ini file.
17:55:57 09/03/2014: Starting log file.
17:55:57 09/03/2014: Loading message groups.
17:55:57 09/03/2014: Starting threads.
17:55:57 09/03/2014:    1 initial threads. Threads will auto-scale.
17:55:57 09/03/2014: Event: 0, 2, Loading the Agentry Runtime's public/private key for password exchanges.
17:55:57 09/03/2014: Event: 0, 2, Key pair loaded successfully.
17:55:57 09/03/2014: Starting Agentry: Agentry Server Agent v7.0.3.159
17:55:57 09/03/2014: Event: 0, 2, Agentry Startup
17:55:57 09/03/2014: Loading 0 front ends
17:55:57 09/03/2014: Loading front end from angelvine
17:55:57 09/03/2014: WebSockets Front End: loading configuration
17:55:57 09/03/2014: Event: 17, 14, WebSockets Front End v7.0.3.159
17:55:57 09/03/2014: Starting Agentry Server Agent
17:55:57 09/03/2014: Agentry Server Agent: Starting threads.
17:55:57 09/03/2014:    1 initial threads. Threads will auto-scale.
17:55:57 09/03/2014: Agentry Server Agent: Adding messages.
17:55:57 09/03/2014: Event: 1, 4, Agentry Server Agent v7.0.3.159
17:55:57 09/03/2014: Loading agent from ag3.dll
17:55:57 09/03/2014: Starting Server
17:55:57 09/03/2014: Server: reading config file
17:55:58 09/03/2014: Event: 20, 150, Loading Development application definitions
17:56:01 09/03/2014: Initializing SQL-MietraSQLConnection from ag3sqlbe.dll
17:56:01 09/03/2014: MietraSQLConnection Back End: reading config information.
17:56:01 09/03/2014: MietraSQLConnection: name set to 'SQL-MietraSQLConnection'.
17:56:01 09/03/2014: SQL-MietraSQLConnection Back End: reading query config information.
17:56:01 09/03/2014: SQL-MietraSQLConnection Back End: initialized
17:56:01 09/03/2014: Event: 21, 4, Loaded SQL-MietraSQLConnection (SQL v7.0.3.159) from ag3sqlbe.dll
17:56:01 09/03/2014: SQL-MietraSQLConnection Back End: connecting 'dba' to database 'CDB_SDRSUP2'
17:56:01 09/03/2014: Event: 21, 101, dB Connect
17:56:01 09/03/2014: SQL-MietraSQLConnection Back End: started
17:56:01 09/03/2014: Event: 20, 152, Loading Development application definitions for default localization
17:56:01 09/03/2014: Event: 20, 153, Finished loading Development application definitions for default localization
17:56:01 09/03/2014: Event: 20, 151, Finished loading Development application definitions
17:56:01 09/03/2014: Server: Starting threads.
17:56:01 09/03/2014:    1 initial threads. Threads will auto-scale.
17:56:01 09/03/2014: Event: 20, 4, Server v7.0.3.159
17:56:01 09/03/2014: Starting front ends
17:56:01 09/03/2014: WebSockets Front End: Opening WebSockets servlet for sub-URL /Mietra
17:56:01 09/03/2014: Event: 17, 10, WebSockets Front End v7.0.3.159
17:56:01 09/03/2014: Event: 0, 0, Old log files moved into C:\SMP\MobilePlatform3\Server\log\agentry\rolled\2014-09-03-175556
17:56:01 09/03/2014: Event: 0, 23, Agentry startup is complete.

What is executable (or Runnable) file in Agentry Application?

I have built an application using Agentry, the application is completed now I want to publish this application, and want to deploy it on mobile device, but I don't have any idea how to do it, because it generated .apg file, but Android supports .apk and windows supports .xap, and iPhone supports .cod, now how to use .apg file, I am also unable to check it on Agentry Test Environment, because it is not Responding, it always hang when i open it. need some help ... Thank you.

SMP 3.0 SDK requires the SMP 3.0 Server. You cannot use older Agentry servers with the SMP 3.0 SDK.
The SMP 3.0 Server is currently in Ramp up and only avaliable if you are part of the Ramp Up program. If you are part of the ramp up program you can download and install the SMP 3.0 server.
Otherwise, I would recommend you use either the Agentry 6.0.x server and tools or the SMP 2.3 Server / SDK. You should be able to export your application from the SMP 3.0 Agentry Editor and then import back into the Agentry Editor version that matches the Server you will be using.
--Bill

Agentry 6.0.32 client: does it work on Windows 64-bit?

Hi Folks - We use Work Manager 5.3 with Agentry 6.0.32 server and client. We generally use Panasonic Toughbook mobile devices that are 32-bit Windows 7. But recently a couple of 64-bit PCs have been added.
Does anyone know if the 6.0.32 Agentry win32 client works on Windows 64-bit? If so are any additional steps needed to make it work?
We have been using the client install found in this zipfile from SAP SMP: 51046915_1.zip
Best Regards - Jeff

Jeff,
The Agentry 6.0.x clients run just fine on Windows 64-bit. I am running Windows 7 Enterprise 64-bit and have used all the Windows clients (Agentry 6.0.x, SMP 2.3/Agentry 6.1 win32 and WPF and SMP 3.0 Win32 and WPF clients) on my laptop without any issues.
No additional steps are needed to get this to work.
--Bill

Agentry client default server list

Hi Experts,
How to maintain a list of default servers on the Windows Agentry client and ATE for SMP 3.0 Agentry application?
We need to key-in server details every time we reset the client and connect to other servers.
Thanks!
Tags edited by: Michael Appleby

This was a list of server that the Agentry Server broadcasted to the Subnet. But with SMP 3.0 This is no longer valid screen as it wouldn't transmit the FQDN or the SubURL.
I would recommend building a client with the server information already and then give this client to your users.
Stephen

Integration SMP 3.0 and Inventory Manager 3.2 / 4.0

Hello,
I have a Little doubt. For an Implementation of Inventory Manager after I have installed/configured the SMP 3.0 or SMP 2.3, in order to actívate the Agentry for Inventory Manager, Do I have to install the Inventory manager server (Agentry Server) which I had downloaded with Inventory Manager Package from services marketplace? or Do I have to install Agentry server which came with SMP, and after that just configure the deployment package as application within the SMP? ... I'm a Little bit confused because I think these deployment files (bundle) are on the agentry server that came with the Inventory Manager package (that is why the question was raised) and if I do not install the Inventory Manager Server I wont be able to get this bundle. Another questions is: In case the inventory manager server must be installed in order to make the agentry / SMP integration work for this standard app, If after this implementation We want to develop /configure another agentry apps, Can I do this with the agentry server installed for Inventory Manager (Inventory Manager Server) and not the "generic" one that came with the SMP?
Please Help Manju Venkatesha Michael Appleby Steve Streeter Jason Latko
Best Regards,
Mariana

Hi Manju Venkatesha & Stephen Streeter
Let me see if I understood what you guys answered me on this post...
1.- The agentry server is built on SMP 3.0 & SMP 2.3 and the standalone server on SMP 2.3 is only configure for development. Now, I have a another question about this...
Q.- if I need to configure the agentry's development environment besides Inventory Manager Mobile App, Does the SMP 2.3 developer server need two agentry server (The one built within SMP and the standalone for development process)? or just standalone server? or just SMP Server with Agentry generic server built within?. I understood production environment only will have one... the "generic" agentry server... as Steven said "SMP 2.3 needs to be use for QA and production", but i have this question regarding development server.
2.- Manju, We can install either IM 3.2 or IM 4.0, the thing is we are reviewing what versión is better to implement So I need to clarify my doubts for implementation process on both versions. The steps you mentioned put me in context and gives me some lights about the process, now, when you wrote: "Download Inventory Manager from service marketplace (it comes exe file)", is this the mobile server called "Inventory Manager 3.2.0 Sever" for IM 3.2 / "SAP Inventory Manager 4.0.1 Deployment" for IM 4.0?. The confusion raised here because the wizard for the mobile server that comes with mobile application implementation package, it is almost the same of Agentry standalone server, besides the SAP Backend information, it's pretty much the same wizard. In fact I think it will create a file system directory similar to standalone agentry server... So, my question about this is:
Q.- If the answer to my previous question: Does the SMP 2.3 developer server need two agentry server (The one built within SMP and the standalone for development process)? , is yes… and as you remark on your steps I need to install this mobile server (exe file), Is this mean that I need to install three agentry server on the development server (generic, standalone, mobile server)?, What happen with the file system directory for the agentry standalone dev server and inventory manager mobile server? Do they will merge in one??? And if I need to modify the inventory manager mobile app: which agentry server will be my development environment?
The SMP 3.0 which has the agentry component integrated and does not need a standalone one will need the "mobile server", does it? (exe file within SAP Inventory Manager 4.0.1 Deployment I guess or Inventory Manager 3.2.0 Server) and what about if I need to customize something on IM 4.0? The changes will be publish directly to the agentry component within SMP 3.0?
Another thing, is the Inventory manager server (mobile server) will give me the jar file from which I can get the IM agentry project for Inventory manager mobile app customization?
I know I can be confusing on my questions but please help me understand
Thank you both for the information / help you could give me ...
Best Regards,
Mariana

Upgrading SAP Work manager 5.3 to 6.1 on SMP 3.0

Hi Experts,
We have SMP 3.0 server,work manager 5.3.Now want to upgrade from 5.3 to 6.1 and deploy standard work manager 6.1 (without crew management,meter management,customer service,linear asset management components)on to SMP 3.0
Agentry Editor and SMP 3.0 server are in different systems
Please suggest prerequisite add-ons needed,development and customization guides(for work manager 6.1 on SMP 3.0)
Manju Venkatesha, Please suggest in this scenario.
Thanks
Siva chandu
Tags edited by: Michael Appleby

Deploying WM 6.1 on SMP 3.0 can be found in
http://scn.sap.com/community/mobile/blog/2014/08/30/quick-start-guide-sap-work-manager-6x-with-smp-agentry
Thanks
Manju

SAP WM 5.3 Support on SMP 3.0 SP03

Hi,
I have deployed SAP WM 5.3 on SMP 3.0 SP03 and restarted SMP server. Agentry application started successfully. But, when i connect through Agentry client , it is showing 'Invalid password'.
Can you please confirm SAP WM 5.3 is supported in SMP 3.0 SP03?
Regards,
Anselm

SAP will only support the Application on the patform it was release.
WM 5.3 is only supported on Agentry 6
WM 6.0 is only supported on SMP 2.3 (Agentry 6.1)
WM 6.1 is only supported on SMP 3 (Agentry 7.0)
While it not supported, If you find an issue, support can help if it falls under one of the two:
1. The issue can be seen when using the Application on the Release platfrom version (for 5.3 it would be Agentry 6.)
2. The issue can be seen on all applications running on that platform. (i.e if you have a different test application on SMP 3 that has the same issue).
Stephen

Agentry Server Log Settings Error

Hi,
I'm working on SMP 2.3 Agentry Server and want to change Agentry Server Log Settings. When I try to change "Server.Backend.Java-1" log settings, it gives error like this ;
I've tried to disconnect all users but it did not work.
Best Regards,
Serkan
Tags edited by: Michael Appleby

Serkan,
Another idea is to do it manually.
Steps:
1. Under your SMP 2.3 / Unwired Server / Repository / Application Directory or AgentryServer directory - find the AgentryLogging.ini and modify the levels 1 to 4 (4 being most detail) and Y for Yes - use a separate file.
2. Stop / Restart your SMP 2.3 server from your Desktop Icon.
The steps above is not normally recommended as it requires you to restart the SMP 2.3 server. If it is successful from the SCC then no restart is needed. If you are in debug or development mode, I guess it is okay to know what files control the logging and what to edit.
In production mode, you never really want to do it this way due to the restart.
Let me know if it works for you.
Regards,
Mark Pe
SAP Senior Support Engineer

SMP 3.0 - Agentry - SSO

Similar Messages

Maybe you are looking for