on 03-04-2010 1:45 PM
Hi,
I am doing JDBC-File scenario.
Do we need to give field names of sender Message Type(MT) same as they are declared in Database??
If not, if i have 3 fields in sender Message type like below,
Occurence
Row 0..Unbound
Field1 1
Field2 0..1
Field3 0..1
if i execute a query in jdbc sender adapter . how it identifies that the selected fields should send to which fields in sender MT??
and
while i am creating sender data type for JDBC sender, is there any difference if i mention data type as below or both acts in the same manner..??
Occurence
Row 0..Unbound
Field1 0..1
Field2 0..1
Field3 0..1
Occurence
Row 1..Unbound
Field1 1
Field2 1
Field3 1
Thanks,
Murali
> if i execute a query in jdbc sender adapter . how it identifies that the selected fields should send to which fields in sender MT??
The sender JDBC adapter does not care about the data type structure.
You have to define the structure according to the output ouf JDBC adapter.
See online help to see how the structure looks like.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
fieldnames along with upper and lower case and the sequence of the fields should be the same as in the database
or am i missing something
Edited by: Tarang Shah on Mar 4, 2010 7:42 PM
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi stefen,
while i am creating sender data type for JDBC sender, is there any difference if i mention data type as below or both acts in the same manner..??
Occurence
Row 0..Unbound
Field1 0..1
Field2 0..1
Field3 0..1
Occurence
Row 1..Unbound
Field1 1
Field2 1
Field3 1
Thanks,
Murali
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
101 | |
13 | |
13 | |
11 | |
11 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.