Hidden Tools functionality with ESR/ID JNLP files

In this blog, I will explore you with all the features that were covered till now in my blog series (check References) as “XI hidden tools” along with some new features with a very simple approach using ESR/ID jnlp files. All that we need to do is modify jnlp files. To understand jnlp formats, please check official java site.

Highlights

• Enabling debugging/developer mode
• Passing user credentials via JNLP file (new)
• Enabling exporting of mappings as XIM files in PI7.3
• Referring your local workstation jars/PI server(s) jars and even combination of both in JNLP file (new)
• Changing ESR/ID application names with your own custom names (new)
• Enabling XSLT and abap mappings, without changing exchange profile (new)
• Enable/disable single sign-on (new)
• Changing the heap memory for the ESR/ID clients

Procedure

• Open XI/PI main page http://<xihost>:<port>/dir/start/index.jsp (or) http://<xihost>:<port>/rep
• save ESR/IR and ID links as jnlp files to your local workstation
• To edit/view, open jnlp file with any text editor with XML syntax highlighting feature e.g., Editplus
• To enable debugging/developer mode & to pass the user credentials, add the below highlighted tags under “application-desc” node

<application-desc main-class="com.sap.aii.ibrep.gui.appl.ApplicationImpl">

          <argument>webstart</argument>

          <argument>-u</argument>

          <argument>username</argument>

          <argument>password</argument>

</application-desc>

• To enable export of mappings in PI7.3, we require PI7.1 system “com.sap.xpi.ib.mt.gui.lib.jar “ jar file as I explained in my blog: http://scn.sap.com/community/pi-and-soa-middleware/blog/2013/01/25/trick-to-export-pi73-mappings-as-a-xim-file.This can be accommodated in jnlp file in two ways. a) refer to PI7.1 server path URL b) refer to local copy of PI7.1 in your work station. First comment/remove the existing jar property as below,

<!--<jar href="repository/com.sap.xpi.ib.mt.gui.lib.jar" download="lazy" part="part-109"/> -->

And then add below property for option a)

<jar href="http://<PI7.1hostname>:<PORT>/rep/repository/com.sap.xpi.ib.mt.gui.lib.jar" download="lazy" part="part-109"/>

or below property for option b)

<jar href="file:///C:/<DIR-PATH>/com.sap.xpi.ib.mt.gui.lib.jar" download="lazy" part="part-109"/>

• To enable you own names for ESR/ID swing applications, change

<property name="jnlp.SAPMYNAME" value="Your own Text"/>

e.g,. with <property name="jnlp.SAPMYNAME" value="Welcome to XI"/>

• To enable abap XSLT and abap mappings (without requesting BASIS team to change exchange profile )

<property name="jnlp.com.sap.aii.repository.mapping.additionaltypes" value="R3_ABAP|Abapclass;R3_XSLT|XSL (ABAPEngine)"/>

• To enable/disable single sign-on, use true/false for the below property

<property name="jnlp.com.sap.aii.ib.core.sso.enabled" value="false"/>

• Changing the heap memory for the ESR/ID clients

<j2se version="1.6+" initial-heap-size="32m" max-heap-size="512m"/>

<property name="jnlp.com.sap.aii.ib.client.jnlp.j2se.initialheapsize" value="32m"/>

<property name="jnlp.com.sap.aii.ib.client.jnlp.j2se.maxheapsize" value="512m"/>

• Finally double click the modified jnlp file to be opened with default java web start application or force it with required javaw.exe java version
  

I strongly recommend above procedure only for development XI stacks. Please share your valuable feedback

Thanks,

Praveen Gujjeti

References

http://scn.sap.com/community/pi-and-soa-middleware/blog/2013/01/09/hidden-tools-in-xipi-bat-file-to-launch-esrid-frameworks

http://scn.sap.com/community/pi-and-soa-middleware/blog/2013/03/01/hidden-tools-in-sap-xipi--part-ii

http://scn.sap.com/community/pi-and-soa-middleware/blog/2013/01/25/trick-to-export-pi73-mappings-as-a-xim-file