SMP3 Agentry Server SQLBEException - SAInvalidLogin

Hello Experts,
I am creating from scratch Agentry app.
Our Department have on-Premise SMP3 SP3 PL1 Server with running Agentry Server.
Steps done:
On the Server installed MS SQL 2012 Expressactivated "sa" user with default password
On the Server configured ODBC Connection via "Set up data sources (ODBC)"
used driver is "SQL Server Native Client 11.0"
name of the connection is "smp3sqlserver"
server is "(local)\sqlexpress"
verification is done by login ID and password. "sa" user is used.
the ODBC Data Source Connection is working and verified
using the SMP3 cockpit Agentry app was created
the App was named "com.sap.agentry.swatapp"
Security profile contain "No Authentication Challenge"
On the Server within SMP folders, the agenry application folder with the agentry.ini" file was created.
Network drive mapped - on server folder "..\Server\configuration\com.sap.mobile.platform.server.agenry.application"
on my machine the Agentry app was created using Eclipse
application is called: "com.sap.agentry.swatapp
System Connection - "smp3sqlserver" SQL System Connection
app compiles without errors.
deployed app via Eclipse to the mapped network drive
"https://<server>:8082/comsapagentryswatapp" gives "I am here!" message
The problem I am having is logged inside the Server startup.log
<---------------------------------------------------------------------------- startup.log ---------------------------------------------------------------->
12:50:19 06/19/2014: Starting Agentry (64-bit Windows)
12:50:19 06/19/2014: Reading system ini file.
12:50:19 06/19/2014: Starting log file.
12:50:19 06/19/2014: Loading message groups.
12:50:19 06/19/2014: Starting threads.
12:50:19 06/19/2014: 1 initial threads. Threads will auto-scale.
12:50:19 06/19/2014: Event: 0, 2, Loading the Agentry Runtime's public/private key for password exchanges.
12:50:19 06/19/2014: Event: 0, 2, Key pair loaded successfully.
12:50:19 06/19/2014: Starting Agentry: Agentry Server Agent v7.0.3.205
12:50:19 06/19/2014: Event: 0, 2, Agentry Startup
12:50:19 06/19/2014: Loading 0 front ends
12:50:19 06/19/2014: Loading front end from angelvine
12:50:19 06/19/2014: WebSockets Front End: loading configuration
12:50:19 06/19/2014: Event: 17, 14, WebSockets Front End v7.0.3.205
12:50:19 06/19/2014: Starting Agentry Server Agent
12:50:19 06/19/2014: Agentry Server Agent: Starting threads.
12:50:19 06/19/2014: 1 initial threads. Threads will auto-scale.
12:50:19 06/19/2014: Agentry Server Agent: Adding messages.
12:50:19 06/19/2014: Event: 1, 4, Agentry Server Agent v7.0.3.205
12:50:19 06/19/2014: Loading agent from ag3.dll
12:50:19 06/19/2014: Starting Server
12:50:19 06/19/2014: Server: reading config file
12:50:20 06/19/2014: Event: 20, 150, Loading Production application definitions using file "comsapagentryswatapp-v1-0-0-app"
12:50:20 06/19/2014: Event: 20, 152, Loading Production application definitions for default localization
12:50:20 06/19/2014: Initializing SQL-smp3sqlserver from ag3sqlbe.dll
12:50:20 06/19/2014: smp3sqlserver Back End: reading config information.
12:50:20 06/19/2014: smp3sqlserver: name set to 'SQL-smp3sqlserver'.
12:50:20 06/19/2014: SQL-smp3sqlserver Back End: reading query config information.
12:50:20 06/19/2014: SQL-smp3sqlserver Back End: initialized
12:50:20 06/19/2014: Event: 21, 4, Loaded SQL-smp3sqlserver (SQL v7.0.3.205) from ag3sqlbe.dll
12:50:20 06/19/2014: SQL-smp3sqlserver Back End: connecting 'sa' to database 'smp3sqlserver'
12:50:21 06/19/2014: Exception: 12:50:21 06/19/2014 : 16 (SQLBEException), SAInvalidLogin (3: SA_DBMS_API_Error, DB Code: 0, DB Text:IM002 [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified, ), sqlBE.cpp#1353:DbConnectionPoolMgr::create
12:50:21 06/19/2014: SQL-smp3sqlserver Back End: started
12:50:21 06/19/2014: Event: 20, 153, Finished loading Production application definitions for default localization
12:50:21 06/19/2014: Event: 20, 151, Finished loading Production application definitions using file "comsapagentryswatapp-v1-0-0-app"
12:50:21 06/19/2014: Server: Starting threads.
12:50:21 06/19/2014: 1 initial threads. Threads will auto-scale.
12:50:21 06/19/2014: Event: 20, 4, Server v7.0.3.205
12:50:21 06/19/2014: Starting front ends
12:50:21 06/19/2014: WebSockets Front End: Opening WebSockets servlet for sub-URL /comsapagentryswatapp
12:50:21 06/19/2014: Event: 17, 10, WebSockets Front End v7.0.3.205
12:50:21 06/19/2014: Event: 0, 0, Old log files moved into D:\SAP\MobilePlatform3\Server\log\agentry\rolled\2014-06-19-125019
12:50:21 06/19/2014: Event: 0, 23, Agentry startup is complete.
<---------------------------------------------------------------------------- startup.log ---------------------------------------------------------------->
Thanks & Regards
Peter Vargovcik
MIC Dublin Intern

Hi Jason, here is the screenshot:
The ODBC connection definition is made via 64bit ODBC Data Source Administrator
Thanks.
Peter

Similar Messages

Is there any way to restart Agentry Server without restarting SMP3.0 server?

Hello Experts,
Is there anyway to restart Agentry server, without restarting SMP server? I want to modify the setting of Agentry app and restart the Agentry to make change effective. Each time I restart Agentry, I have to restart the SMP3.0. It is very inconvenient.
Please assist me on this issue. Thank you very much.

That is something I believe they are working on for the next SP release (along with multiple Agentry apps on the same SMP 3 server). I don't know if there is an offical way to do this but will see if I can get any answer.
--Bill

Getting error in connecting ios simulator with SMP3.0 server

Hi,
We have configure ODATA service on SMP3.0 server document provided by SAP of "How to configure Application using Security Profile". We are using the SAP Netweaver Gateway DemoSystem for calling the ODATA services-HTTPS (got access of it using http://scn.sap.com/docs/DOC-31221).We also use Server Certificate to get successfully ping to backend steps performed to import the OData Service URL certificate into smp_keystore.(by using Getting Started with Kapsel - Part 1).
Now we are trying to build Native app on ios platform using pdf provided in IOS Development study material with the exercise material provided by SAP to call the app deployed on SMP3.0 server.But we are getting an
Error:- Could not connect to server(screenshot attached) client side
Error:-.
2014 02 27 23:42:07#0-800#WARN#com.sybase.security.http.HttpAuthenticationLoginModule##anonymous#http-bio-8080-exec-4###Anonymous authentication is not supported. |
2014 02 27 23:42:09#0-800#WARN#com.sybase.security.http.HttpAuthenticationLoginModule##anonymous#http-bio-8080-exec-4###Server responded with the status code "401"|
Can anyone please help me out in resolving this issue.
Thanks,
Anjali Agrawal

Hi Brenton,
As I have performed the steps for server certificate exchange with SAP Netweaver Gateway DemoSystem which provides me with Sample OData Service (HTTPS) it does not include any need to use"Allow Anonymous Connection" option even without using that I am able to successfully ping the backend server as shown below..
Know my requirement is to make Native app and get my ios device/simulator to connected to SMP server 3.0.
So I am referring the link Getting Started with Kapsel - Part 8 -- AuthProxy which specifies a need to generate client certificate(which will help in authentication betn the client and server when using HTTPS).
Here also have successfully exchange the client and server certificate but when theirs need to generate the .csr I am getting the following error:-
Error:-keytool error: java.lang.Exception: Alias <sapserverca> has no key
Have stuck here badly and not able to find out solution I think their might be some step missing in this document or some thing which we are not doing correctly.
Can u please help me
-With some material which involves steps to generate the CSR
-Some link which will help in configuring OData Service(HTTPS) in SMP3.0
Any of your guidance regarding this will be helpful to us.Will be waiting for your reply.
Thanks,
Anjali Agrawal

Syclo : Error in connecting Work Manager Client with Agentry Server

Hi,
Can somebody please shed some light on work manager client-server connections? I have downloaded the "SAP_WORK_MANAGER_BY_SYCLO_5.2" package from market place and set up the Work Manager server. It can successfully connect to the SAP back-end. Environment variables are correctly set too. However, I'm failing to connect to the Work Manager server from the Work Manager clients. I have tried from the Win32 & Android clients both.
For Win32 client, the error I'm getting is:
For Android, I can't even see the server instance, although it's running (it shows up while attempting to connect from Win32). Error:
When I attempt to connect from Work Manager client to the server, it asks for username/password and for Android client it asks for Agentry user id and password. Aren't these username/password of the server where my Work Manager (Agentry) server is installed?
Also, the "Agentry Development Server" which has been set to run as a service runs with Administrative privileges.
I followed this: http://wiki.scn.sap.com/wiki/display/SAPMOB/Agentry+error+Client+Receiving+RFC+ERROR+LOGON+FAILURE+incomplete+logon+Data+when+connecting+to+server
It didn't help. Please let me know where I'm going wrong?
Tags edited by: Michael Appleby

Hi Michael,
I can login to SAP backend using the credentials mentioned in JavaBE.ini file.
Please take a look at the JavaBE.ini:
[HOST]
server=<SAP server host name>
; mobile application name configured in sap like SMART_WORK_MANAGER_51, SMART_CUSTOMER_SERVICE_10, SMART_ISU_WORK_MANAGER_10...etc
APPNAME=SMART_WORK_MANAGER_52
[CONFIG]
; Used to get the SAP Configutaions from SAP if source=SAP or from JavaBE ini file
; SAP Configurations are [ENABLE_TABLE], [TABLE_CHECK], [TABLE_REFRESH], [BAPI_WRAPPER],
; [SAPOBJECT], [CT_SAPOBJECT], [CT_BAPI_WRAPPER], [CT_RETURN_TABLE], [CT_DELETE_TABLE].....etc
source=SAP
[TEST_LOGON]
UID=
UPASSWORD=
UGUID=
SERVERSERIALNUM=
; Service login user is used to get the SAP Configutaions from SAP if source=SAP
; Set ENABLED=true if source=SAP or ENABLED=false if source=INI
; If ENABLED=true, set the UID, UPASSWORD and SERVERSERIALNUM
; SERVERSERIALNUM is the Agentry server serial number
[SERVICE_LOGON]
ENABLED=true
UID=<SAP backend username>
UPASSWORD=<SAP backend password>
UPASSWORDENCODED=false
SERVERSERIALNUM=AVKNN@NILKGGBTLD
[PUSH_LOGON]
ENABLED=false
UID=
UPASSWORD=
UPASSWORDENCODED=false
SHAREDCONNECTION=10
[CLIENT_NUM]
CLIENT=720
;CLIENT=010
[SYSTEM_NUM]
;SYSNUM=33
SYSNUM=00
[LANGUAGE]
LANG=EN
[LOGGING]
;1=Fatal, 2=Error, 3=Warning, 4=Info, 5=debug, 6=trace
Level=4
[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
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
[GROUP_LOGON]
; referenced when LOGON_METHOD=USER_AUTH_GROUP
; individual user authentication using an SAP Message Server which distributes
; client connections among a "group" of SAP application servers based on load
; balancing criteria
; host name or IP address of SAP Message Server
MESSAGE_SERVER=
GROUP_NAME=
SYSTEM_ID=
CLIENT=
[REQUIRED_BAPI_WRAPPER]
com.syclo.sap.bapi.LoginCheckBAPI=/SYCLO/CORE_SUSR_LOGIN_CHECK
com.syclo.sap.bapi.RemoteUserCreateBAPI=/SYCLO/CORE_MDW_SESSION1_CRT
com.syclo.sap.bapi.RemoteParameterGetBAPI=/SYCLO/CORE_MDW_PARAMETER_GET
com.syclo.sap.bapi.SystemInfoBAPI=/SYCLO/CORE_SYSTINFO_GET
com.syclo.sap.bapi.ChangePasswordBAPI=/SYCLO/CORE_SUSR_CHANGE_PASSWD
com.syclo.sap.bapi.CTConfirmationBAPI=/SYCLO/CORE_OUTB_MSG_STAT_UPD
com.syclo.sap.bapi.DTBAPI=/SYCLO/CORE_DT_GET
com.syclo.sap.bapi.GetEmployeeDataBAPI=/SYCLO/HR_EMPLOYEE_DATA_GET
com.syclo.sap.bapi.GetUserDetailBAPI=/SYCLO/CORE_USER_GET_DETAIL
com.syclo.sap.bapi.GetUserProfileDataBAPI=/SYCLO/CORE_USER_PROFILE_GET
com.syclo.sap.bapi.PushStatusUpdateBAPI=/SYCLO/CORE_PUSH_STAT_UPD
com.syclo.sap.bapi.RemoteObjectCreateBAPI=/SYCLO/CORE_MDW_USR_OBJ_CRT
com.syclo.sap.bapi.RemoteObjectDeleteBAPI=/SYCLO/CORE_MDW_USR_OBJ_DEL
com.syclo.sap.bapi.RemoteObjectGetBAPI=/SYCLO/CORE_MDW_SESSION_GET
com.syclo.sap.bapi.RemoteObjectUpdateBAPI=/SYCLO/CORE_MDW_SESSION_UPD
com.syclo.sap.bapi.RemoteReferenceCreateBAPI=/SYCLO/CORE_MDW_USR_KEYMAP_CRT
com.syclo.sap.bapi.RemoteReferenceDeleteBAPI=/SYCLO/CORE_MDW_USR_KEYMAP_DEL
com.syclo.sap.bapi.RemoteReferenceGetBAPI=/SYCLO/CORE_MDW_SESSION_GET
com.syclo.sap.bapi.RemoteReferenceUpdateBAPI=/SYCLO/CORE_MDW_SESSION_UPD
com.syclo.sap.bapi.RemoteSessionDeleteBAPI=/SYCLO/CORE_MDW_SESSION1_DEL
com.syclo.sap.bapi.RemoteUserDeleteBAPI=/SYCLO/CORE_MDW_SESSION1_DEL
com.syclo.sap.bapi.RemoteUserUpdateBAPI=/SYCLO/CORE_MDW_SESSION_UPD
com.syclo.sap.bapi.TransactionCommitBAPI=WFD_TRANSACTION_COMMIT
com.syclo.sap.bapi.SignatureCaptureBAPI=/SYCLO/CS_DOBDSDOCUMENT_CRT
I haven't yet installed ATE and tested out any application. I just want my connections to be perfect, first.
I have a question. Are the credentials used to connect Work Manager client to the server, same as the SAP backend credentials or are they the credentials of the host on which the Work Manager server is installed?
I have tried logging in using the SAP credentials also. But that results in error too.
These credentials are valid for SAP backend and successfully logs onto it and also responds correctly to connectTest.bat. However, I think this error is logical because these are the credentials for SAP backend and not the server where Work Manager server is hosted.

How to publish definitions to agentry server from other system having Agentry editor?

Hi,
   I have agentry editor in one system and the agentry server in another system.
   Now I want to publish the definitions from the editor to the server. i.e, the server is maintained centrally in one host, editor definitions from different systems should published to the server hosted centrally.
   How can I achieve this? Please help me
Thanks in advance,
Swaroopa.

Hi Swaroopa,
          When the agentry server is running in one system and the editor in another system, both the systems should be connected in network and the Agentry Server folder should be shared to a group of users who want to access your server.
When the application developing in editor is completed,while publishing click browse button ,then network connections,and select the system in which the agentry server is running,then in server folder select agentry.ini file.
     Now your application is published to another system agentry server .Check the application in ATE.
Regards,
Sravanthi Polu

Agentry server date conversion

Hi Experts,
I have developed a sample customer application in agentry connecting to mssql back end.There are fields with data type 'date' in front end and data type 'date and time' in back end. In the process of updating orders from ate to back end "The conversion of a varchar data type to a datetime data type resulted in an out-of-range value" error has been encountered.Now i have changed 'date' data type to 'date and time' in front end,now the orders for customer has been updated.Previously the data has been updated with date property in front end,suddenly this issue has been encountered .Can any one please help to identify what may be the reason for this behavior.Agentry server version is 6.0.30.
Thanks & Regards,
Sravanthi Polu

Because you are using to different data types (Date and DateTime) you would need to do a convert from the data to the DataTime when you insert the row into the database. See more information on converting for MS SQL Server here: http://msdn.microsoft.com/en-us/library/ms187928.aspx
Stephen Streeter

Agentry Server: /SYCLO/CX_CORE_RFC_OO_DATA:An exception occurred

I get this error when starting the Agentry server I have set up accoding tp the PDF "How-to Build an Agentry Based Mobile App from Scratch Connecting to an SAP Back-end Part 1".
I have searched the forum and found several possible solutions:
- checking that all BC services are activated
- checking that the application name in javaBE.ini is the same as in the SAP config pannel
- having JDK 1.6 or 1.7 installed
- checking path environmental variable
I have done everything and can't find the problem. Every time I start the server I get the following entries in the SAP system log (transaction SM21):
Tags edited by: Michael Appleby

Most of /syclo/* tables gets populated when BC set is activated or when you add or edit entries in /syclo/config panel. Do you create Mobile application in /syclo/configpanel ?
Thanks
Manju.

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

SMP3 - Agentry - User Authentication

Hi all,
I created an Agentry Application using SMP 3.0 and Agentry 7.
SMP 3.0 is installed locally on my machine. The Agentry Application is connected to a local SQLServer that contain Northwind database.
For the test phase, I create a security profile for the application using an online LDAP Server (Online LDAP Test Server | Forum Systems)
The application is correctly deployed on the SMP 3.0 and now I'm trying to test it using ATE (Agentry Test Environment).
The application can download the certificate and it can connect to the SMP. Now I got a problem in the authentication phase.
I insert the correct username/password (tesla/password) as described in the online LDAP guide (I also tested it using an LDAP Client).
Attached you can see the LDAP security profile configuration.
In event.log I got this entries
05/23/2014 17:48:57, 0, 0, 12, Thr 11912, AG-3ea-3A424B5A-3C65-47F6-B1F2-174EDAABA049
05/23/2014 17:48:57, 0, 0, 6, Thr 11912, tesla: Invalid Password
In XXX-smp-server.log this one:
2014 05 23 17:48:57#+0200#WARN#com.sybase.security.core.CertificateValidationLoginModule##anonymous#http-bio-8081-exec-2###The certificate (chain) is not valid. |
I restarted the server after the configuration change.
Any ideas? How do I configure the application for the authentication?
Up to now I just need to test the application, so the configuration is a "nice to have" now.
I also tried with "No authentication Challange" configuration, but with no results.
Thanks
-- Marco

Marco,
In SMP3.0 Agentry is not yet fully tied into the SMP server for authentication and will handle the authentication itself. As such when you define your Agentry application you should select No Authentication Challenge in the Security profile.
For you application, you will then need to configure at least one Agentry backend connection to handle the authentication. Since you are using SQL as the backend, the default sql user check authentication accepts any user / pwd combination.
Depending on how you are intending to authenticate your users you can either modify the query to check against a table in the database or add an additional backend to handle the authentication using some other source.
For example you could setup a File backend and then use that to authenticate users against Active Directory or add a Java backend and write custom authentication code to validate against a generic LDAP source or some other mechanism.
--Bill

Agentry Server Communications error (14)

Hi All,
We are trying to use WPF client for testing the application,
but we were getting the below error message
To resolve that we used the local certificate generated by using steps mentioned in the below link
http://infocenter.sybase.com/help/topic/com.sybase.infocenter.dc01930.0233/doc/html/fre1383608304168.html
After installing new certificate we are getting below communication error in ATE and as well as in WPF client:
before installing local certificate Application was working fine in ATE
Message:
Requesting Public Key from Server
Communications error (14)
Connection failed
Ending transmission
Please guide me to resolve the issue
Regards,
Lekhak Patil

Hi Steve,
We got the same issue working with WPF client , Hence we upgraded the SMP server 2.3 from SP00 to SP03 .
At present the Server is SMP 2.3 SP03 but we have not installed any certificate.
Again when trying to connect to server we got the Communication error(14) error.
Do we need to install the certificate again ?
Please let us know the exact process of installing and working with WPF client with SMP 2.3 SP03
Thanks
Neha

SMP3 - Agentry - No Backend tab available

Hi,
I installed the new 3.0 SP03 PL01 (EBF 22961) as fresh installation. I tried to create a new Agentry application in the Management Cockpit, but the "Backend" tab is empty. See attached picture.
Any suggestion?

Have you published your agentry app? then only you can define back-end connections for a particular agentry based app.
I suggest you to check Defining Back-end Connections for Agentry
Rgrds,
JK

SMP3 - AppDevelopment (Agentry):

Hi, I have a question on SMP3 and AppDevelopment (Agentry):
In previous projects we have typically run Agentry Server processes on our development machines so that we can unit test the enhancements that we are making prior to publishing to a more public DEV server.
I'm guessing that this is a pretty standard practice.
My question is: Does this model of having Agentry developers run their own Agentry Servers still hold for SMP3.0 now that Agentry has been incorporated into the main SMP server process.
We are on Ramp-Up for SMP 3 and I'm just about to setup our dev environments. Your comments would be appreciated!
Anyone know of any good articles that cover this topic for SMP 3.0?
Regards
Marty

In terms of environments here is what we commonly see and use. This actually applies to any Agentry version but yes also applies to SMP 3.0 as well.
Typically each developer will install an SMP 3.0 server as a developer installation on their development machine for their individual configuration activities. This instance would be setup in Agentry Developer mode (equivalent to ServerDev in previous releases). This instance would be pointing to your developement backend environment and be used for initial unit testing of their changes.
If you have multiple developers the would either checkin code to the Agentry share or go through a merge process to create a master version (Agentry Production Publish) that would then be promoted forward to the next environment.
The next environment is sometimes an integration test instance running in Agentry Production mode (ServerProd) SMP 3.0 (probably still as a developer installation) where the application is deployed for initial testing still against the development backend environment.
If everything looks good on the integration test instance, next would be deploying to your QA/Acceptance instance pointing to your QA/Acceptance backend environment. This should mirror production in terms of load balancing / clustering / data volumes etc. As such for SMP 3.0 it should be configured for a Production installation. Here is where your test team would execute their acceptance test scripts to confirm everything is ready before moving to the final Production environment.
Hope this helps!
--Bill

SMP3 - AppDevelopment (Agentry):how to use GCM (Google cloud Messaging) for Agentry Application.

Hi, I have a question on SMP3 and AppDevelopment (Agentry): how to use GCM (Google cloud Messaging) for Agentry Application for PUSH notification

Pratik,
Let me walk you through the flow with the assumption that the user is on an Android device and "connected" to the Agentry server.
An emergency workorder is created in SAP and assigned to the technician.
The SAP backend system will notify the Agentry server via an XML message that there is a workorder to send.
Agentry will get the details and if the user is connected attempt to send the workorder to the device via the Push mechanism
If the push fails to reach the Agentry client, the Agentry server will send a GCM message to the user
When the user returns to the Agentry client, the normal push processing / fetch will occur to receive the workorder from the server assuming the push retrys are in effect.
So, essentially you should not have to do anything to get the GCM to work as a secondary notification mechanism.
If you are looking to do something else with GCM that would be outside of Agentry.
--Bill

Issue while deploying Agentry application on local SMP server

Hello Experts,
I have deployed a customized SAPWM application on the SMP 2.3 server.
I am referring to the tutorial maintained at the following URL :http://scn.sap.com/docs/DOC-43353
After deployment, the status of the application is shown as "running_without_metadata".
Few sections from my agentry.INI (present under application's root folder (C:\SAP\MobilePlatform\Servers\UnwiredServer\Repository\Agentry\default\com.sap.agentry.wm53) are as follows.
[HTTPXML-2]
authenticationCertificateStore=MY
authenticationCertificateStorePassword=
authenticationCertificateStorePasswordEncoded=False
autoDequote=True
baseURL=http://localhost:8282
basicAuthenticationPassword=
basicAuthenticationPasswordEncoded=False
basicAuthenticationUserID=
constantsFile=httpxml_sd.ini
enableAuthentication=False
enablePreviousUserAuthentication=False
httpConnectTimeout=60
httpReceiveTimeout=300
httpResolveTimeout=60
httpSendTimeout=300
listenOn=8282
name=HTTP-XML Back End
timeZoneName=
timeout=300
trustedCertificateStore=
useSSL=False
xmlAllowXSLTScript=True
xmlNamespaces=
xmlResolveExternals=True
xmlValidateOnParse=True
[Java-1]
classPath=./ini4j.jar;./sapjco.jar;./Agentry-v5.jar;./SAPWM-5.3.0.0.jar;./SAPCommon-122971.jar;WMDeloitte.jar;
constantsFile=
deleteSource=True
enableAuthentication=True
enablePreviousUserAuthentication=False
initialHeapSize=256
maxHeapSize=512
name=Java Back End
outputDirectory=.
performCompile=False
printBusinessLogicStackTrace=False
printStackTrace=False
reduceOSSignalUse=True
scriptsPath=
serverClass=com/syclo/sap/workmanager/Server
sourceDirectory=.
timeZoneName=
[File-1]
name=dos
enableAuthentication=false
enablePreviousUserAuthentication=false
allowPreviousUserLogin=false
userDomain=dev
tempPath=
[Configuration]
apnsCertificateDirectory=apnsCertificates
apnsCertificatePassword=Rzdrj~SwixoAqzmbVxgi
apnsCertificatePasswordEncoded=True
apnsEnabled=True
applicationGlobalsFile=Globals.ini
applicationStringsFile=ApplicationText.ini
clientStringNamesFile=ClientStringNames.ini
clientStringsFile=ClientText.ini
developmentServer=False
enableFailedTransactionLogging=True
enableOverrideFile=Enables.ini
enableTransactionFailureHandling=False
failedTransactionFilenameFormat=%{userid} %{transaction_name} %{date} %{time}-%{count}.xml
failedTransactionsQueue=FailedTransactionsQueue
gcmEnabled=True
gcmServerAuthorizationKey=Authorization:key=AIzaSyDi0qWQEewdbmNSV_o9QNtSQrlxPnBXtBM
gcmServerLink=https://android.googleapis.com/gcm/send
imagesPath=Application\Development\Images
localizationPath=
localizations=
overrideInfoTableDirectory=OverrideInfoTable
overrideTypesFile=OverrideTypes.ini
postedTransactionDirectory=posted
postedTransactionFile=%{device}.pli
scriptsPath=Application\Development\Scripts
spinDocIniFile=
threadCount=0
transmitConfigurationFile=TransmitConfigurations.ini
trustedCertificateStore=
updateIdleWait=60
updatePeriod=60
[Web Server Front End]
listenOn=80
permitGetCGI=true
xslDirectory=xsl
resourceDirectory=resource
authenticationCertificateStore=AgentryServer.pfx
authenticationCertificateStorePassword=Rzdrj~SwixoAqzmbVxgi
authenticationCertificateStorePasswordEncoded=true
When I connect this application from my iPad with my machine's IP and port as 7003, I get an error saying "Invalid password for User <username>".
When I debugged this application in the ECC, in the BAPI /SYCLO/CORE_SUSR_LOGIN_CHECK, I saw that the Password being sent to the ECC was blank, inspite of entering the password on the application. (have run it for another user in ECC in the below screenshot).
Is something missing in the agentry.INI or application configuration on the SCC which is causing this issue?
Any help will be appreciated.

If you are getting "running_without_metadata" this means the Agentry server did not load any application on start up.
1) In your Agentry.ini in the [Configuration] section what is developmentServer set to?
2) Depending on the value is where the Agentry Server looks for the application logic in the following locations:
Set to" True"
C:\SAP\MobilePlatform\Servers\UnwiredServer\Repository\Agentry\default\com.sap.agentry.wm53\Application\Development\
Set to false:
C:\SAP\MobilePlatform\Servers\UnwiredServer\Repository\Agentry\default\com.sap.agentry.wm53\Application\Production
In the above folder does it contain your application logic?
Stephen

How to create 2 Work Manager Apps on SMP Server (Agentry)

Hi All,
I encountered a problem with my SMP 2.3 SP3 in combination with Agentry 6.1.. and Work Manager 6.0.
I have an already working version of WorkManger on my SMP Server on port 7003, but whenever I create another WorkManager version on a different port e.g. 7005 the SMP/Agentry Server displays the status STARTING but never finishes this processs state.
The version of both Work Manager instances is the same, with the exception that the section [ANGEL Front End Ports] in the file Agentry.ini contains once the port 7003 and in the other file e.g. 7005.
Has anyone a encountered a similar problem or is able to create two different WorkManager versions on the same AgentryServer?
Regards,
Thomas

Hello Steve,
thanks for your quick reply, the listenOn Port is at both applications the same I will fix that in a few seconds.
the entry nonStandardJavaOptions is at both apps empty.
the startup.log of the second application:
14:16:58 03/19/2014: Starting server (64-bit Windows)
14:16:58 03/19/2014: Administration client command port is 55086, status port is 55087
14:16:58 03/19/2014: Looking for initial status connection...
14:17:04 03/19/2014: Event: 0, 30, Admin client 10.33.160.94:55094 authenticated successfully.
14:17:04 03/19/2014: Event: 0, 27, Admin client 10.33.160.94:55094 has connected
14:17:04 03/19/2014: Reading system ini file.
14:17:04 03/19/2014: ID: SAP Work Manager Server v6.0.0.0, Name: ???, Location: ???
14:17:04 03/19/2014: Starting log file.
14:17:04 03/19/2014: Loading message groups.
14:17:04 03/19/2014: Starting threads.
14:17:04 03/19/2014: 1 initial threads. Threads will auto-scale.
14:17:04 03/19/2014: Starting Server: Agentry v6.1.3.10212
14:17:04 03/19/2014: Event: 0, 2, System Startup
14:17:04 03/19/2014: Loading 1 front ends
14:17:04 03/19/2014: Loading front end from angelvine.dll
14:17:04 03/19/2014: ANGEL Front End: reading init files.
14:17:04 03/19/2014: Event: 17, 14, ANGEL Front End v6.1.3.10212
14:17:04 03/19/2014: Event: 0, 2, Loading the Agentry Server's public/private key for password exchanges.
14:17:04 03/19/2014: Event: 0, 2, Key pair loaded successfully.
14:17:04 03/19/2014: Starting Server Agent.
14:17:04 03/19/2014: Agentry: Starting threads.
14:17:04 03/19/2014: 1 initial threads. Threads will auto-scale.
14:17:04 03/19/2014: Agentry: Adding messages.
14:17:04 03/19/2014: Event: 1, 4, Agentry v6.1.3.10212
14:17:04 03/19/2014: Loading 1 agents
14:17:04 03/19/2014: Loading agent from ag3.dll
14:17:04 03/19/2014: Starting Server
14:17:04 03/19/2014: Server: reading ini file
14:17:04 03/19/2014: Initializing 2-HTTPXML from ag3httpxmlbe.dll
14:17:04 03/19/2014: SystemConnection-2: Reading configuration information.
14:17:04 03/19/2014: SystemConnection-2: Setting name to 'HTTP-XML Back End'.
14:17:04 03/19/2014: HTTP-XML Back End: Initialized.
14:17:04 03/19/2014: Event: 24, 4, Loaded HTTP-XML Back End (HTTPXML v6.1.3.10212) from ag3httpxmlbe.dll
14:17:05 03/19/2014: Initializing 1-Java from ag3javabe.dll
14:17:05 03/19/2014: SystemConnection-1: Reading configuration information.
14:17:05 03/19/2014: SystemConnection-1: Setting name to 'Java Back End'.
14:17:05 03/19/2014: Java Back End: Initialized.
14:17:05 03/19/2014: Java Back End: Java Virtual Machine loaded.
14:17:08 03/19/2014: Java Back End: Java Back End AJAPI version 5.0, release 6.1.3.10200
14:17:08 03/19/2014: Event: 23, 101, Java Back End: AJAPI JAR version 6.1.3.10200 does not match the version of the Agentry Server
14:17:08 03/19/2014: Java Back End: Initialized.
14:17:08 03/19/2014: Event: 23, 4, Loaded Java Back End (Java v6.1.3.10212 (JVM version 1.6.0_22, AJAPI version 5.0 build 6.1.3.10200)) from ag3javabe.dll
14:17:08 03/19/2014: Event: 20, 150, Loading Production application definitions using file "SAPWM-v1-0-0-app"
14:17:08 03/19/2014: Event: 20, 152, Loading Production application definitions for default localization

SMP3 Agentry Server SQLBEException - SAInvalidLogin

Similar Messages

Maybe you are looking for