In this section:
The following are upgrade considerations for the installation and configuration of WebFOCUS:
As a workaround, you must perform a manual step after the installation and update the database field by running a simple SQL command.
The following is a list of supported databases that are impacted and the SQL command that needs to be issued:
ALTER TABLE bip_component ALTER COLUMN bip_component_data set data type blob(2G);
ALTER table BIP_COMPONENT ALTER bip_component_data SET DATA type BLOB(214783647);For MS SQL Server 2008/2005:
ALTER TABLE BIP_COMPONENT ALTER COLUMN bip_component_data VARBINARY(MAX);
Note: No changes are required for Oracle, MySQL, PostgreSQL, or MS SQL Server 2012 and higher.
As a result of this enhancement, the bat files and script files have changed. The full installation option installs the enhanced bat and script files to the ...ibi/WebFOCUS8x/ReportCaster/bin directory. The upgrade installation does not update utility bat and script files. If you installed using the upgrade installation, copy the bat files or script files from the ...ibi/WebFOCUS8x/8105_update/ReportCaster/bin directory to the ...ibi/WebFOCUS8x/ReportCaster/bin directory. If you have previously modified the bat files or script files, you must repeat those modifications in the new files.
Note: The user ID that accesses the WebFOCUS Repository database when performing an upgrade must have CREATE TABLE access in order for the WF_PARM_REG table to be created.
This is a change in how Tomcat was configured in version 7.0.33, where maxPostSize was set to zero (maxPostSize=0), indicating that the POST size was unlimited. The reason for this change is that starting with Tomcat version 8.0.24, when maxPostSize is set to 0, it means a limit of zero (0), instead of unlimited. A value of -1 is used for unlimited.
Note: When the maxPostSize parameter is missing, the maximum size for POST requests is 2 MB.
<property name="ConcurrentSessionFilterEnabled" value="false"/> <property name="sessionAuthenticationStrategy" value=" SessionFixationProtectionStrategy "/>
Important: Before installing WebFOCUS Release 8.1 Version 03 and higher, it is strongly recommended that you back up your existing WebFOCUS Release 8.0.x Repository database.
WebFOCUS Release 8.0.x locations and files:
WebFOCUS Release 8.1.x locations and files:
You must create a new file called weblogic.xml in the WEB-INF directory for the WebFOCUS web application. It must contain the following information:
<?xml version="1.0" encoding="UTF-8"?> <wls:weblogic-web-app xmlns:wls="http://xmlns.oracle.com/weblogic/weblogic-web-app" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/ejb-jar_3_0.xsd http://xmlns.oracle.com/weblogic/weblogic-web-app http://xmlns.oracle.com/weblogic/weblogic-web-app/1.4/weblogic-web-app.xsd"> <wls:container-descriptor> <wls:prefer-application-packages> <wls:package-name>org.eclipse.persistence</wls:package-name> </wls:prefer-application-packages> </wls:container-descriptor> </wls:weblogic-web-app>
Once the file is saved, you must recreate the .war file by adding it to webfocus.war. The .war file can be renamed based on your naming convention, and then redeployed.
If a Library report in HTML format was migrated from an earlier release and it contains charts that are rendered through applet tags that reference these files, the charts will no longer display. Contact Customer Support Services to add these files back to your installation.