Talking about JAVA...script and more

After we have configured our portal object, we must install the gateway application and modified the target application. 1. Deployment of the Gateway Web J2EE Application : We must to create an j2ee web application with the purpose to be a gateway from every application that want to validate the SAP Ticket Logon. I have created this application because of the problem with the sapssoext library provied from SAP, it can't be loaded from more than one classloader, then this new web application will be the unque application on the server that can load this library. This application could expose 2 or more services, it depends of you. I will mention 2 services: /SsoGatewayWeb/ssojson.dtx : under this URI will happen the vaidation of the SAP Ticket Logon sent by the SAP Portal, it returns a JSON string with the information retrieved from the ticket. /SsoGatewayWeb/sendsso2cookietest : this URI generates HTML content, it generates the string ACL of the certificate file. Both only acc...

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...

For this part, we will create, build and deploy a J2EE Application on SAP AS 7.0 with J2SE 1.4, and the version of Spring Framework is 2.0.8 because it is the last one that can be supported by J2SE 1.4. For the Spring XML configuration we will use the XML configuration syntax based on XML Schema, also we could use syntax based on XML DTD for backward compatibility. Because of we are using J2SE 1.4, we will need a parser that supports XML Schema like Xerces. We need to remind that when you create an application with transaction support, we could use 2 type of transaction: Local Transaction are resource-specific (by example when only we work with one resource that needs transaction support like jdbc connection). Global Transaction are managed by the application server using JTA, it provide the ability to work with multiple transactional resources (by example when we work atleast two resources that need transaction support like jdbc connection, and jca connection). Now, we must fo...