Evaluating Your Architecture

Changing the architecture may be mandatory depending on the version of the applications you are using. If you are going to change your architecture:

Determine when to make this change.
Account for the technical work involved.
Communicate the architecture change to your organization and create consensus to minimize disruptions.
Evaluate whether you need to change the following architectures:
- Hardware Platform The hardware change should take place prior to the upgrade or after the upgrade finishes. You may need to change the hardware prior to the upgrade for the following reasons: new data size requirements, CPU capacity, platform age (generally lasts about 3 to 5 years), changing the complete hardware stack to a different technology. Review the Tested Configurations document to determine which platforms support which versions of P6 EPPM, related tools, hardware drivers, and required patches.
- Database Size requirements and database features will affect upgrading the database. You should evaluate availability and disaster recovery when determining which database platform to use. Refer to the Tested Configurations document when making upgrade decisions. P6 EPPM will not support all versions of a database.
- Middleware P6 EPPM supports Oracle Fusion Middleware products (for example, WebLogic).
- Unicode You may need to convert your database to Unicode. Most have data in a non-Unicode format. Knowing which option you will use will clarify hardware and project requirements.
- Web Architecture P6 EPPM products are mostly online, with optional desktop clients. This allows flexibility as to where clients can reside, but may require architecture changes. Refer to the Tested Configurations document to determine client hardware and software requirements. Remember to consider whether you need remote development.

Related Topics