Java and i. A Salesforce Recipe: Integrating Java and RPGLE

Transcription

1 Java and i A Salesforce Recipe: Integrating Java and RPGLE Dr. Paul Coleman Systems Integration Consultant paul.coleman@averyinstitute.com April 13, 2011

2 Introduction Problem: Legacy RPGLE CRM to Salesforce.com Web Services API (SOAP & REST) Constraints: Limited Budget & Tight Schedule Do not reinvent the wheel regarding HTTP & XML No in-house C expertise Must have compile-time type checking Solution: Java WS via ILE binding and Java Native Interface (JNI)

3 The Salesforce Integration Plan Educate RPGLE team Implement the Salesforce WS clients (SOAP and REST) in Java Synchronize compile-time stubs with Salesforce object definitions using XSLT Implement direct integration in free-format RPGLE, reusing existing modules and service programs when appropriate

4 Java and RPGLE H ACTGRP(*NEW) DFTACTGRP(*NO) H MAIN(main) D main PR EXTPGM('TEST') P main B D main PI /FREE dsply 'Hello World'; /END-FREE P E

5 Java and RPGLE public class Test { public static void main(string[] args) { System.out.println("Hello World"); } }

6 Java and I Installed LICPGM

7 Performance Tests Test Description: record REST (bulk) upload in one job of four batches (submitted to Java in two method calls of records each). Contact records were used for testing, hard coded with the same values for each object intentionally forcing all records to fail processing because of duplication. Each test was submitted three times to ensure that startup and JIT optimization (caching) were included in the tests. 5 min 9 secs Classic VM (build 1.6, build JDK-1.6, native threads, jitc) 64bit JAVA_HOME= /QIBM/ProdData/Java400/jdk6 2 min 35 secs IBM J9 VM (build 2.4, J2RE IBM J9 2.4 OS400 ppc64-64 jvmap (JIT enabled) 64bit JAVA_HOME= /QOpenSys/QIBM/ProdData/JavaVM/jdk60/64bit 2 min 13 secs IBM J9 VM (build 2.4, J2RE IBM J9 2.4 OS400 ppc-32 jvmap (JIT enabled) 32bit JAVA_HOME= /QOpenSys/QIBM/ProdData/JavaVM/jdk60/32bit JDK Reference Material:

8 Environment VARs

9 Salesforce.com Components Enterprise WSDL Partner WSDL Apex WSDL Apache Axis 1.4 Web Services Framework

10 Generating the Java Stub View enterprise.wsdl java -cp axis.jar:axis-ant.jar:commons-discovery- 0.2.jar:commons-logging jar:jaxrpc.jar:log4j jar:saaj.jar: wsdl4j jar:mail.jar:activation.jar org.apache.axis.wsdl.wsdl2java -o ~/SalesforceClient/ -a ~/enterprise.wsdl View c.sfadapter / cb.sfbulkadapter (short package names) Generate and move jar files to i server: /QIBM/UserData/Java400/ext folder acts as the typical /jdk.x/jre/lib/ext global classpath folder for jar files

11 Generating the RPGLE Stub View extractsfsourcememberprototypes.xsl View stubsourcememberprototypes.xml View SF Source Members RDP/RDi can generate the prototype declaration for a Java class for you: 1] Right-click in LPEX editor 2] Select New Java Method Call 3] Browse for the.class file for jar, then select the desired method

12 A look at the WSDL & Java

13 A look at the XSL

14 A look at the RPG XML

15 The final RPG Prototypes Method s Object Return Type Java class and procedure name (Method) Java byte[] array return type Object Type Input Parameter

16 RPGLE using Java Prototypes Can you tell what is Java and what is RPG? Constructing Java Class Instance First Parm into Java procedure calls is always the Java class instance variable unless the Java procedure is a *CONSTRUCTOR method or is declared as STATIC

17 Testing & Debugging ILE usage of Java is through JNI Compile time type checking for instance objects is by pointer, not by actual Java type. Method signature type-checking is by RPG type when using byte arrays or Java primitives, else pointers for Java object parms. Exception handling needs to be handled mostly within Java, with monitor blocks RPG. We compensated for limited RPG exception handling by using the Error object returned from Salesforce.

18 Testing & Debugging... Before After Java class variables are pointers to Object types O types act like * types

19 Testing & Debugging... IMPORTANT: Java Virtual Machine Runtime Only one instance of the JVM may be run per job, including interactive When a new jar is pushed or before a recompile, we found it prudent to signoff and make sure we had a pristine JVM instance before beginning a new debug session. Otherwise, we started to get 'phantom' error conditions that were compounded by the JVM state from a previous CALL but really did not have anything to do with our code. The JVM will be terminated automatically (and the memory reclaimed) at the end of a job. A catastrophic termination of the JVM will require the job to be restarted, e.g., System.exit(1). The JVM cannot be restarted in the same job. The runtime environment for the JVM must be supplied to a batch job, just as any other JOBD parms, including classpath and std/sterr IO capture, if any.

20 Testing & Debugging... Java Exceptions are all monitored using one message (RNX0301). The first 100 bytes of the replacement text contains the Java exception's tostring() content. However, more of the exception can be accessed from the job log's 2 nd level messaging during debug...

21 Java Exceptions... Uninitiated Java Class Instance: parmobj

22 Message Info...

23 2 nd Level Information...

24 Shift+F11 console output... Java output: System.out/err.println( ) Java log output: Logger.log()

25 Wrap-up Use Java classes directly in RPGLE Use RDi/RDP to get Prototypes correct Debug Java in Java debugger, RPGLE in system debugger Let Java and RPG do what they do best do not try to turn RPG into Java Questions?