Properties for the JCo 2 Server
Within a configuration document (by default: <X4>/X4DB/0/jco_server_settings.prop) the number of JCo Server instances, function handler processes and IDoc handler processes are defined. For each JCo Server instance a JCo Server configuration file must be referenced in the central configuration file <X4>/X4config.xml . The properties file is divided into the following blocks.
General configuration
Regarding the allowed server instances and the handling with connections and Connection Pooling, the JCo 2 Server can be configured with the following properties, see Connection Pooling (X4 SAP JCo 2).
# Number of server instances
server_instances_count = Number of JCo Server instancen
usePool = Boolean value
poolSize = Permitted number of connectionsExplanation:
server_instances_count: Number of JCo Server instancesusePool: Activate (true) oder deactivate (false) Connection Pooling, see Connection Pooling (X4 SAP JCo 2)poolSize: Number of permitted client connections in the pool; Recommendation: Choose a value corresponding at least to the sum of the JCo 2 Server instancen (identified by a ProgID).
Function handler configuration
In the following properties the function handlers for RFC/BAPI calls per SAP host are defined. The configuration of the default function handler processes is optional and is only used as a fallback, if no appropriate handler processes were assigned in the function block/method definitions, see Function Block/Method Definitions (X4 SAP JCo 2).
However, commit and rollback handlers can only be agreed using these properties.
# per jcoserver instance settings
# this should always be set in the method definitions
jcoserver.function.handler.userId = User folder within the X4DB (optional)
jcoserver.function.handler.process = Default Function Handler process (optional)
jcoserver.function.commit.userId = User repository for the commit process
jcoserver.function.commit.process = Path to the X4 process for commit
jcoserver.function.rollback.userId = User repository for rollback processes
jcoserver.function.rollback.process = Path to the X4 process for rollbackExplanation:
jcoserver.function.handler.userId: User repository within theX4DB(e. g.1), in which the function call handler process is locatedjcoserver.function.handler.process: Optional path specification to an X4 process serving as default handler for function callsjcoserver.function.commit.userId: User repository within theX4DB(e. g.1), in which the Commit handler process for function calls is locatedjcoserver.function.commit.process: Path specification to an X4 process serving as Commit handler for function callsjcoserver.function.rollback.userId: User repository within theX4DB(e. g.1), in which the Rollback handler process for function calls is locatedjcoserver.function.rollback.process: Path specification to an X4 process serving as Rollback handler for function calls
IDoc processing
In the following properties the handlers for incoming iDocs are defined. The configuration of the default iDoc handler processes is optional and is only used as a fallback, if no appropriate handler processes were assigned in the function block/method definitions, see Function Block/Method Definitions (X4 SAP JCo 2).
For each JCo 2 Server instance (identified by a respective ProgID) only a commit and rollback handler can be agreed using these properties.
If no handler configuration was found, the corresponding Commit respectively Rollback will be skipped.
# this should always be set in the method definitions
jcoserver.idoc.handler.userId = User folder within the X4DB (optional)
jcoserver.idoc.handler.process = Default iDoc handler process (optional)
# commit and rollback handlers for IDocs
jcoserver.idoc.commit.userId = User repository for the Commit process
jcoserver.idoc.commit.process = Path to the X4 process for the Commit
jcoserver.idoc.rollback.userId = User repository for the Rollback process
jcoserver.idoc.rollback.process = Path to the X4 process for the RollbackExplanation:
jcoserver.idoc.handler.userId: Optional specification of the user repository within theX4DB(e. g.1), in which the iDoc handler process is locatedjcoserver.: Optional path specification to an X4 process serving as default handler for iDocs (Fallback)idoc.handler.processjcoserver.: User repository within theidoc.commit.userIdX4DB(e. g.1), in which the Commit handler process for iDocs is locatedjcoserver.: Path specification to an X4 process serving as Commit handler for iDocsidoc.commit.processjcoserver.: User repository within theidoc.rollback.userIdX4DB(e. g.1), in which the Rollback handler process for iDocs is locatedjcoserver.: Path specification to an X4 process serving as Rollback handler for iDocsidoc.rollback.process
Connection settings to the SAP host
In the following properties the settings to connect to an SAP host are defined for the respective JCo 2 Server instance:
# connection String to SAP
jco.server.gwhost = Gateway host
jco.server.gwserv = Gateway service
jco.server.progid = Program ID
jco.server.trace = Boolean value
jco.server.unicode = Boolean value
# required for dynamic repository and metadata lookup
jco.client.client = Client ID
jco.client.user = User name
jco.client.passwd = Password
jco.client.lang = Client language
jco.client.sysnr = SAP system number
jco.client.ashost = SAP application server
jco.client.trace = Boolean valueExplanation:
jco.server.gwhost: Gateway hostjco.server.gwserv: Gateway service (normally sapgwNN)jco.server.progid: Program ID of the SAP hostjco.server.trace: Activate (1) or deactivate (0) RFC trace for the SAP Serverjco.server.unicode: Connect (1) or do not connect (0) in Unicode modejco.client.client: Client ID (three-digit numeric value)jco.client.user: User namejco.client.passwd: Passwordjco.client.lang: Language of the clientjco.client.sysnr: SAP system numberjco.client.ashost: SAP application serverjco.client.trace: Activate (1) or deactivate (0) RFC trace