Restoring an Application Node Using restore-workingconfig.bat

Run restore-workingconfig.bat to restore the server configuration to a previous working state that allows you to restart the current SAP Mobile Server. Use this script only if the server configuration is not in a working state.

The server configuration is backed up automatically each time the SAP Mobile Server starts successfully. When you incorrectly set configuration parameters in SAP Control Center (for example, invalid JVM options, or too many background thread counts), the current SAP Mobile Server may fail to restart.

The property values of the system table CLUSTER_PROPS in the cluster database stores the cluster properties. During server startup, these properties are automatically backed up. By running the script, you restore the following key configurable properties to the previous successful state:

cdb.threadcount
DJC_JVM_MAXHEAP
DJC_JVM_MINHEAP
DJC_JVM_STACKSIZE
DJC_JVM_USEROPTIONS
httpchannel.proxy.tm.max_connections_per_host
httpchannel.proxy.tm.threadcount
maximumMessagesInMemory
maxThreads@http1
maxThreads@https1
maxThreads@https2
maxThreads@tm1
minThreads@http1
minThreads@https1
minThreads@https2
minThreads@tm1
ml.cachesize
ml.threadcount
sup.msg.inbound_count
sup.msg.outbound_count

Stop all SAP Mobile Platform services.
Verify that the root process OBServiceManager.exe and all subprocesses have been stopped.
Run restore-workingconfig.bat in SMP_HOME\Servers\UnwiredServer\bin.
Start SAP Mobile Server and check whether all related services are started, and configuration values are restored.