Topic
IC4NOTICE: developerWorks Community will be offline May 29-30, 2015 while we upgrade to the latest version of IBM Connections. For more information, read our upgrade FAQ.
4 replies Latest Post - ‏2011-11-10T21:46:36Z by p8learning
p8learning
p8learning
7 Posts
ACCEPTED ANSWER

Pinned topic Custom Java Application Migration from FileNet P8 4.5 to 4.5.1

‏2011-11-08T21:38:21Z |
Hi Friends,

We are planning to upgrade FileNet P8 from 4.5 to 4.5.1. We have lots of custom java applications on 4.5. Whe we move 4.5.1 I heard that there is a new set of jar files to use to develop applications. The following tech note from the 4.5.1 release note:

[b]Systinet™ is no longer supported[/b]
Systinet has been replaced by a custom Web services serialization framework. As a result, the following
constants have been deprecated:
• ConfigurationParameter.WSI_SYSTINET_HOME
• ConfigurationParameter.WSI_SYSTINET_HOME_AS_INT
• ConfigurationParameter.WSI_SYSTINET_HOME_AS_STRING
• ConfigurationParameter.WSI_SYSTINET_LOGGING_LEVEL
• ConfigurationParameter.WSI_SYSTINET_LOGGING_LEVEL_AS_INT
• ConfigurationParameter.WSI_SYSTINET_LOGGING_LEVEL_AS_STRING
For more information, see IBM FileNet P8 Documentation > Developer Help > Content Engine Development >
Java API Reference > ConfigurationParameter Class.
In addition, changes have been made to the list of .jar files that are required for a client that uses the
CEWS transport:
Required: stax-api.jar, xlxpScanner.jar, xlxpScannerUtils.jar, Jace.jar, log4j.jar
No longer required: wasp.jar, activation.jar

Since we are using CEWS transport how this will affect our existing applications? Do you have any idea how to migrate the existing code to new 4.5.1 env? I will appreciate all your inputs. Thanks in advance.
Updated on 2011-11-10T21:46:36Z at 2011-11-10T21:46:36Z by p8learning
  • SystemAdmin
    SystemAdmin
    199 Posts
    ACCEPTED ANSWER

    Re: Custom Java Application Migration from FileNet P8 4.5 to 4.5.1

    ‏2011-11-08T22:14:51Z  in response to p8learning
    Your code will almost certainly NOT have to change. It's just configuration of things like JARs on the classpath. (If you do any configuration from your code instead of from the Java command line, you may need to look at that, but that is probably OK even if parts of it are no longer needed.)
  • p8learning
    p8learning
    7 Posts
    ACCEPTED ANSWER

    Re: Custom Java Application Migration from FileNet P8 4.5 to 4.5.1

    ‏2011-11-09T20:19:46Z  in response to p8learning
    Thanks for the reply. So that means I need to supply the new jar files (stax-api.jar, xlxpScanner.jar, xlxpScannerUtils.jar, Jace.jar, log4j.jar) and remove the ones not required (wasp.jar, activation.jar) from each custom application. Nothing else changes??
    • SystemAdmin
      SystemAdmin
      199 Posts
      ACCEPTED ANSWER

      Re: Custom Java Application Migration from FileNet P8 4.5 to 4.5.1

      ‏2011-11-09T22:17:49Z  in response to p8learning
      Correct as far as JAR files are concerned. You may also need to change some environmental things, like the CE connection URL, but you shouldn't need any code changes.
  • p8learning
    p8learning
    7 Posts
    ACCEPTED ANSWER

    Re: Custom Java Application Migration from FileNet P8 4.5 to 4.5.1

    ‏2011-11-10T21:46:36Z  in response to p8learning
    Thanks. I will post here if there is any issues/concerns after our migration.