| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Graphical Mapping - Configurable Datasource ? |
« View previous topic :: View next topic » |
| Author |
Message
|
| akil |
 Posted: Sat Jun 28, 2014 10:41 pm Post subject: Graphical Mapping - Configurable Datasource ? |
 |
|
Partisan
Joined: 27 May 2014
Posts: 338
Location: Mumbai
|
Hi
As per this link - http://www-01.ibm.com/support/docview.wss?uid=swg21403712 , there is a dataSource property for the Mapping Node.
However, I don't find it in the IDE, and if I try to set it via mqsiapplyoverride it fails saying property not supported when I eventually deploy. Even mqsireadbar does not list the dataSource property.
So currently, I change the map xml manually to point to reconfigure dataSource, and corresponding changes in the data projects, so while there is a workaround, it is a bit clunky and error prone.
Is override the dataSource available? or is there a better way to manage changes to the dataSource? |
|
| Back to top |
|
 |
| martinb |
| Posted: Sun Jun 29, 2014 1:34 am Post subject: |
|
|
Master
Joined: 09 Nov 2006
Posts: 210
Location: UK
|
You need to be state what version of the Broker you are running.
The Mapping technology was replaced in Broker v8, and the properties of the Mapping node and it's connection to Databases is diffrent.
The previous version message maps can still be run but not modified in Broker v8 and v9.
Given that you report you can't see a datasource property on the Mapping node in the Tooling and provoke errors by attempting to set an override for it, implies you are in fact using the new Mapping node.
The new Mapping node does not have a Datasource property because as noted in the info centre, (
Mapping database content), it makes it connection to the databae via a JDBC.
Hence it uses a JDBC Provider Configurable service in the runtime to provide the details of the database server to be used.
The "data source" name in the database transforms in your Graphical Data Map selects the JDBC Provider Configurable service. The properties of the JDBC Provider Configurable service give you all you need to point to a particular database server, and configure overrides for the database name, and database schema to be used by the runtime. See Setting up a JDBC provider for type 4 connections
So the typical cycle would typically be
- Designer connects his Toolkit to a development database server and runs discovery on the tables etc to be included in the map. The map database transforms have the "data source" name of the connected development database.
- When deploying the application the administrator provides a JDBC Providers configurable service having the corresponding data source name and sets it's properties to specify the database server, database name, and perhaps database schema name to be used in the relevant test, staging or production environment |
|
| Back to top |
|
|
| akil |
| Posted: Sun Jun 29, 2014 5:11 am Post subject: |
|
|
Partisan
Joined: 27 May 2014
Posts: 338
Location: Mumbai
|
Hi
Sorry, I should have put the version, the version that I am using is 9.0.0.0.
The database that we are connecting to is Oracle.
At design time, we are manually creating the table structures ( this is a fresh development, and so the table structure is being defined by the developer ).
There are 3 of us, doing development at the same time , and need to connect to separate database's , we all end up using 'Default' as the database name in the data project.
While creating the JDBCProvider, we individually point to different database's (like you mentioned), for our datasource name 'Default'
Now, when we have to do a deployment to the Integration environment, we end up with a clash, since all of us have used the same dataSource name but we want to point to different database's, but the JDBCProvider has dataSource name as the unique identifier.
At this point, we are manually changing the XML files to make the dataSource name different across the 3 files. I suppose we need to fix some sort of convention for dataSource names, but it would have been good if dataSource name was configurable ..
_________________
Regards |
|
| Back to top |
|
|
| akil |
| Posted: Tue Jul 01, 2014 11:10 am Post subject: |
|
|
Partisan
Joined: 27 May 2014
Posts: 338
Location: Mumbai
|
Hi
I hope my last update on this post was not unclear, I suppose I've to set some sort of common dataSource naming guideline across designers to avoid name clashes when all the flows get together .
_________________
Regards |
|
| Back to top |
|
|
| martinb |
| Posted: Tue Jul 01, 2014 11:18 pm Post subject: |
|
|
Master
Joined: 09 Nov 2006
Posts: 210
Location: UK
|
Hi
Yes OK I understand your issue.
However since it sounds like each of you is effectively building a data design of separate databases, when you are creating your models via "physical data model" ".dbm" files, as you say you should be picking a unique name for the database, rather than all leaving the value as the default of "Default".
The Data model tools provides this rename to be done it it's UI, rather than having to open and edit the Broker map file in a text editor. |
|
| Back to top |
|
|
| akil |
| Posted: Wed Jul 02, 2014 2:17 am Post subject: |
|
|
Partisan
Joined: 27 May 2014
Posts: 338
Location: Mumbai
|
Hi
The data project allows a rename, but the graphical data map does not get refactored. The file that needs to be changed by hand is the GDM File.
For example , in the following line , mssql.dbm is the data project name, DESK is the dataSource name , dbo is the schema name, EXNA is the table name. I change the dataSource name by editing this file, once I rename the data project via the UI.
| Code: |
<output path="db:table(/mssql.dbm,DESK,dbo,EXNA)" var="EXNA"/>
|
I hope I am doing it right..
_________________
Regards |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
