To configure your workflow system development environment:
For information about the current, supported version of the JDK for your platform, see the IBM FileNet P8 system requirements web page.
Install the supported version of the JDK on your development system and add the installation path to your PATH variable.
Required Files for Application Development
The following JAR files in the Process Engine Developer Files samples set are required for any Process application development:
Contains the Process Java API runtime classes.
Contains Content Platform Engine resource files (such as exception and string files).
Contains third-party classes that are used by Content Platform Engine.
These JAR files are supplied in the Process Engine Developer Files samples set, but are used only for specific types of development:
Contains the Java Step Processor UI Toolkit classes. This toolkit contains a panel set of Swing-based interfaces, support classes, JavaBeans, and related information classes. The toolkit classes are used to provide user interface controls for the Java Step Processor samples. For more information, see Java Step Processor UI Toolkit Overview.
(For FileNet Image Manager only.) Contains Process Java API runtime and related classes.
Process Java API Samples
The Process Java API sample files that are supplied in the Process Engine Developer Files samples set include the following items:
Java API files that you can use to create, start, and complete a workflow, as well as displaying and saving log information. MainSample.java is a simple workflow processing application that demonstrates how the API sample classes are related. These files are in the Directory Files\samples\api directory.
Step Processor and Launch Step Processor sample applications, along with the image files needed for the default user interface. These files are in the Directory Files\samples\vwpanel directory.
A Java class for viewing or removing entries from the Java Remote Method Invocation registry. These files are in the Directory Files\samples\utils directory.
For more information about the Process Java API samples, see Process API Samples Overview.
Additional JAR files for Process application development are located on either the Application Engine, or Content Platform Engine host:
Contains the Content Engine Java API runtime classes. This JAR file is located on the Application Engine host in filenet_installation_directory\WorkPlace\download.
The workflow system uses the Content Engine Java API for LDAP directory access and authentication. Refer to the Getting Started information for the Content Engine API for JAR file information. Alternatively, you can install the Content Engine Java API.
The workflow system uses the Java Authentication and Authorization (JAAS) login context for establishing sessions. The default JAAS login context is FileNetP8WSI for HTTP transport and FileNet P8, FileNetP8Engine for EJB transport.
For more information, see Authentication and JAAS.
If you use the Web Services transport rather than the EJB transport, change the FileNetP8 stanza to reference the FileNet WS-I login module:
FileNetP8
{
com.filenet.api.util.WSILoginModule required;
};
For an example of a login module that is used by the workflow system, see Component Authentication Example.
java.security.AccessControlException: access denied (java.lang.RuntimePermission modifyThreadGroup)
at java.security.AccessControlContext.checkPermission(Unknown Source)
at java.security.AccessController.checkPermission(Unknown Source)
at java.lang.SecurityManager.checkPermission(Unknown Source)
. . .
Use any one of the following workarounds to correct this behavior:
In addition to the Process Engine developer files, the Web Application Toolkit provides an extensible framework with reusable modules for building event-driven, Java Server Pages-based Web applications for the FileNet P8 Platform. Building HTML Step Processors is one example of how you might use this toolkit. The Web Application Toolkit is installed as part of the Application Engine installation. A number of FileNet applications (including Workplace itself) were built using this framework.
For additional information see Web Application Toolkit. See also the Web Application Toolkit Sample located in the FileNet P8 Platform Developer Samples section at IBM FileNet FileNet P8 Platform publication library.
If your application server uses the IBM JVM, for optimal performance, make the following changes to the application server startup file, according to your platform:
Weblogic
JAVA_OPTIONS=$JAVA_OPTIONS -Dprogram.name=$PROGNAME -Dfilenet.pe.peorb.pool.min=2 -Dfilenet.pe.peorb.pool.max=5
set JAVA_OPTIONS=%JAVA_OPTIONS% -Dprogram.name=%PROGNAME% -Dfilenet.pe.peorb.pool.min=2 -Dfilenet.pe.peorb.pool.max=5
JBoss
JAVA_OPTS=$JAVA_OPTS -Dprogram.name=$PROGNAME-Dfilenet.pe.peorb.pool.min=2 -Dfilenet.pe.peorb.pool.max=5
set JAVA_OPTS=%JAVA_OPTS% -Dprogram.name=%PROGNAME% -Dfilenet.pe.peorb.pool.min=2 -Dfilenet.pe.peorb.pool.max=5
The US Federal Information Processing Standard 140-2 (FIPS 140-2) is a cryptographic function validation program. It defines security standards for cryptographic modules that are used in software. The workflow system uses the FIPS 140-2 approved cryptographic provider IBMJCEFIPS (certificate 376) for cryptography.
FIPS 140-2 mode is enabled by default when the Content Platform Engine server and other workflow system components, such as Component Integrator, are installed. However, the following scenarios require that you manually enable FIPS:
Enabling FIPS 140-2 Mode
To manually enable FIPS 140-2 mode, you must specify as the first provider, a FIPS-certified security provider. For clients that use an IBM JRE, you must use IBM Java Secure Sockets Extension (JSSE). The IBM JSSE contains the ibmjcefips.jar file. Add the following to the jre\lib\java.security file:
security.provider.1=com.ibm.crypto.fips.provider.IBMJCEFIPS
ssl.SocketFactory.provider=com.ibm.jsse2.SSLSocketFactoryImpl
ssl.ServerSocketFactory.provider= com.ibm.jsse2.SSLServerSocketFactoryImpl
For more information, see IBMJSSE2 Provider Reference Guide.