Processing Data Objects

Procedure

The following table explains the operations that you perform on a data object.

Function	Follow-on Menu Path	What You Should Know
Displaying a data object	Click the data object with the secondary mouse button and choose Display .	The details of the data object are displayed.
Displaying the metadata information of the data object	Click the data object with the secondary mouse button and choose View Metadata .	The metadata information of the data object like the generated CDS tables, associated distribution models, back-end adapters and so on are displayed.
Modifying a data object	Click the data object with the secondary mouse button and choose Change .	When you want to modify a data object, by default, the inactive version of the data object is displayed. If the inactive version does not exist, the active version is displayed. When you modify the active version of a data object, a new inactive version is created. As a result, both the active and inactive versions of the data object exist in the repository. Only one inactive version of a data object can exist in the repository. Therefore, when the inactive version of a data object exists, you cannot create additional inactive versions for the same data object.
Deleting the inactive version of a data object	Click the data object with the secondary mouse button and choose Delete Inactive V...	This deletes the inactive version of the data object from the repository if no active version for the data object exists. However, if an active version of the data object exists, the inactive version is deleted from the repository and the active version is displayed on the user interface. If both the active and inactive versions of a data object exist, by default, the inactive version of the data object is displayed on the user interface. When you delete a newly created data object that is inactivate, the object directory entry for the data object is not deleted immediately. In this case, the object directory entry for the data object is deleted only when the transport request that contains the data object is released. However, if the newly created data object is saved as a local object and you delete the data object without activating it, the object directory entry is deleted immediately.
Deleting a data object	Click the data object with the secondary mouse button and choose Delete .	This deletes the data object irrespective of whether it is an active or inactive version. In addition, the generated objects of the data object are also deleted. When you delete an active version of a data object, you are prompted to specify a transport request if no transport request exists for the data object. The object directory entry for the data object is deleted when the transport request that contains this data object is released.
Activating a data object	Click the data object with the secondary mouse button and choose Activate .	When you activate a data object, the inactive version of the data object is converted as the active version and the previously active version (if any) is archived. When you activate a data object, the DOE performs the consistency check on the data object to check for any inconsistencies or errors. In addition, the following are generated: Databases tables to stage data in mobile middleware Runtime message structure Core services, such as Key Mapping, Data Staging, Rejection, Replication and Realignment, Inbound and Outbound handlers Default flow definition
Checking consistency of a data object	Select the data object and choose Check .	This allows you to check the data object for any inconsistencies or errors. The following are some of the checks that are performed: Name check Namespace check References check Dependency check After you perform the consistency check, if there are: No errors or inconsistencies in the data object, you can activate it. Errors and inconsistencies in the data object, you can save the data object, however, you cannot activate it. You must rectify the errors and inconsistencies before you activate the data object. By default, when you save or activate a data object, the consistency check is performed.
Generating a data object	Select the data object and choose Generate .	When you generate a data object, the following are generated: Databases tables to stage data in mobile middleware Runtime message structure Core services, such as Key Mapping, Data Staging, Rejection, Replication and Realignment, Inbound and Outbound handlers Default flow definition By default, when you activate a data object, the data object is generated. However, if the data related to generation gets corrupted, you use this option to explicitly generate the data object.
Viewing messages	Choose Goto View Logs .	This allows you to view the messages that are logged when you perform the various operations, such as SAVE, ACTIVATE, DELETE.
Object Directory Entry	Click the data object with the secondary mouse button and choose More Functions Object Directory Entry .	This allows you to view the object directory entry for a data object. In addition, you can use this to assign a locally saved data object to a transportable package. To do this, choose Change and in the Package field, enter the name of the transportable package.
Transporting a data object	Select the data object and choose Transport .	This creates a transport request for the data object. If a transport request already exists, the data object is added to the existing transport request. Only an activate a data object can be transported.
Testing a data object	Select the data object and choose Utilities Message Generator .	You can simulate a message that is received from the client device or back-end system by using the message generator. This allows you to test the runtime behavior of a data object. When you choose to simulate a message, you must specify the task type (INSERT, UPDATE, or DELETE) and the name of the flow blue print that processes the message. You can generate a message only for an active data object.