|You can create an Atom feed from a data object model file. A data object model file is a file generated from a data modeling tool such as IBM® InfoSphere™ Data Architect or IBM InfoSphere Discovery. The tool examines each column in the database tables and analyzes the relationships between tables. The data object model file contains the metadata about the table relationships. The nesting and grouping patterns in the Atom feed that you create are based on the table relationships in the data object model file.
You can create an Atom feed from a data object model file. A data object model file is a file generated from a data modeling tool such as IBM® InfoSphere™ Data Architect or IBM InfoSphere Discovery. The tool examines each column in the database tables and analyzes the relationships between tables. The data object model file contains the metadata about the table relationships. The nesting and grouping patterns in the Atom feed that you create are based on the table relationships in the data object model file.
Before you begin
- One physical data model file that matches the database. This file is the data object model file that you generate with the data modeling tool. Review the relationships in the file to verify that the relationships are relevant to the feed that you want to create. If you later change the primary keys or the foreign keys in the database tables, you must regenerate the physical data model file.
- Feeds created from data object files are supported for DB2® databases or for IBM Optim™ archives. For information about supported versions and setup requirements, see Configuring MashupHub for enterprise database feeds.
About this task
To create a feed from a data object file:
Creating a query for data object feed: imc3
- On the Home:Catalog page, click Create and select New Feed.
- Select Data Objects and click Next.
- Upload the physical data model file or enter the web address to access it.
- In the Connection Profile field, select a database connection profile that is already known to MashupHub or select New to create a new profile.
Important: If you edit the connection profile, all feeds that use the profile are affected. Before you edit a profile, ensure that the database schema is the same and that no dependent feeds will be broken.
If you grant Edit permission for a database feed to another user, that user can change the profile, which will change the properties for all the feeds that use that profile.
- If you select a known profile, the remaining fields are automatically filled in.
- For a new connection profile, in the Connection Profile Name field, type the new profile name.
- In the Database Type field, select the database type.
- In the Connection Type field, select Driver Manager (Non-managed Connection) or JNDI (Managed Connection):
(Optim only supports Driver Manager connections.)
The fields that are displayed depend on the database and the connection type that you select.
- Driver Manager (Non-managed Connection): Connects to the database using the JDBC DriverManager interface. Connection management is not handled by WebSphere® Application Server, but through the API instead.
- In the Database Name field, type the database name that contains the tables from which to generate the feed.
- In the Host field, type the hostname or IP address of the database server.
- In the Port field, type the port number.
- For DB2, type the port number that your DB2 server listens on. Tip: On Windows®, you can find the port number in the C:\\WINDOWS\\system32\\drivers\\etc\\services file.
- In the Username field, type the userid that you use to connect to the database.
- In the Password field, type the password that is associated with the userid that you use to connect to the database.
- JNDI (Managed Connection): Applies to DB2 only. Requires the specification of the JNDI name. With managed connections, a connection factory must have been defined by using the WebSphere Application Server Administrative console. This JNDI name needs to have been specified in the connection factory. The JNDI name is case-sensitive.
Restriction: Only direct JNDI names are supported. With direct JNDI names, such as jdbc/myDataSource, the application server assigns default values to the resource reference data. Indirect JNDI names require the use of an assembly tool to define the resource references. They are not supported.
- Click Next.
Select the tables and columns to include in the feed. You begin by selecting one table and then browsing the hierarchy of related tables. The hierarchy is based on the relationships in the data object model file. After you select a table, a tree view of the related tables is displayed. Each table and each column represent an element that you can use in the feed. Columns are repeating elements. Use the hierarchy represented in the tree view to group or to nest the elements in the feed.
Sample format for data objects feeds: imc3
The output for a data objects file feed is in Atom format.
Parent topic: Creating and registering new feeds: imc3
Choosing a feed generator for enterprise databases: imc3