In an integrated environment, determining whether the data published by one application is sufficient for use by another application that retrieves that data is difficult and sometimes unachievable. A publishing application that provides some but not all of the necessary information required by a retrieving application can create complications for the retrieving application.
The process of checking that the information published by a publishing application contains all the necessary data required by a retrieving application is called verification. In Schema Editor, verification is performed on a business object basis. A particular publishing application might provide the necessary information for retrieval of some business objects by another application but fail to provide the necessary information for other business objects. Therefore, verification checking must be performed for each and every business object published by one application and retrieved by another application.
The Schema Editor supports two types of verification:
-
Verification of a publishing application’s tool map schema files versus one or more retrieving applications’ tool map schema files
-
Verification of a published data file versus one or more retrieving applications’ tool map schema files
In both cases, published business objects are compared with the requirements for retrieval for those business objects (as defined by the retrieving application’s map file) to determine the level of compliance of the publishing application.
The following definitions determine the level of compliance between a publishing application and a retrieving application.
-
Level 0 compliance – Some of the required retrieved properties for application A are published by application B.
-
Level 1- compliance – Some of the required retrieved properties for application A are optionally published by application B.
-
Level 1+ compliance – All required retrieved properties for application A are published by application B. If a retrieving application has no required properties, then the publishing application need only publish one of the retrieved properties to qualify as level 1+ compliant.
-
Level 2- compliance – Includes Level 1- compliance plus all optional retrieved properties for application A are published by application B (optional or required).
-
Level 2+ compliance – Includes Level 1+ compliance plus all optional retrieved properties for application A are published by application B (optional or required)
When verification is run against either a publishing tool map schema file or a published data file, a verification report is produced that contains the results of the verification and includes the following information for each published business object.
-
The name of the tool map schema file or the data file used for verification
-
Published class definition (business object)
-
Map class definition for retrieving application
-
Level of compliance (0, 1-, 1+, 2-, 2+) between the publishing application and retrieving application for that business object