Talking about JAVA...script and more

In the previous part ( 1st ) , we saw how to configure SAP JTA Transaction into the Spring Context, now we are going to review the SAP J2EE Datasources. We need to review two parts: 1. Configuration of the JEE datasources in the data-sources.xml file (in according to the SAP AS Platform). In the next picture, you can see the last file that I used in my project In this image you can see the definition of the Driver JDBC (2nd box), it needs to be set-up in the Visual Administrator. After, you see the sql-engine tag, it allows us to define the SQL type support ( help ). The valid values are ( link ): Open_SQL: the system returns a DBI CommonConnection Native_SQL: the system returns a DBI DirectConnection Vendor_SQL: the system returns a standard connection from JDBC driver (not using DBI at all) In this case, I have used the value of Vendor_SQL because I have used iBatis in my persistence layer and not the persistence engines of SAP NW AS (jdo or entity beans). Finally, you need to

In the previous part ( 1st ), we saw how to configure SAP JTA Transaction into the Spring Context, now we are going to review the SAP J2EE Datasources. We need to review two parts: 1. Configuration of the JEE datasources in the data-sources.xml file (in according to the SAP AS Platform). In the next picture, you can see the last file that I used in my project In this image you can see the definition of the Driver JDBC (2nd box), it needs to be set-up in the Visual Administrator. After, you see the sql-engine tag, it allows us to define the SQL type support ( help ). The valid values are ( link ): Open_SQL: the system returns a DBI CommonConnection Native_SQL: the system returns a DBI DirectConnection Vendor_SQL: the system returns a standard connection from JDBC driver (not using DBI at all) In this case, I have used the value of Vendor_SQL because I have used iBatis in my persistence layer and not the persistence engines of SAP NW AS (jdo or entity beans). Finally, you need to de