Inhaltsverzeichnis
Naming conventions for jobs
Inbound Jobs
Inbound stands for messages sent to your in-house system from the outside.
Convention:
Here is an example of the inbound job naming convention:
Outbound Jobs
Outbound stands for messages sent from your in-house system to the outside world.
Convention:
Here is an example of the naming convention for the outbound jobs:
special/ administrative jobs:
By special is meant that the jobs are not required for automated messaging
or processes that are neither inbound nor outbound, but processes that are triggered manually.
Under this we understand e.g. the discard job.
Convention:
Here is an example of the naming convention for the special jobs:
Naming job objects
The many different job objects also offer both names and remarks. Since usually the job object names are generated only generically when creating,
it is helpful for reading and understanding TraceLogs or processes, if the generic names of the job object are supplemented with the contents of the most important attribute or renamed completely.10)
Examples:
- EntitySelector Names are e.g. completed with the type name that is to be selcted.
- EntityTransformer Names contain references to the mappings which are to be used.
- EntityIfCase Names ideally reflect your switching mechanics.
- EntityMessageCreator names are supplemented with the name of the message box into which containerization is to be performed.
1)
“i” in this case stands for inbound)
4)
“o” in this case stands for outbound
7)
“z” in this case stands for special jobs (neither incoming nor outgoing). When naming with the letter “z”, it has the advantage,
that the special jobs are at the end of the job listing
that the special jobs are at the end of the job listing
8)
The jobs are numbered in ascending order
9)
The jobs are given a brief description (bullet points) of what is done in it
10)
for example, by copy paste of the main attribute property.