JVM Peer Gone in WebLogic T3 connection

So I have this exception when connecting to a FileNet P8 API from my Linux Machine:

com.filenet.api.exception.EngineRuntimeException: FNRCE0040E: E_NOT_AUTHENTICATED: The user is not authenticated. Message was: java.net.ConnectException: t3://1.2.3.4:9210: Bootstrap to 1.2.3.4/1.2.3.4:9210 failed. It is likely that the remote side declared peer gone on this JVM  at com.filenet.apiimpl.core.UserPasswordToken.getSubject(UserPasswordToken.java:121)
 at com.filenet.api.util.UserContext.createSubject(UserContext.java:288)

This happens when my application is connecting to FileNet P8 Content Engine deployed into a WebLogic Cluster and not into a single node (Well it might happen with a single node…). The connection point used by the application is a single node address.

The solution for this error message?

Just add to the host files of the client machine the name and ip address of each weblogic cluster physical machine.

P8 Process Engine Process Administrator Date Format

For those that are using the P8 FileNet products, specifically the Process Engine Process Administrator tool, may have the need to do a search based in dates values, like, for example, if F_StartTime is greater than yesterday.

The date format for using as the parameter is the following: MM/DD/YYYY HH:MM AM/PM

For example: 06/20/2012 15:00 pm or 06/20/2012 08:00 am

The Process Administrator then inserts the date value with the UNIX timestamp format on the search condition.

An online tool as: http://www.onlineconversion.com/unix_time.htm can be used to convert the values back and forth between formats.

P8 5.0 on CentOS/Redhat install

If by any chance, during the setup launching this happens:

Preparing to install…
Extracting the JRE from the installer archive…
Unpacking the JRE…
Extracting the installation resources from the installer archive…
Configuring the installer for this system’s environment…

Launching installer…

Graphical installers are not supported by the VM. The console mode will be used instead…

Preparing CONSOLE Mode Installation…

=======================================================

Installer User Interface Mode Not Supported

The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The valid UI modes identifiers are GUI, Console, and Silent.

=======================================================

Just install de compatibility libstd to your system:

yum install compat-libstdc++-33.i386