Dan,

I am using SQL maps in GIS 4.1.

I have not come across the "invalid SQL map" issue.  But, I can tell you
how we have our process setup.  

GIS requires that you use a JDBC connection (called a Data Pool) to the
database by using the jdbc.customer.properties file and running the
"Install3rdParty" command to import the JDBC drivers into GIS.  If
you've built GIS on a SQL server the Install3rdParty command is not
necessary.  It is required that the Data Pool name be the same as the
ODBC DSN name.  

The jdbc.properties file can be used as a reference for the attributes
you must setup for your new Data Pool.  If you ask Sterling they can
give you all the details to this file.

Now for something Sterling may or may not tell you:  When exporting data
to your database using a SQL map you will not have any correlation data
to review.  I brought this to Sterling's attention and the group has
heard me mention it a million times, but here I go again... :)  The
problem is that JDBC requires results in order to report anything in
GIS.  When you send data to a database there is no result to report.
Therefore once the data has been exported to your database the Primary
Document in GIS becomes empty, thus removing any trace of the
translation document for correlation data to display.  It was a painful
discovery that prompted another six to eight months worth of development
to overcome it.  If you are interested please let me know.

As for translation, I am simply using each partner envelope with the map
assigned to it.  A regular translation service will work as well as long
as your Data Pool is setup.  I have not needed to use the JDBC adapter
with the map assigned.

Let me know if you have any specific issues you'd like to discuss
regarding these types of maps.  We're using them with great success on a
couple different database types.

Have fun,

David Nielson
Lifetime Products
(EDIJunkie)

-----Original Message-----
From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of
pemadorje
Sent: Tuesday, September 26, 2006 11:37 AM
To: [email protected]
Subject: [EDI-L] GIS 4.1 - Difficulties mapping to SQL


I am using GIS 4.1. I'm in the process of trying to map XML data 
directly into a SQL database. I've finished the mapping part of it and 
from within the map I'm able to successfully test connectivity to the 
database. But now, I'm not sure how to handle the business process 
part of it. I'm assuming that I need to use a JDBC adapter and then 
specify my map in the adapter. But when I test this it says that my 
map is not a valid SQL map file. If anyone has any suggestions or can 
at least nudge me in the right direction I would greatly appreciate it.

Thanks very much in advance,
-Dan











...
Please use the following Message Identifiers as your subject prefix:
<SALES>, <JOBS>, <LIST>, <TECH>, <MISC>, <EVENT>, <OFF-TOPIC>

Job postings are welcome, but for job postings or requests for work:
<JOBS> IS REQUIRED in the subject line as a prefix. 
Yahoo! Groups Links






 



________________________________________________________________________
This email has been proactively scanned for all known and unknown
viruses.  This message is now certified Virus-free.
________________________________________________________________________


...
Please use the following Message Identifiers as your subject prefix: <SALES>, 
<JOBS>, <LIST>, <TECH>, <MISC>, <EVENT>, <OFF-TOPIC>

Job postings are welcome, but for job postings or requests for work: <JOBS> IS 
REQUIRED in the subject line as a prefix. 
Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/EDI-L/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://groups.yahoo.com/group/EDI-L/join
    (Yahoo! ID required)

<*> To change settings via email:
    mailto:[EMAIL PROTECTED] 
    mailto:[EMAIL PROTECTED]

<*> To unsubscribe from this group, send an email to:
    [EMAIL PROTECTED]

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/
 


Reply via email to