Administration Guide > Configuration > Structure of the Configuration Files > RFC Server

RFC Server

Default values have been specified for the most parameters. They can be changed if needed. Parameters that must be adjusted to your system environmentAn Environment consists of Deployment Targets which represent your endpoints. Different environments are used for different phases in the software delivery cycle, for example Development, QA, Staging, Production. An environment is typically set up once and used by several applications. at any case are written in red letters.

Structure of the INI File UCXSAPC.INI

Section/Parameter Description
[GLOBAL]  

system=

AE system.

This entry must be identical to the entry in the INI file of the Automation EngineThis component drives an Automation Engine system and consists of different types of server processes..

logging=

The path and file name of the log file.

The number signs serve as place holders for a series in numerical order. When starting the agentA program that enables the de-centralized execution of processes (such as deployments) on target systems (computers or business solutions) or a service that provides connectivity to a target system (such as for databases or middleware). An agent is also an object type in the Automation Engine. [Formerly called "Executor."] See also: host, the log files are renamed so that the most current log file is always the one with the number "00".

logcount=

The number of stored log files.

language=

The language in which the logging is processed. Entries for primary and secondary language.

Allowed values: "E", "D", "F"
Default: "E,D" (Primary English, secondary German)

If there is no log in the primary language, a log in the secondary language is searched for.

Helplib=

The name of the message file.

CHANGE_LOGGING_DAYS=

The number of days, after which the log file should be changed.

Default value: 365

CHANGE_LOGGING_MB=

The size in MB, when the log file should be changed.

Default value: 100

The parameter "max_logging_kb" is used for log-file changes if this parameter is not specified.

max_logging_kb=

The maximum size of the log file.

A new log file is created when the size specified here has been reached.

Default value: 1000 KB

log_to_file=

This refers to the creation of log files.

Allowed values: "0", "1" (default values)

"0" = No log files are created
"1" = Log files are created

Logging contents are always sent to the Automation Engine regardless of the specifications made here. These contents are available in the System OverviewThe UserInterface window that contains information about the Automation Engine system..

TimeOut=

The time in seconds during which the CallAPIA programming interface that processes a script in the Automation Engine system. It can be called directly from within the program itself or from a different program. waits for a response from AE. If this is exceeded, the CallAPI ends with a timeout error.

Default value: 60

With the parameter timeout=0 being used, the CallAPI waits (without time limit) until the Automation Engine acknowledges.

[USER]  
clientA closed environment within an Automation Engine system where you can create and run objects. A client name consists of a 4-digit number that must be indicated when a user logs on to the Automation Engine system. Users and their rights are also defined in clients. A particular Automation Engine object type.=

Login specifications: Client

Login data from this section is used when no loginAn Automation Engine object type that stores account credentials used by agents on target systems. data is specified at service-program call

userIn the Automation Engine, a user is an instance of a User object, and generally the user is a specific person who works with Automic products. The User object is assigned a user ID and then a set of access rights to various parts of the Automation Engine system and product suite. These access rights come in the form of Automation Engine authorizations and privileges, Decision user roles and EventBase rights and ARA web application object rights. You can manage all these centrally in the ECC user management functions. See also, Unified user management.= Login specifications: Name of the user
dept= Login specifications: Department of the user
pass=

Login specifications: Password (optional)

The passwordA secret combination of characters for a Automation Engine user. can be encrypted using the programUCYBCRYP.

[RFC]  
hostname=
PROGID=
GWSERV=

These parameters are required for the RFC Server connection.

hostname: Name of the computer on which the SAP Gateway runs. PROGID: Program ID. Any ID of your choice is possible.
GWSERV: Gateway Service Number (e.g.: sapgw00).

This data must comply with the RFC destination data in transaktion SM59 on the SAP system. Example: If you selected "SAP_TEST" in the created destination in SM59, this ID must also be specified in the INI file.

RFC_TRACE=

Creates an RFC Trace

Allowed values: "0" (default), "1"

"0" = RFC Trace is created.

"1" = No RFC Trace is created.

unicode=

Use of "Unicode"- coding in the SAP system.

Allowed values: "0" (default), "1"

"0" = Unicode is not used in the SAP system.

"1" = The SAP system to which a connection is established is a Unicode system.

This information can also be retrieved via the SAP system's RFC connection. In this case, the INI-file parameter must only be specified if there is no RFC connection parameter.

[CP_LIST]

A listShows entities in a grid view of communication processes.

Format:
Port number
= DNS name
Port number
= TCP/IP Address

[TRACE]

 
file=

The path and the file name of the trace file.

The number signs serve as placeholders for a series in numerical order. When you start a trace, the trace files will be renamed so that the most current trace file is always the one with the number "00"

trccount= The number of stored trace files.
xml=

Creates an XML Trace

Allowed values: "0" (default), "1"

"0" = No XML Trace is created.

"1" = XML Trace is created.

 

Example of an INI File

[GLOBAL]
helplib=c:\AUTOMIC\bin\uc.msl
;logging=C:\AUTOMIC\CallAPI\SAP\temp\ucxsapc_logg##.txt
logcount=10
;helpcache=ALL
TimeOut=60
system=UC4
language=(E,D)
CHANGE_LOGGING_MB=100
CHANGE_LOGGING_DAYS=1
log_to_file=0
max_logging_kb=1000

[USER]
client=1
user=test
dept=dept
pass=pw

[RFC]
hostname=sap01
PROGID=TEST
GWSERV=sapgw00
RFC_TRACE=1
unicode=1


[CP_LIST]
2217=fsu

 

[TRACE]

file=../temp/sapc_trace##.txt

trccount=10

xml=0

 

See also:

 


Automic Documentation - Tutorials - Automic Blog - Resources - Training & Services - Automic YouTube Channel - Download Center - Support

Copyright © 2016 Automic Software GmbH