cancel
Showing results for 
Search instead for 
Did you mean: 

Connecttest.bat not working

Former Member
0 Kudos

I have SMP 3.0 installed (patch 04) and I believe the server credentials are correct but cannot get a connection.

Connecttest.bat is installed in folder: C:\SAP\MobilePlatform3\Server\configuration\com.sap.mobile.platform.server.agentry.application

Where are LOGS for the connecttest.bat or where should errors show up please?

JavaBE.ini:

[HOST]

;server=localhost

server=epd.xxx.com

;  mobile application name configured in sap like SMART_WORK_MANAGER_51, SMART_CUSTOMER_SERVICE_10, SMART_ISU_WORK_MANAGER_10...etc

APPNAME=SAP_WORK_MANAGER_61

[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

;source=INI

[JCO]

CLASS=JCO3

[TEST_LOGON]

UID=sapServiceUser

UPASSWORD=sapServiceUserPW

UPASSWORDENCODED=false

UGUID=

SERVERSERIALNUM=SAP_WORK_MANAGER_61

;  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=sapServiceUser

UPASSWORD=sapServiceUserPW

UPASSWORDENCODED=false

SERVERSERIALNUM=SAP_WORK_MANAGER_61

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

The ConnectTest.bat file is a command line program there is no log files it is exected to open a command line and then run the applications.

There is a issue with the ConnectTest.bat file in Work Manager 6.1 see SAP note: 2042566 - Patch to correct connectTest.bat Java Exception under Work Manager 6.1, Inventory Manager 4.0

Former Member
0 Kudos

My local VM has the newest patched version of SMP (3.0.4.0).  The Dev SMP server has version 3.0.3.0 installed (not updated).  I get exactly the same results on both SMP servers.

I also have done the fix in patch 2042566 (put 2042566.jar in /Java folder) to no avail on both servers.

I am pretty sure everything else is correct... should I just wipe everything out and start over? 

Does SMP service need to be started for connecttest.bat to work? (I think the answer is: no)...

Former Member
0 Kudos

What error do you get when run the connectTest.bat from command line?

Former Member
0 Kudos

Error: *** Caught exception: null

Here is the full text from DOS command:

INI file: F:\SAP\MobilePlatform3\Server\configuration\com.sap.mobile.platform.se

rver.agentry.application\JavaBE.ini

Encoding: ASCII

reading user credentials from [SERVICE_LOGON] section

connecting as...

clientNum=110

sysNum=00

host=epd.xxx.corp

name=smpAdmin

openCustomConnection::begin

beginStatefulConnection::begin

*** Caught exception: null

release::releasing connection

endStatefulConnection::begin

release::complete.

Press any key to continue . . .

bill_froelich
Product and Topic Expert
Product and Topic Expert
0 Kudos

Can you also share your classpath from the Agentry.ini or SMP Management Cockpit?

--Bill

i834235
Product and Topic Expert
Product and Topic Expert
0 Kudos

You usually get Null pointer exception either because  your missing some entries in Agentry.ini file or java path is not correct.

Thanks

Manju.

Former Member
0 Kudos

I am running connecttest.bat from a command prompt. 

We are running connecttest.bat from the server where SMP3 is installed so there should be no connectivity errors or problems. 

  • SMP Path (where connecttest.bat exists): F:\SAP\MobilePlatform3\Server\configuration\com.sap.mobile.platform.server.agentry.application
  • ​Java Path for connecttest.bat: F:\SAP\MobilePlatform3\Server\configuration\com.sap.mobile.platform.server.agentry.application\Java
  • ​In the SMP Server environment variables:

PATH = C:\ProgramData\Oracle\Java\javapath;D:\SAP\ASE-16_0\jobscheduler\bin;D:\SAP\ASE-16_0\dll;D:\SAP\ASE-16_0\bin;D:\SAP\SCC-3_3\bin;D:\SAP\DBISQL-16_0\bin;D:\SAP\DataAccess64\ADONET\dll;D:\SAP\DataAccess\ADONET\dll;D:\SAP\DataAccess64\ODBC\dll;D:\SAP\DataAccess\ODBC\dll;D:\SAP\OCS-16_0\lib3p64;D:\SAP\OCS-16_0\lib3p;D:\SAP\OCS-16_0\dll;D:\SAP\OCS-16_0\bin;%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\

Classpath from Agentry.ini:

classPath=./ini4j.jar;./sapjco3.jar;./Java/Agentry-v5.jar;./Java;./Java/SAPWM-

6.1.1.0.jar;./Java;./Java/SAPCommon-133461.jar

Not sure if I need the jar file patch: 2042566.jar

bill_froelich
Product and Topic Expert
Product and Topic Expert
0 Kudos

You need the jar file patch also included in the classPath per the note.

--Bill

Former Member
0 Kudos

by 'jar patch' do you mean the '2042566.jar' file?  I have added that to the Agentry.ini Java path to no avail.  Does the connecttest.bat even reference the Agentry.ini file?  Do I need any of these in my Environment paths? ie: JAVA_HOME or similar variables for the environment?

From Agentry.ini file:

[Java-1]

classPath=./Java/2042566.jar;./ini4j.jar;./sapjco3.jar;./Java/Agentry-v5.jar;./Java;./Java/SAPWM-6.1.1.0.jar;./Java;./Java/SAPCommon-133461.jar

Former Member
0 Kudos

is the Agentry.ini file even referenced in the connecttest.bat operation?

I have a pointer to localhost in the agentry.ini file

Here is the whole agentry.ini on the SMP server (where I am running the connecttest.bat):

ASA Added: ==================================

[Agentry]

systemName=SAP Work Manager Server v6.1.0.0

[Configuration]

applicationGlobalsFile=Globals.ini

applicationStringsFile=ApplicationText.ini

clientStringsFile=ClientText.ini

developmentServer=True

transmitConfigurationFile=TransmitConfigurations.ini

[HTTPXML-2]

authenticationCertificateStore=MY

authenticationCertificateStorePassword=

authenticationCertificateStorePasswordEncoded=false

autoDequote=true

baseURL=http://localhost:8282

basicAuthenticationPassword=xxxx

basicAuthenticationPasswordEncoded=false

basicAuthenticationUserID=smpAdmin

constantsFile=httpxml_sd.ini

enableAuthentication=true

enablePreviousUserAuthentication=true

httpConnectTimeout=60

httpReceiveTimeout=300

httpResolveTimeout=60

httpSendTimeout=300

listenOn=8282

name=HTTP-XML Back End

timeZoneName=

timeout=300

useSSL=false

xmlAllowXSLTScript=true

xmlNamespaces=

xmlResolveExternals=true

xmlValidateOnParse=true

[System Connections]

1=ag3javabe.dll

2=ag3httpxmlbe.dll

[Java-1]

classPath=./Java/2042566.jar;./ini4j.jar;./sapjco3.jar;./Java/Agentry-v5.jar;./Java;./Java/SAPWM-6.1.1.0.jar;./Java;./Java/SAPCommon-133461.jar

constantsFile=

deleteSource=True

enableAuthentication=True

enablePreviousUserAuthentication=True

initialHeapSize=256

maxHeapSize=512

name=Java Back End

nonStandardJavaOptions=

outputDirectory=.

performCompile=False

printBusinessLogicStackTrace=False

printStackTrace=False

reduceOSSignalUse=True

scriptsPath=

serverClass=com/syclo/sap/workmanager/Server

sourceDirectory=.

timeZoneName=

[LastUpdates]

Java-1=13:16:47 10/6/2014

ASA Added: ==================================

bill_froelich
Product and Topic Expert
Product and Topic Expert
0 Kudos

Connecttest.bat does not reference the Agentry.ini classpath but instead has it's own classpath within the batch file.  Be sure to set the connecttest.bat classpath to be the same as the Agentry.ini one (i.e. include the '2042566.jar'.

--Bill


Answers (1)

Answers (1)

Former Member
0 Kudos

Here are the results of java -version (if this helps):

C:\SAP\MobilePlatform3\Server\configuration\com.sap.mobile.platform.server.agent

ry.application>java -version

java version "1.7.0_67"

Java(TM) SE Runtime Environment (build 1.7.0_67-b01)

Java HotSpot(TM) 64-Bit Server VM (build 24.65-b04, mixed mode)

Former Member
0 Kudos

should I have 'set ' before the path statements in agentry.ini and connecttest.bat?  I'm pretty sure I need it for the .bat file because it is literally setting the path...

Former Member
0 Kudos

"Set=" should only be in the connectTest.bat. The "set=XXXX" should match the Agentry.ini "classPath=XXXX'

Former Member
0 Kudos

yes, that is exactly how I have connecttest.bat and agentry.ini set:

"Set=" should only be in the connectTest.bat. The "set=XXXX" should match the Agentry.ini "classPath=XXXX'

Anything else you see in the settings in either file?

This is driving me nuts...