IBM BPM, V8.0.1, All platforms > Authoring services in Integration Designer > Services and service-related functions > Access external services with adapters > Configure and using adapters > IBM WebSphere Adapters > IBM i > Reference > Business object information
Naming conventions
When the external service wizard generates a business object, it provides a name for the business object that reflects the naming convention for the adapter. Typically, the business object name indicates the structure of the business object.
Naming convention for Data queue object type - The adapter names business objects according to the <PREFIX> <Queue name> naming convention, where the prefix is DTAQ (for queue business objects) and the queue name is the actual name of the queue on the IBM i system.
For example, the business object representing the QSYS.LIB/MYLIB.LIB/MYQUEUE.DTAQ data queue is named DTAQMYQUEUE by the adapter.
Naming convention for IBM i program (RPG or Cobol) or service program (SRVPGM) object type - For program (RPG or Cobol) or SRVPGM, the adapter names business objects according to the <PREFIX> <PCML name> <Program name>, where the prefix is PGM. For Struct, the adapter names business objects according to the <PREFIX> <PCML name> <Struct name>, where the prefix is PGM.For example, the business object representing the QSYS.LIB/MYLIB.LIB/MSG1PGM1.PGM program is named PGMP1MSG1 by the adapter. In this example, for a PCML say P1.PCML and inside this PCML there are program tags MSG1, MSG2, and MSG3. The program MSG1 have the PGM name as QSYS.LIB/MYLIB.LIB/MSG1PGM1.PGM, so the business object name is PGMP1MSG1.
Business object names have no semantic value to the adapter or the IBM i system; that is, they derive no information nor meaning from the business object name. If one name is replaced by another, the adapter behavior remains the same.
You can rename business objects by using the refactoring functionality in Integration Designer. For more details, refer to the Integration Designer documentation.
Related tasks: