cancel
Showing results for 
Search instead for 
Did you mean: 

Issue while deploying Agentry application on local SMP server

Former Member
0 Kudos

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.

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

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

Former Member
0 Kudos

Hello Stephen,

The configuration under Agentry.INI has "developmentServer" set to False.

My agentry application looks like as below in the screenshot.

The status is still being shown as "RUNNING_WITHOUT_METADATA".

Former Member
0 Kudos

The layout the files is for development logic not production.  Please republish as from the Editor as Production.

Also, i would recommend clearing out the folder as it is not production logic.

Former Member
0 Kudos

Thank you Stephen. Your suggestion worked like a charm!

Answers (2)

Answers (2)

Former Member
0 Kudos

hi,

I have a customer that is experiencing the same thing.  we have cleared out the development traces out of the application folder.  re-published production files with correct version of the agentry editor plugin. zip up the appropriate files from the agentry server, deployed, and receive the same error.  we are working with 6.1.3 editor and SMP 2.3 server.

Former Member
0 Kudos

Patrick,

Please open a new thread or email me.

Stephen

sravanthi_polu
Contributor
0 Kudos

Hi,

Please check the entries in javabe.ini file for test_logon and serivce_logon for invalid password error

Regards,

Sravanthi

Former Member
0 Kudos

Hello Sravanthi,

Thank you for looking into this issue.

My JavaBE.ini (present only under application's root)  has following sections for test_logon and service_logon:

[TEST_LOGON]

UID=kotharar

UPASSWORD=<password>

UGUID=

SERVERSERIALNUM=

[SERVICE_LOGON]

ENABLED=true

UID=kotharar

UPASSWORD=<password>

UPASSWORDENCODED=false

SERVERSERIALNUM=AVKNN@NILKGGBTLD

I am able to log-in to the SAP ECC with these credentials.

What configuration is expected here?