Description:
New Procedures developed using TIBCO iProcess Technology Plug-ins v11.3.0, do not require the steps mentioned in this Solution. However, when an EAI Java step is processed using TIBCO iProcess Technology Plug-ins v11.3.0 or higher, for procedures developed with previous versions of the technology plugins, the eaijava logs indicate that a step needs to be upgraded to include a cache key in order to improve performance.
Symptoms:
The following warning messages may be seen when using TIBCO iProcess Technology plugins v11.3.0: 

2013-07-19 07:10:11,468 [WARN ] SWParser - Please upgrade step to include a cache key in order to improve performance
2013-07-19 07:10:11,472 [WARN ] SWXMLHandler - Please upgrade step to include a cache key in order to improve performance
2013-07-19 07:10:11,472 [WARN ] SWXSLTHandlerGeneric - Please upgrade step to include a cache key in order to improve performance
2013-07-19 07:10:11,476 [WARN ] SWBWTransport - Please upgrade step to include a cache key in order to improve performance

From iProcess Technology plugins v11.3.1, these log statements have been changed from WARN to DEBUG level (as per an internal enhancement JIRA Id - IPTP-653).
Cause:
This performance improvement was first introduced via MR 43134 in iProcess Technology Plugins v11.2.0 HF 3. Every step of the procedure was appended with the element CACHE_KEY. Any new procedure developed using iProcess Technology Plugins v11.3.0 or higher, will include this CACHE_KEY element. A check was introduced if a step does not include this cache key.These messages will be written to the eaijava logs. All procedures developed using versions prior to Technology Plugins v11.3.0 will meet this criteria.

You may choose to ignore these log messages. In case you opt to address them, you can upgrade the step to add the CACHE_KEY element in any of the following process modeling tools. 

1). Using TIBCO iProcess Modeler.

    - Open each procedure where a EAI BW step is being used.
    - Go into each BW step, to the component editor where data mapping is being done. 
    - Save the steps.
    - Release the new procedure version via the modeller.  

2). Using TIBCO Business Studio. 

This option should be used only when TIBCO Business Studio iProcess Add-in v3.5 or higher is being used. The run-time performance improvement was introduced in TIBCO Business Studio iProcess Add-in 3.5 via SIA-42. This enhancement id is not listed in the release notes.

 - Configure the iProcess destination environment to "11.3+" (in Window->Preferences->Destination Environments).

 - Export iProcess XPDL or Deploy to iProcess Server, as per your preferred deployment method.

After upgrading to TIBCO iProcess Technology Plug-ins v11.3.0, the procedures can be modified to improve performance.