KB Article #182065
Character restrictions for pop.cfg, j_select.cfg and ssi.cfg parameters
Problem
There is a need to know the character restrictions for the value of parameters from param/newconfig/pop.cfg (POP_SENDER, POP_RECEIVER and POP_OBJ_CLASS), param/newconfig/ssi.cfg (SSI_SENDER, SSI_RECEIVER and SSI_DATA) and param/newconfig/j_select.cfg (EV_ATTRI).
Resolution
Character restrictions:
1. POP_SENDER, POP_RECEIVER and POP_OBJ_CLASS from file param/newconfig/pop.cfg:
These parameters allow ISO-8859-1 characters, but do not permit regex wildcards, meaning the following characters are not permitted:
'\', '[', ']', '.', '^', '$', '*', '|', '{', '}', '(', ')'.
This does not mean that it is illegal to have partners or object classes that contain these characters.
If you really want to have a partner name or object class that contains a '.', it is still possible to generate events for it. However, it can only be
done with j_select.cfg with the use of regexes.
Spaces are permitted, but it is recommended to avoid using them, since you might encounter difficulties having to escape them or use quotes when generating the events.
2. SSI_SENDER, SSI_RECEIVER and SSI_DATA from file param/newconfig/ssi.cfg
These parameters from ssi.cfg do not have any restrictions in terms of regex special characters. However it is recommended not to use these characters here either, as
there would be problems creating pop.cfg entries with them.
Any value that is accepted by partner.cfg and objclass.cfg should be acceptible here.
3. EV_ATTRI from file param/newconfig/j_select.cfg
This parameter initiates a new job selection entry. It generally consists of a sender (SENDER), a receiver (RECEIVER) and a data type (OBJ_CLASS). The parameter's attributes will be interpreted from the left to the right beginning with SENDER, RECEIVER etc. It has length from 16 characters for key.
This also permits ISO-8859-1 characters.
The values of the parameters here (ex. values of SENDER, RECEIVER, OBJ_CLASS, etc.) are interpreted as regexes, meaning that some special characters
will not be taken explicitly (ex. '\', '[', ']', '.', '^', '$', '*', '|', '{', '}', '(', ')', etc.).
Example patterns:
- EV_ATTRI=SENDER=.* RECEIVER=receiver OBJ_CLASS=SAP_IDOC -> SENDER can have any value.
- EV_ATTRI=SENDER=abcd.+ RECEIVER=receiver OBJ_CLASS=SAP_IDOC -> SENDER can be anything that starts with "abcd" and contains at least one character after.
- EV_ATTRI=SENDER=SSSS\.SSSS RECEIVER=RRRR\.RRRR OBJ_CLASS=OOOO\.OOOO -> the '\' is used as an escape character for '.'