Syclo Work Manager 6.1 SSL Configurations

Hello Experts,
We have an "Communicaiton Error 14" on Device and ATE. I have worked on WM 5.2 and 6.0 and aware of the SSL configurations. I have Generated a Self Signed Certificate and a PFX file using OpenSSL. Now, with SMP 3.0 SP03 we are not able to find how to configure the Agentry.ini and where to copy the .sst file.
Can someone help us understand on how to make this work??? Is there a workaround for HTTP communication without SSL and any document on this which can help.
Is SSL/pfx mandatory to have in 6.1 while testing with ATE?
Regards,
Sarika

Hi Stephen,
Yes, I have to change the FDQN name to IP to work with Management console, only I will get logon screen. Similarly I have tried to do the same in ATE & WPF client.
in Management Console, while have FDQN in URL,
https://jilan.wirelessap:8083/Admin/
the error is below. But when I change to IP it works.
This page can't be displayed
Make sure the web address https://jilan.wirelessap:8083 is correct.
Look for the page with your search engine.
Refresh the page in a few minutes.
Make sure TLS and SSL protocols are enabled. Go to Tools > Internet Options > Advanced > Settings > Security
Similarly, in WPF/ATE, if FDQN is in URL, I get the Communication Error(14).
Requesting Public Key from Server
Communications error (14)
Connection failed
Ending transmission
Is any mapping needed in my laptop between FDQN to IP address?
Thanks,
Jilan

Similar Messages

Syclo Work Manager 6.1 Deployment Issues

Hi Experts,
I am trying to Setup Syclo WM 6.1 have issues issues during the setup. I was following the Installation guide from SAP, found a clean and a neat blog from http://scn.sap.com/docs/DOC-56329#comment-506689. I am stuck at an error during deployment of the zip file to SMP 3.0 server as follows:
Can anyone suggest what could be the reason for this?
Søren Hansen hope you can help us. I have other issue which is reported on Syclo Work Manager 6.1 + SAP Connection Issue
Regards,
Nagesh
Tags edited by: Michael Appleby

Your error states that something is null.
You may go inside the SAPCommon-133461.jar library under your Java folder -> com.syclo.sap.connectTest.class and decompile it using your favorite Java decompiler.
~~~~~from the code~~~~~~~
you will see something like:
_connection.openCustomConnection(clientNum, _userName, _password, "EN", host, sysNum, 1);
~~~~~end~~~~~~~~~~~~~~~
From the list above, it takes the data from your javaBE.ini for username, password, host and sysNum and hardcoding the "English - EN". Most likely the host might be the one at fault from your picture above. It does not know what your host name is under your JavaBE.ini. It is blank hence it does not know where to connect. May want to try making things Unencoded but you need to study the Java code by de-compiling it so you may know the rules.
Make sure you are also running the connectTest under the Configuration folder of your SMP 3.0. From your picture above: C:\SAP\WM610\..\configuration\com.sap.mobile.platform.server..\javaBE.ini <-- wondering if this is under your SMP 3.0 install configuration folder.
Hope this helps.
Regards,
Mark Pe
SAP Senior Support Engineer

Syclo Work Manager 6.1 + SAP Connection Issue

Hello,
I have been trying to setup Syclo Work Manger 6.1 and testing the connection between Work Manager and SAP ERP System.
I have updated the connectTest.bat with the ERP login details uder test_user, I get an "caught exception null" and the test is not successful.
I get the following error:
I have my SMP3 and WM installed in the following path:
Any suggestions to get this tested successfully.
Regards,
Nagesh

Your error states that something is null.
You may go inside the SAPCommon-133461.jar library under your Java folder -> com.syclo.sap.connectTest.class and decompile it using your favorite Java decompiler.
~~~~~from the code~~~~~~~
you will see something like:
_connection.openCustomConnection(clientNum, _userName, _password, "EN", host, sysNum, 1);
~~~~~end~~~~~~~~~~~~~~~
From the list above, it takes the data from your javaBE.ini for username, password, host and sysNum and hardcoding the "English - EN". Most likely the host might be the one at fault from your picture above. It does not know what your host name is under your JavaBE.ini. It is blank hence it does not know where to connect. May want to try making things Unencoded but you need to study the Java code by de-compiling it so you may know the rules.
Make sure you are also running the connectTest under the Configuration folder of your SMP 3.0. From your picture above: C:\SAP\WM610\..\configuration\com.sap.mobile.platform.server..\javaBE.ini <-- wondering if this is under your SMP 3.0 install configuration folder.
Hope this helps.
Regards,
Mark Pe
SAP Senior Support Engineer

SAP SYCLO Work Manager 6.1 Blueprint

Hi Friends,
I am new to syclo, going to implement syclo agentry wm 6.1 for our client in coming days.
can anybody give me the tips to create business blueprint template on sap syclo agentry work manager 6.1.
Tips on requirement gathering also appreciate.
Thanks
Rag
Tags edited by: Michael Appleby

Looks at some documents posted in http://scn.sap.com/docs/DOC-55878
and http://scn.sap.com/docs/DOC-54054 related to methodology and process for Agentry mobile application development .
Thanks
Manju

Syclo Work Manager 6.0

Good afternoon,
us are actually implementing WM 6 according to the guide, but when we want to upload a file that is not sent to ERP. We should check?. We already checked the values of BDS (Business Document Service) / GOS (Generic Object Services), DMS (Document Management System) according to the guide.
A part of this problem we observed an error("error code: -1 se ha producido un error de red. file:///data/data/com,syclo.sap.SAPWorkMgr.cliente.android/files/aplication%20Directory/img") in the client device when we want to see the file to be attached
Tags edited by: Michael Appleby

Features:
Tablet: Huawei MediaPad
Android Version: 4.0.3
What type of client are you using?: WorkManager 6.0 for tablet.
What is the Agentry version of the clients? Agentry 6.0 + SMP 2.3
What type of files are you trying to upload? jpg, doc, pdf.
Thanks

How to configure the work manager java code to eclipse?

Hello all,
               I am working with the syclo work manager app. I have successfully installed all components required.
               I imported the work manager mobile application and I want to import the standard work manager java code, what is the process to import java code into work space.
               Guide me with some screen shots.
               When I try to start the WM server it is giving me the following error:
How to resolve the error.
Please anyone provide me complete setup needed to run the work manager app smoothly.
Please guide me.
Thanks & Regards,
Swaroopa.

Swaroopa,
That error is telling you the SAP JCo library cannot find one of the needed DLLs on the system. The sapjco.jar loads two additional DLL files (sapjcorfc.dll and librfc32.dll). Both should be installed by default into your ServerDev directory (assuming you are running Agentry 6.0.x).
I would guess it is having trouble loading the librfc32.dll based on the message but confirm both are in the correct location.
--Bill

Custom Work Manager not shown in WL Server Admin Console

An application scoped custom work manager is to be configured, for which the files weblogic-application.xml, weblogic-ejb-jar.xml, weblogic.xml have been defined. After it is deployed on the server, custom work manager is not being shown in the list on console -> deployments -> application -> monitoring -> workload.
What could be the reason? Is there something which is missed out?

Hi Justin,
According to the error message and the issue can be caused by the edition of your SSRS is not support for the custom data provider. For example the express edition have limitation support on this:
Features Supported by the Editions of SQL Server 2012 .
If your edition is the supportted edition and the issue can be caused by the custom data provider do not necessarily support all the functionality supplied by Reporting Services data processing extensions. In addition, some OLE DB data providers and ODBC
drivers can be used to author and preview reports, but are not designed to support reports published on a report server. For example, the Microsoft OLE DB Provider for Jet is not supported on the report server. For more information, see
Data Processing Extensions and .NET Framework Data Providers (SSRS).
If you are running on a 32-bit platform, the data provider must be compiled for a 32-bit platform. If you are running on a 64-bit platform, the data provider must be compiled for the 64-bit platform. You cannot use a 32-bit data provider wrapped with 64-bit
interfaces on a 64 bit platform.
More details information:Data Sources Supported by Reporting Services (SSRS)
Similar thread for your reference：
ERROR: An attempt has been made to use a data extension 'SQL' that is not registered for
this report server.
Error when viewing SSRS report with SQL Azure as data source
If you still have any problem, please feel free to ask.
Regards
Vicky Liu
Vicky Liu
TechNet Community Support

SAP Work Manager customization - adding a new field to equipment details screen (Syclo Agentry)

Hi Experts,
I am trying to add a field (NAME1) on the Equipment details screen under work orders in work manager 5.3 application.
I have performed the following steps, but I am getting an error while connecting to the application.
1) Create extension for Equipment class to add a new field.
2) added the new field (Name1) as the property to the standard object Equipment.
3) Added the field on the screen.
4) Added the field (name1) to the complex table ctEquipment.
5) Added the JAR file to Agentry.ini file.
6) Changed the Class mapping for parameter "Equipment" under group "SAPOBJECT" to point it to the custom (Extended) class.
7) Changed the class mapping for complex table parameter "ctEquipment" under group "CT_SAPOBJECT" to point it to the custom class.
8) after publishing the changes and re-starting the server, I get following error.
the log file generated (message.log) also has the same description.
What am I missing here? Any help would be really appreciated.

Hi Emanuel,
Thanks for looking into this issue.
I have performed the following steps as suggested by you, still it doesn't seem to work and gives the same error.
Below are the changes done on the ECC Side.
1) Copied the standard equipment class /SYCLO_CL_PM_EQUIPMENT1_DO to custom class ZSYCLO_CL_PM_EQUIPMENT1_DO. Changes made in the GET Method to get custom equipment related data
2) Modified the standard equipment structure /SYCLO/PM_EQUI_STR by adding one custom field
3) Configured this custom class as the object handler in the equipment mobile data object
4) Configured this custom class as the object handler for the equipment complex table
5) We are still using the standard BAPI Wrapper itself for getting the equipment data and the added field is reflected in the BAPI Wrapper table parameter
Is there something we are missing?

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.

Work Manager 6.1.0.4 configuration

Hi all,
currently Im trying to create connection from a iphone (work manager app installed) to an SAP Backend. Everything is set up and running (agentry server). Everytime i want to reach the server i get the next error message:
(On my iPhone)
Requesting Public Key from Server
SSL Invalid Chain
Communications error (14)
Connection failed
Ending transmission
(On backend log)
error:2006F067:BIO routines:BIO_read:connect error, ..\Socket\openSSLsockets.cpp#893:OpenSSLstreamSocket::SSLStreamSocket::checkSSLerror
Please can someone help me with this?
Thank you!

The error you are seeing indicates that the certificate presented by the Agentry server to the client (iPhone) is not trusted or the name on the certificate does not match the server name entered on the Agentry Client.
If you generate your own certificate for the Agentry server you will need to install the root CA certificate used to sign it as a trusted authority on the iPhone. I usually just email the root certificate file to myself and open it from the mail app on the phone to install.
Secondly even if the root CA is trusted, the name you enter when connecting the first time must match the name on the certificate. For example if the certificate is generated for myserver.mydomain.com but when I enter the server infomration on the iPhone I only enter myserver as the name even though the netowrk will properly route the connection to the server using only the hostname I will still get an error since what I entered doesn't match what is on the certificate. I believe you will get a different error message but it is still a key thing to consider.
--Bill

Book For SAP SYCLO Agentry Work Manager 6.0

Hi Expert's,
Can any one suggest me the book for SAP SYCLO Agentry Work Manager 6.0 , Which covers End-To-End Implementation methodology?
Answer appreciates.
Thanks
Rag
Tags edited by: Michael Appleby

Moved to SAP for Mobile. Application related, not SMP.
Regards, Mike (Moderator)
SAP Customer Experience Group - CEG

Analyze link generated by Portal not working after SSL Configuration

Hi,
We've installed OracleAS Portal 10.1.4 and Oracle Discoverer Version 10.1.2.48.18 on the same machine. We recently configured SSL on OracleAS Portal for SSO server only. Discoverer was not SSO enabled.
Now after successful SSL configuration we are facing one problem. The Analyze link that is generated by Portal to analyze the worksheet in Single Worksheet Viewer is no longer working. when we click on the analyze link we get the "HTTP 500 Internal Server Error" and a message that Page cannot be displayed.
Please advise...

Hi Andrew
It sounds like you need to enable SSO for Discoverer too.
Best wishes
Michael

Filtering lists in Syclo Agentry SAP Work Manager application

Hello Experts,
I am trying to filter a displayed list at run time ( while running the application). the list fetches the data from an existing object.
I am trying to customize few things while displaying the filters on the list.
So far, I could only find a single property under Agentry application configuration to deal with filtering list values, as per the screenshot below.
Moreover, I could see that I can allow filtering the list based on a set of particular fields.
Here, I cannot determine if the Agentry Editor will allow me to customize the look and feel of the filters being displayed.
Is there any other way I can filter the lists and which provides me with the flexibility to customize the look and feel of the filters being displayed?
For example, i could add an image in the list and might want to filter the list based on a particular image. will this be possible and supported by SAP Work Manager 5.3 (Agentry 6.0) ?

Hi Arihant,
I tried this filter and sort list tile in ATE. Please refer my example regarding the filtering and sorting:
Step1: No Filter.
Here there is no filter, so ATE is not hvaing any filtering.
Step2: Add filtering property to the List Tile.
Filtering properties:
Test in ATE.
Click on that filter symbol, we will get the following.
Step3: Add Sorting to the List Tile.
Sort Properties are: Add the CompanyName as sort property
Check in ATE.
Apply sort by clicking the symbol
List rows are sorted based on company name as below:
I to checked in iphone but the sort property is not coming. I will check the gaps and update.
Thanks,
Swaroopa.

Work manager configuration

All,
I'm prototyping work manager configuration for our app under WLS 9.2.
I think I want 2 work managers: one for async batch-type operations and one for sync operations. The async work involves making parallel calls and not necessarily waiting for a response. The sync work involve parallel calls and waiting for a response (such as a web service request resulting in 2 parallel backend calls.) Mainly I don't want to allow the async operations to hog the resources and cause slow responses or timeouts for the users. At the same time, however, I don't want to articifically handicap the async processing during periods of low sync load. If I create 2 fairshare work managers with a 50% share each, during the night when users are not submitting sync requests, will the async batch work manager be allowed to scale up?
A long time ago I wrote a parallel processing facade that used a single JMS queue to achieve paralelism. I quickly learned the hard way that if you have parallel calls that call back into the framework (that is, thread A spawns thread B and C and waits for replies and thread B spawns thread D and E and waits for replies,) then you can wind up blocked forever because A can't complete without B, but B can't complete without D, but D can't run because A and B are hogging all the threads. Is this a risk with the WLS work manager? It seems that as long as I don't cap the thread count, then it might be sufficient to have just 1 big pool. My concern is what will happen when WLS decides not to spawn any more threads and instead just queues up incoming work?
thanks

First Part:
If you are setting the fairshare to 50 % then the server will split the requests equally between the sync and async apps during a period of sufficient demand, with a steady stream of requests for each module such that the number requests exceed the number of threads.In this case the thread pool is equally utilized by each app.
Now, during the night time the sync WM is not working and this will free the thread pool for the async WM alone. The async work manager will utilize the whole thread pool and hence will scale up.
Second part:
Correct me if I'm wrong, I don't think there is a point where WLS will decide not to spawn a new thread. Spawning threads is a continuous process until the server goes down. The self-tuning thread pool would also adjust its pool size automatically based on the throughput history that WLS gathers.
You will have to kill the stuck threads to free up the pool or setup a max thread constraint and allow only a limited number threads to execute requests. I think you would also need to setup a capacity constraint to reject all the requests that are queued up for work.

How to publish Work Manager 6.0 on SMP3.0 ?

Hi SCN Community,
I'm trying to get the Work Manager 6.0 running on SMP 3.0 (running on Linux). Currently the events.log within the Agentry folder states, that the Agentry Server was started. But If I look into the Threads*.log I see there might be a problem and I'm also not able to connect to the server.
Unfortunately I couldn't find any manual or post where someone described the steps to get a work manager running on SMP 3.0. The SMP 3.0 server manual as well as the SDK manual just describing in general how to publish an application to the SMP 3.0. But for Work Manager, there might be some special things to be done ...
Any help/hints are welcome!
Here what I did so far:
Install SMP 3.0 up to SP02 on Suse SLES 11
Install SAP JCo 2.1.11 (test successful: java -jar /DVD_HANA/jco/sapjco.jar -stdout )
Create a new application in SMP with type Agentry and select security profile default
Install SMP3.0 SDK SP02 (Agentry)
Setup Eclispe 4.2.2 with Agentry Plugin 7.0.2
Import a Work Manager 6.0 from Teamshare
Export Agentry Project as a production version and point to the Agentry.ini which is in folder /opt/SAP/MobilePlatform3/Server/configuration/com.sap.mobile.platform.server.agentry.application
Include all jar files to the ZIP file
Import the ZIP file within Agentry application in SMP 3.0
Create JavaBE.ini in folder /opt/SAP/MobilePlatform3/Server which is copied from WM6.0 server
Adjust Agentry.ini in folder /opt/SAP/MobilePlatform3/Server/configuration/com.sap.mobile.platform.server.agentry.application (see section config files)
Restart Server
Config files:
Agentry.ini
[Server Administration]
authenticationCertificateStore=AgentryServer.pfx
authenticationCertificateStorePassword=Rzdrj~SwixoAqzmbVxgi
authenticationCertificateStorePasswordEncoded=true
[System Connections]
2=ag3httpxmlbe.dll
1=ag3javabe.dll
[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
urlPath=
[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=
name=2
timeZoneName=
timeout=300
trustedCertificateStore=
useSSL=False
xmlNamespaces=
[Java-1]
classPath=./ini4j.jar;./Agentry-v5.jar;./Z_SAPWM-6.0.0.0.jar;./SAPWM-6.0.0.0.jar;./SAPCommon-130881.jar;
constantsFile=
deleteSource=True
enableAuthentication=True
enablePreviousUserAuthentication=True
name=Java-1
outputDirectory=.
performCompile=True
printBusinessLogicStackTrace=False
printStackTrace=False
scriptsPath=
serverClass=com.syclo.agentry.Server
sourceDirectory=.
timeZoneName=
[SpinDoc]
facePath=sql\custom;sql
facepath=sql\custom;sql
[TimeZoneAlias]
Log files:
events.log
02/27/2014 18:51:45, 0,         0,         0, Thr 140352349296384, New files opened events.log, messages.log
02/27/2014 18:51:45, 0,         0,         2, Thr 140352349296384, Agentry Startup
02/27/2014 18:51:45, 0,        17,        14, Thr 140352349296384, WebSockets Front End v7.0.2.151
02/27/2014 18:51:45, 0,         1,         4, Thr 140352349296384, Agentry v7.0.2.151
02/27/2014 18:51:45, 0,        20,       150, Thr 140352200132352, Loading Production application definitions using file "SAPWM-v1-0-0-app"
02/27/2014 18:51:45, 0,        20,       152, Thr 140352200132352, Loading Production application definitions for default localization
02/27/2014 18:52:07, 0,        20,       153, Thr 140352200132352, Finished loading Production application definitions for default localization
02/27/2014 18:52:07, 0,        20,       151, Thr 140352200132352, Finished loading Production application definitions using file "SAPWM-v1-0-0-app"
02/27/2014 18:52:08, 0,        24,         4, Thr 140352349296384, Loaded 2 (HTTPXML v7.0.2.151) from ag3httpxmlbe.dll
02/27/2014 18:52:08, 0,        23,         4, Thr 140352349296384, Loaded Java-1 (Java v7.0.2.151) from ag3javabe.dll
02/27/2014 18:52:08, 0,        20,         4, Thr 140352349296384, Server v7.0.2.151
02/27/2014 18:52:08, 0,        17,        10, Thr 140352349296384, WebSockets Front End v7.0.2.151
02/27/2014 18:52:08, 0,         0,         0, Thr 140352349296384, Old log files moved into /opt/SAP/MobilePlatform3/Server/log/agentry/rolled/2014-02-27-185145
02/27/2014 18:52:08, 0,         0,        23, Thr 140352349296384, Agentry startup is complete.
Thread-140352200132352.log
2014/02/27 18:52:07.310: Opening log file
2014/02/27 18:52:07.310: + Thread=140352200132352
2014/02/27 18:52:07.310:   + Server=Agentry
2014/02/27 18:52:07.310:     + Load Loop=Production
2014/02/27 18:52:07.310:       + AppIniFile=SAPWM-v1-0-0-app
2014/02/27 18:52:07.310:         + Module=PM
2014/02/27 18:52:07.310:           + Service Event=WorkOrderPushHTTPListener
2014/02/27 18:52:07.310:             Failed to load definition for Service Event 'WorkOrderPushHTTPListener'
2014/02/27 18:52:07.310:           + Service Event=WorkorderPushByOperationHTTPListener
2014/02/27 18:52:07.310:             Failed to load definition for Service Event 'WorkorderPushByOperationHTTPListener'
2014/02/27 18:52:07.311:           + Service Event=WorkorderPushBySubOperationHTTPListener
2014/02/27 18:52:07.311:             Failed to load definition for Service Event 'WorkorderPushBySubOperationHTTPListener'
2014/02/27 18:52:07.311:           + Service Event=BDSDocumentPushHTTPListener
2014/02/27 18:52:07.311:             Failed to load definition for Service Event 'BDSDocumentPushHTTPListener'
2014/02/27 18:52:07.311:           + Service Event=DMSDocumentPushHTTPListener
2014/02/27 18:52:07.311:             Failed to load definition for Service Event 'DMSDocumentPushHTTPListener'
2014/02/27 18:52:07.311:           + Service Event=WorkorderPushByMRSHTTPListener
2014/02/27 18:52:07.311:             Failed to load definition for Service Event 'WorkorderPushByMRSHTTPListener'
When trying to connect with the WPF client I get a communication error (14) and nothing is shown in the log files ..
Best Regards,
Michel

Jason,
deleting the service events was helpful regarding the error shown in the Thread log file. After publishing a new version the server seems to start, but has no activity to SAP. I expected at least an initial logon to the SAP system using the service user.
Current log files are:
events.log:
02/28/2014 06:16:36, 0,         0,         0, Thr 140136552040192, New files opened events.log, messages.log
02/28/2014 06:16:36, 0,         0,         2, Thr 140136552040192, Agentry Startup
02/28/2014 06:16:36, 0,        17,        14, Thr 140136552040192, WebSockets Front End v7.0.2.151
02/28/2014 06:16:36, 0,         1,         4, Thr 140136552040192, Agentry v7.0.2.151
02/28/2014 06:16:36, 0,        20,       150, Thr 140136413689600, Loading Production application definitions using file "SAPWM-v1-1-0-app"
02/28/2014 06:16:36, 0,        20,       152, Thr 140136413689600, Loading Production application definitions for default localization
02/28/2014 06:17:06, 0,        20,       153, Thr 140136413689600, Finished loading Production application definitions for default localization
02/28/2014 06:17:06, 0,        20,       151, Thr 140136413689600, Finished loading Production application definitions using file "SAPWM-v1-1-0-app"
02/28/2014 06:17:06, 0,        24,         4, Thr 140136552040192, Loaded HTTP-XML Back End (HTTPXML v7.0.2.151) from ag3httpxmlbe.dll
02/28/2014 06:17:06, 0,        23,         4, Thr 140136552040192, Loaded Java-1 (Java v7.0.2.151) from ag3javabe.dll
02/28/2014 06:17:06, 0,        20,         4, Thr 140136552040192, Server v7.0.2.151
02/28/2014 06:17:07, 0,        17,        10, Thr 140136552040192, WebSockets Front End v7.0.2.151
02/28/2014 06:17:07, 0,         0,         0, Thr 140136552040192, Old log files moved into /opt/SAP/MobilePlatform3/Server/log/agentry/rolled/2014-02-28-061636
02/28/2014 06:17:07, 0,         0,        23, Thr 140136552040192, Agentry startup is complete.
messages.log is empty and Thread*.log doesn't exist anymore.
Any further idea how to get this up and running?
Best Regards,
Michel

Syclo Work Manager 6.1 SSL Configurations

Similar Messages

Maybe you are looking for