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