...
| Code Block |
|---|
[foobarInstance] SYSID = X |; |1 | MANDANT = X |; |2 | CONTREP = C |; |3 | LoginCL = S |; |0 |@SYSID@MANDANT |
Example Schemata
here the index files gives mandant and contrep and the LoginCL variable then contains the SAP connector instance id
...
As you see, LoginCLis connected to the Variable S. We see it is concatenated from 2 others. So in index file, the concatenation from place 1 and 2 gives the variable value of LoginCL. This value is pointing to an existing SAP-Connector instance with this name.
Real Example
The Document Router is configured with index-Files. Those .idx-Files contain following lines:
| Code Block |
|---|
Q80;105;XY; |
| Code Block |
|---|
Q80;103;ND; |
| Code Block |
|---|
Q80;134;NF; |
Following the previous given Schemata-Example this would mean:
Q80 = SYSID
105,103,134 = MANDANT
XY,ND,NF = CONTREP
In the Schema above is in Line 5 following configured as “S” (SIDLinking) : @SYSID@MANDANT whereas @SYSID is on place 1 and @MANDANT is on place 2
That means, the DocumentRouter 4.x will concatinate Field 1 and Field 2 and try to find a SAP-Connector-Instance with that Name. In this Example with those three different Index-Files the Document Router tries to call SAP-Connector-Instance:
Q80105
Q80103
Q80134
Means: If those Connections are available (and configured in the SAP-Connector), the DR will Link to those individual SAP-Configurations.