When installing for the first time or changing the Central system where Testimony is operating, each bot’s main config file will need to be updated.
To build the config file that allows the Bot to connect to the SAP central system where Testimony is deployed, most of the information will be on the sap logon pad but you will also require the bot users logon and password and the client where Testimony is being operated from. Each element for the bot is as below:
|ID||The system ID of the central system|
|Instance Number||The instance number of the central system|
|Application Server||The app server for the central system|
|SAProuter String||If one exists for the central system|
|User||The sap user name of the bot user setup on the central system|
|Password||the password for the user above|
|Client||The client of the central system where Testimony is deployed|
|Gateway Host||The same as the application sever above|
|Gateway Service||sapgw + the the instance number (example sapgw00)|
To access the config file go to the bot folder as below and right click on the config file selecting the option to edit.
The config file should appear as below:
Bot Configuration – Specialisations
SAP GUI Location
The bot may be running in an environment where SAP’s SAPGui.exe files are not in the standard location. The logfile on startup will report it as:
A new entry in the config.xml will allow an alternative path to be specified.
If your organisation’s internal policy will not allow the password to be saved into the config file then you can remove the line below in the config file and this will prompt the password to be entered each time the Bot is started.
Message Server and logon Groups
If the central system uses a message server and logon group then the config file can be updated with these three elements below: