Creating a feed from an enterprise database (JDBC)Added by IBM on April 28, 2010 | Version 1 (Original)
|You can create a new Atom feed from an enterprise database query. Use SQL to query the database. The feed is created from the data that is returned in the query result set. Tags: feeds, relational databases, DB2, Derby, IDS, Oracle, feeds, enterprise databases, IMS, v126.96.36.199, v2.0, MashupHub, user, administrator, admin
Table of Contents: User and Administrator Guide : Mashup Center 188.8.131.52
You can create a new Atom feed from an enterprise database query. Use SQL to query the database. The feed is created from the data that is returned in the query result set.
Before you begin
For information about supported databases and setup requirements, see Configuring MashupHub for enterprise database feeds : Mashup Center 184.108.40.206
About this task
To create a feed from an enterprise database:
- On the Home:Catalog tab, click Create and select New Feed.
- Select Enterprise Database (JDBC) and click Next.
- In the Connection Profile field, select a database connection profile that is already known to MashupHub or select New to create a new profile.
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):
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.
For IMS databases, type the name of the IMS data store name.
For Oracle, type the System ID (SID) in this field.
- In the Host field, type the hostname or IP address of the database server.
For IMS databases, type the name or IP address of the data store server (IMS Connect).
- In the Port field, type the port number.
- For Derby, the default port is 1527.
- 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.
- For IMS, type the required port number to be used to communicate with the TCP/IP server, IMS Connect.
- 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.
- For IMS databases only, in the Metadata URL field, type the URL for the location of the database view metadata class file. This metadata URL is case-sensitive. The metadata URL is the fully qualified name of the Java metadata class generated by the IMS Enterprise Suite DLIModel utility plug-in from the database source files that contain the database descriptions (DBDs) and program specification blocks (PSBs).
The URL must be prefixed with class://
(for example, class://com.foo.BMP255DatabaseView
For more information about generating the metadata file for your database that can be used for Java applications to access IMS databases, see the IMS Enterprise Suite information
in the IBM® Information Management Software for z/OS® Solutions Information Center.
- JNDI (Managed Connection): 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. The SQL Query Builder window opens.
Parent topic: Creating and registering new feeds : Mashup Center 220.127.116.11