Preparing for 6.4
A Technical Perspective
Paul Hamill, Senior Director Application Development
Keith Wenyon, Principal Technical Support Engineer
Agenda
• Technology Changes
• Tips
• Q/A
3
Technology Changes
•
•
•
•
•
•
4
Overview
Web Server
Application Server
BIPublisher Reporting
Mobile App
Database
Technology Changes
Overview -­ Platform
5
Platform
6.3
6.4
Oracle Enterprise Linux
5.x, 6.x
5.x, 6.x
Sun Solaris
10, 11
10, 11
Red Hat
5.x, 6.x
5.x, 6.x
IBM AIX
7.1
7.1
HP Itanium
11iv3
11iv3
Windows
2008/2012
2012
Technology Changes
Overview -­ Technology
6
Technology
6.3
6.4
Web Server
Oracle HTTP Server 11.1.1.7
Oracle HTTP Server 12.1.3
Web Server
Tomcat 7.x
Weblogic 12.1.3
App Server
Weblogic 10.3.6
Weblogic 12.1.3
JDK
1.6
1.7
Database
Oracle 11.2.0.x, 12.1.0.x
Oracle 12.1.0.2+
Reporting
BIPublisher 10g (Embedded)
BIPublisher 11g (External)
FTI/GTI – ETL
ODI 11.1.1.7.0
ODI 12.1.3
FTI/GTI – Analytics
OBIEE 11.1.1.7.1
OBIEE 11.1.1.7.1
Technology Changes
Overview – Web Browser
7
Web Browser
6.3
6.4
Internet Explorer
8, 9, 10
11
FireFox
24esr
31.7esr
Google Chrome
34
42
Safari (Desktop)
6 and 7
7 and 8
Technology Changes
Web Server -­ Tomcat
• Tomcat is Replaced with Weblogic
• Key Differences between Tomcat and Weblogic
Configuration
Tomcat
Weblogic
Threads
maxThreads in server.xml
Unlimited
Session Timeout
session-­‐timeout in web.xml
session-­‐timeout in web.xml
<OTM_INSTALL_DIR>/tomcat/conf/server.xml
<otm_install_dir>/tomcat/conf
<OTM_HOME>/glog/gc3webapp.ear/GC
3.war/WEB-­‐INF/ 8
Technology Changes
Web Server -­ ADF Enhanced UIs
• The Enhanced UIs in 6.4 are built using Oracle ADF
• ADF creates a dependency on a new Oracle Database, the Meta-­data Store (MDS), for storing UI personalization
• This database must be created prior to installing 6.4 • The MDS must be accessible from the OTM web server. • For security reasons the MDS should be located on the web-­
tier itself, not co-­located with the OTM Operational database. 9
Technology Changes
Application Server
•
•
•
•
Removed dependency on config.xml.fresh
SSL for SMTP
Virus Scan Support
New Access Control List (ACL) Entry Points
– Integration
– Power Data -­ Update
– Custom UI Actions
10
Technology Changes
Application Server – config.xml.fresh
• Removed dependency on config.xml.fresh file
• Configuration changes to Weblogic Application Server can now be made in Weblogic Console and changes will be preserved upon restart
• Automatic Configuration Backups are enabled by default
• Custom changes made to the config.xml file are not preserved during OTM upgrades (i.e. 6.4.1)
11
Technology Changes
Application Server – SSL for SMTP
• Provide support for configuring SSL for SMTP. In other words, provided support for secure communication between the app server and the SMTP email server.
• Configured via the following properties
glog.mail.smtp.port=<SMTP port #>
glog.mail.smtp.useSSL=true
glog.mail.smtp.useStartTLS=true
• The “useStartTLS” parameter is an optional parameter required by some SMTP email servers.
12
Technology Changes
Application Server – virus scan support
• Provide the ability to configure an ICAP compliant virus scanner for document upload
• Configured via the following properties
glog.icap.antivirus.host
glog.icap.antivirus.port
glog.icap.antivirus.timeout
• Timeout defines the time limit for document scanning. A document which times out will not be loaded
13
Technology Changes
Application Server – ACLs for Integration
• Created ACL Entry Points for all External Integration points (i.e. WMServlet, IntXMLService, etc.)
• Created “External Integration” ACL Role
• Created “INTEGRATION” User Role
• The “INTEGRATION” User Role needs to be assigned to users used for inbound integration
• Integration Users should not be assigned any additional Roles and conversely End Users should not be assigned the Integration Role
14
Technology Changes
Application Server – ACLs for Power Data Update
• Previously, updating Power Data interfaces could only be secured with the single “Power Data – Update” ACL
• Now there are ACL Entry Points corresponding to each Power Data interface
• Power Data Update Entry Points have the following format:
glog.webserver.powerdata.GenericSaveServlet.powerdata.<table_name>
• All of the new individual related Power Data entry points have been grouped into the already existing “Power Data – Update” access control list for backward capability. 15
Technology Changes
Application Server – ACLs for Custom UI Actions
• Previously, securing Custom Actions required manual entry of data in the ACL database tables
• Now, Custom Actions can be secured with an ACL Entry Point
• New “Secure Action” action on the Action Manager generates the ACL Entry Point
• The new Custom Action Entry Point created has the format: glog.webserver.util.QueryResponseServlet.action.<custom_action_gid>
16
Technology Changes
BIPublisher Reporting
• Embedded BIPublisher 10g is removed in 6.4
• In order to run BIPublisher Reports customers must install BIPublisher 11g
• BIPublisher 11g is included with OBIEE Install
• Custom Reports will need to be migrated from 10g to 11g
17
Technology Changes
BIPublisher Reporting
•
Oracle Transportation Management includes a restricteduse of Oracle Business Intelligence Publisher to publish and/or view
– Shipped Oracle Business Intelligence Publisher reports. Layout changes are allowed.
– Shipped or newly created Oracle Business Intelligence Publisher reports that are modified to access data from the existing Oracle Transportation Management Application schema that has not been customized.
•
Full use of Business Intelligence Publisher is required if any shipped, modified or newly created Oracle Business Intelligence Publisher report:
– Accesses data from a nonOTM Application data source, or
– Accesses data from a new schema within the Oracle Transportation Management Application that is not shipped by Oracle, or
– Accesses data from a modified Oracle Transportation Management Application schema (e.g., by adding columns to an existing table)
18
Technology Changes
BIPublisher Reporting
• Report System Defines the BIPublisher server
• Report System can use property macros:
$glog.bip.externalFarm.host
$glog.bip.externalFarm.port
$glog.bip.externalFarm.user
$glog.bip.externalFarm.password
19
Technology Changes
BIPublisher Reporting
• 11g Reports are created in BIPublisher
with a SQL based Data Model and a WYSIWIG Report Designer
• Reports run with proper VPD Context when run from OTM
• Report distribution/storage is still defined within OTM
20
Technology Changes
BIPublisher Reporting
• The following Public Reports have been migrated to 11g
Report
Report
AES Filing
Domestic Packing List
Bill of Lading
Invoice
Customs Commercial Invoice
Pickup Summary
Demurrage Financial
21
Technology Changes
Mobile App
• OTM Mobile Web site is disabled in 6.4
• New Mobile App available in App Stores for free download with 6.4.1
22
Technology Changes
Database
• Upgrading to Database 12c is mandatory for 6.4
• Database 12c includes optional licensable component for in-­memory optimization
23
Technology Changes
Database
24
Technology Changes
Database 25
Technology Changes
Database 26
Technology Changes
Database 27
Technology Changes
Database • In-­Memory is enabled by Initialization Parameters (license required)
• In-­Memory Size is part of the SGA
• Enabled on Tablespace, Table, Sub(Partition), or Materialized View
• Ex. ALTER TABLE SHIPMENT_STATUS INMEMORY;;
28
Technology Changes
Database • Possible candidates: Refnum, Remark, Status
• For more details…
http://www.oracle.com/us/products/database/options/database-­in-­
memory/overview/index.html
29
Database Structure Changes
Summary of GLOGOWNER Changes 6.3 – 6.4
Element
Deleted
Changes
Additions
Table
6 (-­‐86%)
119 (63%)
138 (-­‐16%)
Column
24 (-­‐69%)
69 (25%)
765 (-­‐46%)
Total
30 (-­‐75%)
188 (47%)
903 (-­‐43%)
Note: Number in parentheses is a relative comparison to 6.2 -­ 6.3
30
Tips – Before Installing 6.4.x
•
Review the following MOS note for the latest information on the installation of OTM 6.4.x.
Oracle Transportation Management and Global Trade Management Release 6.4.x Installation Notes and Updates (Doc ID 2006049.1)
There are a number of known issues mentioned in the Installation/Upgrade section of the note that may require some additional patches be installed for Weblogic, OBIEE, Database and for FTI. 31
Tips – Before Installing 6.4.x
•
•
•
Weblogic must be installed for Web Server and/or Application Server installations.
We recommend Weblogic patch 17968606 be installed as mentioned in MOS note 2006049.1. After OHS is installed you will need to run “rcu”, Repository Creation Utility. T his step is required to support ADF features 6.4.x. Note: When the RCU process is run additional tablespaces will be created. T hese tablespaces
should not take up significant disk space unless you have a large number of users customizing the ADF screens.
•
Also during this step a number of users will be created. Be sure and keep track of of these users and their passwords. T he following users and passwords will be needed for the OTM install.
*_mds, *_iau_append, *_iau_viewer, *_opss, *_stb
(*) could vary depending on the prefix you use.
32
Tips – Before Installing 6.4.x
33
Tips – Before Installing 6.4.x
•
Be sure you know the following information before you start the OTM install.
BEA Home
BEA Server Path
Port and protocol you want to use for the Web – You can use http or https protocol and ports
OTM DB server, port, SID, SERVICE and Oracle Client Home
MDS DB Server, port and Service Name – When running the install be sure and change the MDS prefix to the value you used when you ran “rcu” and update the MDS users with the correct prefix too.
34
Tips – Installing 6.4.x
•
35
URL Prefix should not be populated unless the instance is behind a reverse proxy. This question is pre-­populated with a default value of “/” when running the GUI installer. Be sure and remove the “/” before continuing to the next question.
Tips – Installing 6.4.x
•
36
During the install you will be prompted for the Weblogic Weblogic Account Password and the Web Domain Weblogic User Password. Be sure and use the same password for both questions as these are the same user. Additional changes will be made in 6.4.1 to remove these redundant questions from the installer. Tips – Installing 6.4.x
•
37
You will also be prompted for the Web-­to-­App user password. This is for the OTMAppUser, which is used for verifying Web-­to-­App communication. This needs to be set the same value on all Web and App Servers in the same OTM instance.
Tips – Installing 6.4.x
•
38
During the installation python scripts are used to configure the OTM Web and OHS instance. T his step can take several minutes to complete. T he < OTM Home >/logs/web_python_exec.log will be created during the process and may be requested when investigating installation related issues.
Tips – Startup Scripts and Logs
•
•
39
The startup scripts for the OTM Web and App are now in the < OTM Home >/install/appserver and < OTM Home >/install/webserver
directories.
Console logs for the Web and App servers are now in the < OTM Home >/logs/appserver and < OTM Home >/logs/webserver
directories.
Tips -­ General
• Purge data prior to migration
• Clone and perform migration testing on a Test first and then Production Database
• If errors are encountered…restore DB, fix errors, and re-­run from the beginning
• Test the migration until it runs clean
40
Tips -­ General
• Review Custom SQL, PL/SQL, Reports which may be impacted by Database Structure changes
• Regression test key functional scenarios on migrated environment
• Performance testing is strongly encouraged
41
Q/A
42