Real Time Status Information
Command-Line Interface (Console)
The command-line interface (Telnet) is the main interface to the b+s Connects for SAP Windows processes. You can use the command-line interface to query information directly from the various components. Several monitors can be run at the same time. The impact on the system’s performance is minimal, and the monitor’s features are kept for each session.
Only local access is supported!
Telnet Client is not installed by default on Windows Server. As the remote console processes of the b+s Connects for SAP components can only be accessed locally, it is required to install Telnet Client on each server where a b+s Connects for SAP component is deployed. Check out Installing Telnet for more information
The monitor telnet process supports local commands, which are defined within the
monitor. This section provides a list of basic monitor commands for use with
processes such as <list_ > or <dump_ >.
To navigate or edit the executed commands, use the <Up> or <Down> arrows on
the keyboard.
CRMConnectorSAP
A monitor telnet session for the CRMConnectorSAP can be started by entering the following command at a DOS command prompt:
C:\>telnet localhost <RemoteConsolePort>
...or directly in a Telnet session:
Welcome to Microsoft Telnet Client
Escape Character is 'CTRL+¨'
Microsoft Telnet> open localhost <RemoteConsolePort>
localhost indicates a connection to the local server and is the same as the 127.0.0.1 IP address, which always points to the current machine.
<RemoteConsolePort> is the address of the gateway port, which is set by the following key in the CRMConnectorSAP initialization file:
RemoteConsolePort=42031 (Default)
After the monitor is started, the following prompt will be visible:
welcome to b+s CRMConnectorSAP (SAP1)
remote>
List of Commands
In order to display a basic list of commands, type help. The following list is displayed:
welcome to b+s CRMConnectorSAP (SAP1)
remote>help
Available help:
---------------
Categories:
Default: Contains standard commands like help.
admin: admin commands
list: list commands
Name Aliases Parameters Description
-------------------------------------------------------------------------------------
echo Switch echo on and off.
exit quit Terminates this session.
help ? [Category] Generated help for commands.
help flags List all flag commands
Status s Display gateway status
SStatus ss Display gateway status short
ConfigStatus cs Display config status and all
failures
PrintEnv pe Print environment
RouteStatus rs state of media routing
Trace t [mask] Set trace: with param, set mask and
level; w/o param, toggle trace on/off
CollectedTrace ct [mask] Set collected msg: with param, set
mask and level; w/o param, toggle
trace on/off
SpecialFailure sf [key] count of special failure
LogBookmark lb [bookmark text] write a bookmark stamp as info line to
logfile with bookmark text
GetConfigAgent gca key [mask] list all cti config agent data by
search key and optional search
criteria mask 0x0 .. 0x3f.
ResetAgentMonitor [agentid] reset an agent monitor by agent id
ResetTransactionMonitor ID [Key] reset an transaction monitor by agent
id
ResetRouteMonitor ID Key reset an route monitor by agent id
ScriptSelector Key
ForcedOpenNewLog fol open a new logfile
CrashTheApp crash the app to test minidump
ListAgents la [agentid] List all logged agents states
DumpAgents da [agentid] Dump all agent monitor entry by all
agents
ListTransactions lt List all transactions states
DumpTransactions dt Dump all transaction monitor entry by
all transactions
ListRoutes lr List all route states
DumpRoutes dr Dump all route monitor entry by all
route
ListTpiDllInfo ltdi List tpi dll info
DumpTpiDllInfo dtdi dump tpi dll info
ListDsDllInfo lddi List ds dll info
DumpDsDllInfo dddi dump ds dll info
ListCtiConnect lcc List cti connect info
DumpCtiConnect dcc dump cti connect info
ListFailure lf List Failure
remote>
Using the dump-commands while the system is under heavy load can have a serious impact on CRMConnectorSAP's performance! Use these commands cautiously.
The most important commands to check the current status are the following:
Status Information
In order to display status information, type status. The following list is
displayed:
remote>status
Status (2023.03.22 07:06:16)
-----------------------------------------------------------------------------------------
Start Time: 2023.03.22 - 06:45:01 (UTC: 05:45:01)
Up Time: 0 Days 0 Hours
File Name: CRMConnectorSAP.exe
Version: 2.3.4 (dd9fd14e44a-20230317)
Dll Version: TPI: 2.3.4 (c2743c7e0ef-20230314), DS: 2.3.4 (c2743c7e0ef-
20230314)
Application Status: ACTIVE
Product Activation Key: 123456789
Work Path: 'C:\Program Files (x86)\BucherSuter\MCAforSAP\CRMConnectorSAP\'
Data Path: 'C:\ProgramData\BucherSuter\MCAforSAP\CRMConnectorSAP\'
Proc Name: SAP1
Config URL: 'C:\ProgramData\BucherSuter\MCAforSAP\CRMConnectorSAP\
CRMConnectorSAP_SAP1.ini'
Config Status: ok
Recovery Status: ok
Connect Info Cti: SideA[icmpg1A:42027] - connected (cti prot: 20)
Connect Info Media: MSrvB[medB:7050] - connected
ARM: online, MRI: online
Connect Info Ds: SideA[medA:42029] active, SideB[medB:42029] active connecting
Alloc Msg Obj Count: 1
Access Obj Count: 0
Search Param Obj Count: 1
Media Obj Count Total: 0
Call Obj Count: 0
Media Obj Count: 0
Media Domain Obj Count: 0
Timer Schedule Count: 7
Agents Transactions Route
Monitor Act Obj: 0 0 0
Idle Obj: 0 0 0
Queued Messages: 0 0 0
Waiting Messages: 0 0 0
Activate Count: 0 0 0
MGR Queue: 0
TPI Queue: 0
ICM Cti Queue: 0
ICM Ds Queue: 0
MM Queue: 0
Trace / Collected: 0xFFFFFFF5 (Trace) / 0xFFFFFFFF (Trace)
Failure: 0 Errors / 2 Warnings
remote>
| Item | Description |
|---|---|
| File Name | Name of the CRMConnectorSAP executable |
| Version | CRMConnectorSAP version information |
| Dll Version | Version information for the TPI- and DataStore-DLL |
| Application Status | Overall application status |
| Product Activation Key | Product Activation Key that was entered during product installation |
| Work Path | Path to the working directory of the CRMConnectorSAP |
| Data Path | Path to the initialization file of the CRMConnectorSAP |
| Proc Name | Instance name |
| Config Status | Status of the CRMConnectorSAP configuration read at startup |
| Recovery Status | Status of the CRMConnectorSAP’s action item recovery mechanism |
| Connect Info Cti | Info about the connection to the CTI Server |
| Connect Info Media | Info about the connection to the MediaManager including info about the ARM- and MRI-interface status |
| Connect Info Ds | Info about the connection to the DataStore-services |
| Errors Count | Number of errors logged by the CRMConnectorSAP since startup |
| Warnings Count | Number of warnings logged by the CRMConnectorSAP since startup |
| Allocated Message Objects Count | Internal counter. Current number of internal messages |
| Access Objects Count | Internal counter. Current number of validation elements |
| Search Parameters Objects Count | Internal counter. Current number of search elements |
| Agent Media Objects Count Total | Total number of current allocated voice and media objects |
| Agent Call Objects Count | Number of current allocated call objects |
| Agent Media Objects Count | Number of current allocated media objects |
| Agent Media Domain Objects Count | Number of current media domain objects |
| Timer Schedule Count | Number of current waiting times |
| Monitor Act Obj | Number of monitors which are in use |
| Idle Obj | Number of monitors which are waiting to be recycled |
| Queued Messages | Number of messages in monitor queue |
| Waiting Messages | Number of messages which are waiting to be routed |
| Activate Count | Number of monitors that are active |
| MGR Queue | Number of waiting messages in main queue |
| TPI Queue | Number of waiting messages in queue to SAP ICI |
| ICM Cti Queue | Number of waiting messages in queue to CtiSvc |
| ICM Ds Queue | Number of waiting messages in queue to DataStore |
| MM Queue | Number of waiting messages in queue to MediaManager |
Route Status
The RouteStatus displays the amount of routed media tasks in different status.
remote>RouteStatus
RouteStatus (2023.03.22 07:12:08)
-----------------------------------------------------------------------------------------
Current: 0
RONA: 0
Completed: 0
- Routed ok: 0
- Route end: 0
- Route timeout: 0
- Route overflow: 0
- Route try overflow: 0
- Route stack overflow: 0
- Route error: 0
remote>
Special Failure
By calling the SpecialFailure parameter, a list of failure is displayed with a daily and a total count since the last restart of the CRMConnectorSAP-service. To use the Special Failure command, add the following parameter in the [Dynamic]-Section of the CRMConnectorSAP.ini-file:
WriteSpecialFailure=1
remote>SpecialFailure
SpecialFailure (2023.03.22 07:15:16)
-----------------------------------------------------------------------------------------
con_mm_ref : mediamanager connect refused
DayCount = 1, TotalCount = 1
con_ds_ref : datastore connect refused
DayCount = 0, TotalCount = 0
con_cti_ref : cti connect refused
DayCount = 0, TotalCount = 0
per_off : peripheral offline
DayCount = 0, TotalCount = 0
arm_off : arm offline
DayCount = 2, TotalCount = 2
mri_off : mri offline
DayCount = 1, TotalCount = 1
item_ra : tpi item rejected by agent
DayCount = 0, TotalCount = 0
dev_ofs : device out of service
DayCount = 0, TotalCount = 0
dev_rt_ral : media routing, reroute after logout
DayCount = 0, TotalCount = 0
cti_svr_msg_length : cti svr message length to long
DayCount = 0, TotalCount = 0
agent_login_failure : user login failures
DayCount = 0, TotalCount = 0
remote>
All listed special failures can be called with the respective subcommand to get more detailed information.
remote>SpecialFailure con_mm_ref
SpecialFailure (2023.03.22 07:15:20)
-----------------------------------------------------------------------------------------
mediamanager connect refused detail
DayCount = 1
TotalCount = 1
History
2020.01.23 12:47:30 mediamanager refused
remote>
List Agents
The list agents command lists all logged in agent of that CRMConnectorSAP with a unique index value, the current state, the SAP CRM user name and the Cisco Agent ID.
remote>ListAgents
ListAgents (2023.03.22 08:00:47)
-----------------------------------------------------------------------------------------
Agent list by key ''
Index State User Agent
-------------------------------------------------
00001 NotReady 173000 1713000
remote>
List TPI DLL info
The TPI DLL info command lists all configured values of the TPI DLL.
remote>ListTpiDllInfo
ListTpiDllInfo (2023.03.22 08:03:30)
-----------------------------------------------------------------------------------------
Dll State
TpiConnectDll:
ServicePort 8087
WorkPath: 'C:\Program Files (x86)\BucherSuter\MCAforSAP\CRMConnectorSA
ParameterList: 'SSL_HCT CERASN1 PROXY=10.1.6.3:8084'
BlockTimeout: 120000 mSec
ReceivePoolSize: 200
TransmitPoolSize: 250
PendingTcpServiceSession: 0
PendingTcpClientSession: 0
TcpServiceSessionActivateCount: 0
SendErrorCount: 0
CurrentUserPresenceSession: 0/5
ResponseDelays: WRD=0 WERD=0
Proxy: 10.1.6.3:8084
SSL: not used
remote>
Bookmark
The bookmark command writes an entry into the logfile. Additional to the bookmark parameter, a custom text can be added to specify the purpose of this bookmark.
remote>LogBookmark <insert default text here>
LogBookmark (2023.03.22 08:04:54)
-----------------------------------------------------------------------------------------
Bookmark-001 is written to log
remote>
After calling this parameter in the command line interface, a new entry is written into the log.
012.20.27639 Bookmark-001: <insert default text here>
Data Store
A monitor telnet session for the Data Store can be started by entering following command at a DOS command prompt:
C:\>telnet localhost <RemoteConsolePort>
...or directly in a Telnet session:
Welcome to Microsoft Telnet Client
Escape Character is 'CTRL+¨'
Microsoft Telnet> open localhost <RemoteConsolePort>
"localhost" indicates a connection to the local server and is synonymous with the "127.0.0.1" IP address which always points to the current machine.
<RemoteConsolePort> is the address of the gateway port, which is set by the
following key in the initialization file:
RemoteConsolePort=42030 (Default: 9010)
After the monitor is started, the following prompt will be visible:
welcome to b+s DataStore (SAP1)
remote>
List of Commands
In order to display a basic list of commands, type "help". The following list will be displayed:
remote> help
Available help:
---------------
Categories:
Default: Contains standard commands like help.
admin: admin commands
list: list commands
Name Aliases Parameters Description
--------------------------------------------------------------------------------
echo Switch echo on and off
exit quit Terminates this session
help ? [Category] Generated help for commands
status Display gateway status
sstatus Display gateway status short
snapshot SS [comment] Write snapshot in the log
trace [tracelvl] Get or set the trace level
collected_trace CT [tracelvl] Get or set the trace level for collected
list_transaction lt List all transaction states
dump_transaction dt Dump all transaction monitor entries by transaction
list_ds_dll_info lddi List ds dll info
dump_ds_dll_info dddi dump ds dll info
remote>
Status Information
In order to display status information type "status". The following list will be displayed:
remote> status
Start Time: 11/18/19 11:24:44
Current Time: 12/10/19 15:20:12
Local Time: 12/10/19 15:20:12
---Application Status Summary---
File Name: DataStore.exe
Version: 2.x.x (...)
Dll Version: DS: 2.x.x ...
Application Status: ACTIVE
Proc Name: SAP1
Config Status: ok
Errors Count: 0
Warnings Count: 0
---Application Resource Summary---
Allocated Message Objects Count: 0
Access Objects Count: 0
Search Parameters Objects Count: 0
Timer Schedule Count: 2
Transactions
Monitor Act Obj: 0
Idle Obj: 0
Queued Messages: 0
Waiting Messages: 0
Activate Count: 0
MGR Queue: 0
ICM Ds Queue: 0
remote>
Media Manager
A monitor telnet session can be started by entering the following command at a DOS command prompt:
C:\>telnet localhost <RemoteConsolePort>
...or directly in a Telnet session:
Welcome to Microsoft Telnet Client
Escape Character is 'CTRL+¨'
Microsoft Telnet> open localhost <RemoteConsolePort>
"localhost" indicates a connection to the local server and is synonymous with the "127.0.0.1" IP address, which always points to the current machine.
<RemoteConsolePort> is the address of the gateway port, which is stored in the Media Manager configuration-file (.ini) under the [Main] section.
REMOTE_PORT=7010 (Default: 7010)
After the monitor is started, the following prompt will be visible:
Welcome to MediaManager remote console
Press 'help' for a list of commands or 'quit' to end session
remote>
List of Commands
Entering "help" shows the available commands:
remote> help
Available help:
---------------
Categories:
Default: Contains standard commands like help.
admin: admin commands
list: list commands
Name Aliases Parameters Description
--------------------------------------------------------------------------------------------
echo Switch echo on and off.
exit quit Terminates this session.
help ? [Category] Generated help for commands.
help flags list all flag commands
status s Display gateway status
sstatus ss Display gateway status short
RoutingStatus rs Display routing status
RMStatus rms Display redundance manager status
LogBookmark lb [bookmark text] write a bookmark stamp as info line to
logfile with bookmark text
Trace [mask] Set trace: with param, set mask and
level; w/o param, toggle trace on/off
CollectedTrace [mask] Set collected msg: with param, set mask
and level; w/o param, toggle trace
on/off
WinEventLogLevel well level Set Win Event Log Level: 0=off,
2=statistic, 3=info
ArchiveLogLevel all level Set Archive Log Level: 0=off, 1=error,
2=statistic, 3=info
SpecialFailure sf [comment] count of special failure
ConfigStatus cs Display config status and all failures
CrashTheApp crash the app to test minidump
PrintEnv pe Print environment
ForcedOpenNewLog fol open a new logfile
ListAgents la [id Shows a list of all agents, or filtered
name] by agentid or loginname
ListResources lr Shows a list of all resources
PjArm a Shows list of pennding jobs in arm
handler
PjReq r Shows list of pennding jobs in request
handler
PjReqEx rex key Shows list of parameter of pennding
jobs in request handler
remote>
The most important commands to check the current status are the following:
s(status)la(list_agents)
The remote console command trace can be used to switch trace on/off. The following rules apply for this command:
- if trace level \< trace AND write trace on console ==> trace level = trace
- if trace level = trace AND trace level = trace in ini-file AND write trace on console ==> trace level = info
- if trace level = trace AND trace level \< trace in ini-file AND write trace on console ==> trace level = ini-file value
Status Information
In order to display status information type "status". The following list is displayed:
remote> s
----------------------------------------------------------------------
System State Summary MediaManager.exe 2.x.x (...)
----------------------------------------------------------------------
Start Time: 11/19/19 11:04:35
Local Time: 12/10/19 10:53:38
MRI connected from pg1a.domain (192.168.1.1) ( 1 connections since start.)
ARM[0] connected to pg1a (B) ( 1 connections since start.)
Routing is enabled.
RedundancyManager is in ACTIVE state.
Currently queued tasks: 0 (counted in list) 0 (counter variable) of max. 5000
Currently active MCIL clients: 3
Currently active MCIL routing client sessions: 2
Currently connected agents: 1
ReqHandler Pending Jobs: 0
ArmHandler[0] Pending Jobs: 0
ResourceControl Counters
PendingJobs : 0
ReqMsg : 0
ArmMsg : 0
MriMsg : 0
AgtMsg : 0
GWMsg : 0
DBMsg : 0
CcMaps : 0
TableMaps : 0
Queue Sizes
DB-Queue : 0
Agt-Queue : 0
Req-Queue : 0
MRI-Queue : 0
ARM-Queue[0]: 0
Task counters
RouteRequests : 33
RouteFailures : 0
Rejected overflow : 0
Routed to agent : 33
Routed to label : 0
Canceled requests : 0
Remote>
Chat Connector
A monitor telnet session can be started by entering the following command at a DOS command prompt:
C:\>telnet localhost <RemoteConsolePort>
...or directly in a Telnet session:
Welcome to Microsoft Telnet Client
Escape Character is 'CTRL+¨'
Microsoft Telnet> open localhost <RemoteConsolePort>
"localhost" indicates a connection to the local server and is synonymous with the "127.0.0.1" IP address, which always points to the current machine.
<RemoteConsolePort> is the address of the gateway port, which is stored in the
ChatConnector initialization file (.ini) under the [core] section.
TelnetServerPort=9015 (Default: 9015)
After the monitor is started, the following prompt will be visible:
> Type 'help' to list the available commands.
>
List of Commands
Entering "help" shows the available commands:
> help
Available commands are:
Command Aliases Parameters Description
-----------------------------------------------------------------------------
cfg Configure the
connector's core.
help Display this help text.
httpsrv start|stop|status Control the HTTP server.
list_gates lg List gates.
quit exit Quit the program.
start Start the connector.
stop Stops the connector
status s [mask] Get status of the
connector.
telnetsrv telnet start|stop|status Control the telnet
server.
version v Display version
information.
GC.Collect() gc Calls GC.Collect().
Minidump dmp <file path> Generates a minidump
file. Example: dmp
C:\Minidumps\Minidump1
.dmp.
LogBookmark lb [optional text] Writes a bookmark into
the log file
ListAllConnectorUser lacu list all connector users
ListAllConnectorSession lacs list all chat sessions
ReloadChatUser rcu reload chat user
Commands for $mcil
-----------------------------------------------------------------------------
cfg Configure the gate.
help Display this help text.
lat List agent task.
dat Dump agent task.
vp Dump agent task VarPool.
Commands for $jabber
-----------------------------------------------------------------------------
cfg Configure the gate.
help Display this help text.
lju List jabber users.
radc Reconnect All Disabled
Clients.
To get help on a specific command, use:
help <command>
To get help for a specific gate, type
$<gate id> help
Status Information
In order to display status information type "status". The following list will be displayed:
> status
--- Logger ---
Tracemask: 0xFFFFFFFF
Collected: 0x00000004
Errors: 0
Warnings: 0
--- Core ---
Status: Started
Started at: 12/10/2019 17:27:06 (UTC: 16:27:06)
Server time: 12/10/2019 17:27:19 (UTC: 16:27:19)
--- Gate:mcil ---
Status: Started
Class: McilGate.McilGate
Receive Queue: 0 items
Send Queue: 0 items
Direct Message Dispatcher contains 0 entries
CO-00000000 MmGate.MainConnectorObject
Current State: Ready
Idle Time: 4s
MM status: Connected (MRI:Online ARM:Online)
--- Gate:jabber ---
Status: Started
Class: MatrixGate.MatrixGate
Receive Queue: 0 items
Send Queue: 0 items
Direct Message Dispatcher contains 0 entries
CO-00000001 ChatGate.MainConnectorObject
Current State: Ready
Configuration commands
Use the cfg command to access the configuration values.
[@<portid>] cfg [{<key> [<value>]|!save}]
<portid> is the port identifier to access the configuration. If this part is
omitted, the core configuration is accessed. This parameter determines which of
the top-level sections should be accessed.
<key> is the key to access. If the key-value pair is not in a top-level
section, the path is determined automatically. If this parameter is omitted, the
remote console displays all possible keys.
<value> is the value to set for a given key. If the value contains
whitespaces, it must be surrounded with quotes. If the value contains quotes or
backslashes, they must be preceded with a backslash (escape-character). If this
parameter is omitted, the current value is displayed.
After modifying the settings, save the configuration by using the !save command.
Note that this must be done separately for each part – core and gates.
Example of changing a setting via the remote console
The following example sets the key MmPort in port mm to 7051 and AutoStartHttpServer to false in the core and saves the changes.
>@mm cfg MmPort
7050
>@mm cfg MmPort 7071
Value changed.
>cfg AutoStartHttpServer false
Value changes.
>@mm cfg !save
Configuration saved
>cfg !save
Configuration saved.
Complex and Multivalued Values
There is a special syntax to set the value of complex types or multivalued types, or a mixture of both. With this syntax, strings must be surrounded with quotes, even if they do not contain whitespaces. The configuration of complex and multi-valued types will be padded with explicit examples.
Create a list of values by separating them with commas and surround the list with braces.
{value0,value1,value2,…}
Define a structure by setting the fields using an equal sign and putting the field name on the left-hand side and the field value on the right-hand side. Separate the field assignments with commas and surround the whole structure with parentheses.
(key1=value1, key2=value2,…)
Example of adding users via the remote console
The following example would create a list of two users: Support with password
SupportPassword and Sales with password SalesPassword.
>@jabber cfg ChatUsers {(username=\"Support \",password=\"SupportPassword \"),
(username=\"Sales \",password=\"SalesPassword \")}
Notice the use of a leading backslash (escape-character) before every quote.
CRMConnectorOutboundSAP
A monitor telnet session can be started by entering the following command at a DOS command prompt:
C:\>telnet localhost <RemoteConsolePort>
...or directly in a Telnet session:
Welcome to Microsoft Telnet Client
Escape Character is 'CTRL+¨'
Microsoft Telnet> open localhost <RemoteConsolePort>
"localhost" indicates a connection to the local server and is synonymous with the "127.0.0.1" IP address, which always points to the current machine.
<RemoteConsolePort> is the address of the CRMConnectorOutboundSAP local remote console port, which is stored in the
CRMConnectorOutboundSAP initialization file.
TelnetServerPort=9015 (Default: 9015)
List of Commands
| Command | Alias | Parameters | Description |
|---|---|---|---|
| campaign | c | campaign id | Show specific information about a campaign. |
| campaignitem | ci | [campaign id][account nr] | Shows specific information about a campaign item. |
| campaigns | lc | Show a list of all campaigns. | |
| consolelog | cl | status/off/on [log level] | Manages the console log. If enabled it displays incoming log message with the specified log level. Possible log levels are: debug, info, warn, error and fatal. |
| help | - | <empty> | Displays the help text. |
| logger | log | status/set [trace mask] | Manages the logger. You can set adjust the trace level. The trace mask must be in hex notation like 0xffffffff. For more information see 8.1.3 Log on page 44. |
| monitor | mon | on/off/status | Manages the RFC Server Monitor. |
| quit | exit | <empty> | Quits the program on local consoles or quits the actual telnet session. |
| rfcserver | rfcs, status, s | s | Gets the status of the RFC server. |
| start | - | <empty> | Starts the actual instance. If the instance is already running a restart is triggered. |
| stop | - | <empty> | Stops the actual instance. |
| telnet | - | start/stop/status | Manages the telnet server. |
| version | - | <empty> | Display version information. |
Web Status Page
CRMConnectorSAP
Navigate to the CRMConnectorSAP’s web status page for a collection of useful information about the service. Open a browser window and enter following URL in the address bar to access the web status page:
http://hostname:port/CRMConnectorSAP/services
The hostname is the name of the host where the CRMConnectorSAP is running and port is the configured HTTP service port of the CRMConnectorSAP service. If an HTTP connection can be established successfully, a corresponding message is displayed on the web status page including the identifier of the queried CRMConnectorSAP service.
Health Check Page
Navigate to the CRMConnectorSAP’s health check page to get information about the condition of the service. Open a browser window and enter the following URL in the address bar to access the page:
http://hostname:port/CRMConnectorSAP/healthcheck
The hostname is the name of the host where the CRMConnectorSAP is running and port is the configured HTTP service port of the CRMConnectorSAP service. If an HTTP connection can be established successfully, a short health check report is displayed including the identifier of the queried CRMConnectorSAP service.
It is recommended to use the health check page if a web proxy for handling fail-over between multiple CRMConnectorSAP instances is deployed. This reduces network traffic as the health check page contains significantly less data than the web status page.
Chat Connector
In order to verify that the ChatConnector service is ready and running, open a browser and point it to:
http://hostname:port
For "hostname", use the name of the server where the ChatConnector service is running, and for "port", use the port number given during the installation procedure. This port number can be found in the HttpServerPort setting in the [core] section of the ChatConnector initialization file, or by typing "httpsrv status" on the command-line interface.
HttpServerPort=9085 (Default: 9085)
This service is only available if the AutoStartHttpServer is set to active (1) in the [core] section of the configuration file or if the server has been manually started by typing "httpsrv start" on the command-line interface.
