Agile PLM 9.3.6 Install and Upgrade Checklist

0%

0 of 37 items complete

11 critical items still open - these are the highest-risk gaps.

Download checklist:

Prerequisites

Read the 9.3.6 Release Notes, Installation Guide, Database Installation Guide and Capacity Planning Guide for your platformCRITICALCheck the certification matrix for the exact Oracle Database, WebLogic Server, JDK and OS versions supported by 9.3.6CRITICALSize servers with the Capacity Planning Guide: application server memory, File Manager storage and database growthCreate the Agile database instance with the character set required by the Database Installation Guide (AL32UTF8 for Unicode data)CRITICALCreate the Agile schema using the database scripts shipped with the install media, not by handOpen firewall ports between clients, application server, File Manager, AutoVue and databasePrepare service accounts and an SMTP relay for notificationsTake a full database and file vault backup of the current system before any upgrade stepCRITICAL

Application server install

Install the certified WebLogic Server and JDK before running the Agile installerCRITICALRun the Agile PLM installer and select the application server componentCreate or point to the WebLogic domain, admin server and managed server(s)For clusters, configure managed servers, load balancer or proxy and session affinityDeploy and test the Web Client URLSet up the Java Client download (Java Web Start) and confirm the client JRE levelRecord install directories, ports and passwords in the system runbook

File Manager and AutoVue

Install File Manager and define the file vault location on reliable storageCRITICALSet the File Manager URL in Java Client Admin (Server Settings, Locations) and test upload and downloadGrant the File Manager service account read and write access on the vaultInstall AutoVue for Agile PLM and configure the viewer server connectionOpen a CAD file and an Office file in the viewer from the Web ClientPlan vault backup to run together with the database backup

Upgrade path from earlier 9.3.x

Run averify against the source database and fix the reported data issues before upgradingCRITICALRestore a copy of production to a test database for a dry runRun the Agile Upgrade Tool (AUT) on the copy to bring the schema to 9.3.6CRITICALRun averify again on the upgraded schema and review the logRecompile Process Extensions and event handlers against the new AgileAPI.jar and redeployCRITICALRecompile SDK clients and integrations (ERP, CAD, reporting) against the new jarRe-apply custom configuration not carried by the upgrade (server properties, SSO, certificates)Time the dry run to plan the production downtime window

Post-install and go-live checks

Smoke test the Java Client and Web Client: log in, search, open an item, BOM, change and attachmentCRITICALConfigure and test LDAP or SSO authentication for a sample of usersSend a test workflow notification and confirm email deliveryRebuild or re-enable the full text search index for attachmentsRun a change order through routing, approval and releaseTest every PX, event handler and integration end to endSchedule database, vault and configuration backups and test a restoreCRITICALFreeze the old environment read-only and keep it for the agreed rollback period

Critical items block go-live. Exact supported versions and tool options come from the Oracle documentation for 9.3.6 and the current certification matrix; confirm them before you start.

Planning an Agile 9.3.6 upgrade?

Send your current release, stack versions and list of customisations; we will return a reviewed upgrade sequence and risk list.

Optional. The tool and every export work without this. No spam.

Was this tool useful?

How to use it

Work through the groups in order. Prerequisites and backups come first because almost every failed Agile install traces back to an uncertified database, WebLogic or JDK version, or a database created with the wrong character set. The upgrade group applies only if you are moving from an earlier 9.3.x release; for a fresh install, skip it. Critical items block go-live. Add your own lines for site-specific integrations such as an ERP item and BOM interface or CAD connectors.

Assign an owner per group: DBA, WebLogic admin, PLM admin, integration developer.
Keep a dry-run log with timings to plan the production window.
Store the checklist export with your change request.

What the upgrade tools do

averify is the Agile database verification utility. It checks the schema and data for problems that would break an upgrade or the application, and you run it before and after the upgrade. The Agile Upgrade Tool (AUT) upgrades the database schema and data from a supported earlier release to the target release. Neither tool touches your custom Java code, so Process Extensions, event handlers and SDK clients must be recompiled against the AgileAPI.jar from the new release and redeployed. Always run the full sequence on a restored copy first: averify, AUT, averify, then functional testing.

Where things live after install

System settings are maintained in Java Client Admin: server locations including the File Manager URL, LDAP configuration, notification and SMTP settings, Process Extensions registration and SDK-related settings. The Web Client is what most users run; the Java Client is downloaded through Java Web Start and is where administrators work. File Manager stores attachments in the vault on the file system while metadata sits in the database, which is why both must be backed up together and restored together.

Common mistakes

Upgrading production without a timed dry run. Skipping averify and discovering data issues halfway through AUT. Forgetting to recompile PX jars, which then fail at runtime with confusing errors. Restoring the database without the matching vault, which leaves attachments missing. Leaving the full text search index unbuilt, so attachment search returns nothing. Not testing LDAP with real users from each group before cutover.

Frequently Asked Questions

What is the latest version of Oracle Agile PLM?

Agile PLM 9.3.6 is the current release line of the on-prem product, and Oracle delivers fixes as patches and updates on top of it. Check My Oracle Support for the latest 9.3.6 patch set and the support timeline before planning an upgrade.

Where is the Agile PLM 9.3.6 documentation?

Oracle publishes the Agile PLM 9.3.6 documentation library on its documentation site, including the Installation Guide, Database Installation Guide, Database Upgrade Guide, Capacity Planning Guide, Administrator Guide and SDK Developer Guide. Use the guides for your exact platform and keep a copy with your project files.

What is averify in Agile PLM?

averify is the Agile database verification tool. It scans the Agile schema for data and structural problems and writes a report. Run it before an upgrade to fix issues in the source database, and again after the Agile Upgrade Tool to confirm the upgraded schema is clean.

Do I need to recompile Process Extensions after upgrading Agile?

Yes. Process Extensions, event handlers and SDK clients are compiled against AgileAPI.jar, and the jar changes between releases. Recompile them against the jar from the new release, redeploy to the server and retest each one before go-live.

If you want an on-prem assistant that answers Agile PLM questions about items, BOMs and changes for engineers in plain English, we can add it once your 9.3.6 system is stable.

Talk to an Expert Explore More Free Tools

Related Tools

Developer Tools

Oracle Agile PLM SDK Java Snippet Generator (Items and BOM)

Fill in the Agile URL, user and item number to get compilable Java that logs in with AgileSessionFactory, reads an item description and walks its BOM, plus a Process Extension custom action.

More Oracle tools

See all

Oracle Agile PLM 9.3.6 Installation and Upgrade Checklist