| Agile Product Lifecycle Management Capacity Planning Guide Release 9.3.3 E39278-04 |
|
 Previous |
 Next |
| Agile Product Lifecycle Management Capacity Planning Guide Release 9.3.3 E39278-04 |
|
Previous |
Next |
The Agile Solution has an N-tier, J2EE architecture. These tiers are typically deployed across several servers in a production environment: Application Server, File Manager, Web Server, Database Server, and AutoVue for Agile PLM.
The Agile Application Server is the center of the Agile system, the base for the PLM platform, where all common services and business logic reside for the entire solution. The Agile Application Server runs on industry-leading J2EE application servers. As the System Configuration Overview figure illustrates, all client servers and users connect to the Application Server either directly or indirectly. The application server connects to the components in a persistence layer where product content is stored.
The hardware load balancer brokers client communications without compromising the security of your internal network. Clients communicate through the load balancer with the application server. There are no Agile software components running on the hardware load balancer. They are usually deployed in the Demilitarized Zone (DMZ) where it proxies requests from outside the corporate firewall to the application server in the Safe Zone. A load balancer is necessary if you are installing application servers in a cluster.
A load balancer is required if you are installing application servers in a cluster and/or if you have multiple primary file manager instances. The load balancer is required in order to enforce session persistence for both the clustered application server instances and the redundant file manager instances. For the clustered application server, the load balancer must enforce persistence using a cookie-insert mechanism where the load balancer injects its own cookie into the request. The application passes this cookie to the file manager during file operations so that any request from the file manager to the application server on behalf of the end-user is also persisted properly.
Agile PLM 9.3.3 includes two clients, a Web client and a Java client. The Web client is a thin HTML client that uses firewall-friendly protocols (HTTP/S). The Java client is a Java-based client that can use application server-specific protocols, such as T3 for Oracle WebLogic, to connect to the server. Each client has its own strengths and weaknesses from a functional, architectural, and performance standpoint. This document compares the clients from an architectural and performance standpoint.
The Agile Database Server persists or stores all product content and system settings. Check "Software Requirements" for details about which database software is supported.
The Agile File Manager stores all documents, drawings, and other files within the Agile system. Due to the geographically dispersed nature of the global enterprise, multiple Agile File Managers can be deployed in a distributed configuration for efficient distribution of product content. Agile File Manager is made up of two main components: the file server and the file vault. The file vault represents the file system where the actual files reside. The file vault can be located on the application server or a dedicated storage system.
In an effort to better support the industry standard authentication schemes, Agile PLM 9.3.3 supports Lightweight Directory Access Protocol (LDAP) based authentication. LDAP support enables you to integrate Agile with existing directory servers so user accounts can be managed in one place. Integrating with LDAP is optional. Users can be managed within Agile without a directory server. There are no Agile software components deployed on the Directory Server.
AutoVue for Agile PLM allows users to view and mark up documents and drawings in a supported Web browser. One of the advantages of using AutoVue for Agile PLM is that users can view files stored in Agile without having the native application that created the file installed on their desktop systems. Another advantage of AutoVue for Agile PLM is that it decreases bandwidth requirements and improves response time. Instead of sending large native files to the user, AutoVue for Agile PLM streams a smaller image file to the viewer applet on the client.
The following diagram provides an overall depiction of the Agile PLM System Overview.
The Agile PLM 9.3.3 Software Requirements table shows the operating system and other software supported or required for each Agile component. The application server includes all server components for AIS, SDK, Reports, Import, Export, Agile Content Service, LDAP, and all solutions.
The table below lists the supported application servers.
| Agile Components | Operating Systems | Certified Software |
|---|---|---|
| Database Server
(Standalone or RAC) |
Oracle Solaris 11 and 10 (SPARC64, x86-64)
Oracle Linux 6 and 5 (x86-64) Red Hat Enterprise Linux 6 and 5 (x86-64) SUSE Linux 11 and 10 (x86-64) Microsoft Windows Server 2008 R2 IBM AIX 7.1 and 6.1 (POWER 64-bit) HP-UX 11.31 (Itanium64) Note: Oracle Exadata Certified Virtualization: Oracle VM 3 with Oracle Linux, Oracle Solaris and Microsoft Windows guest Operating Systems listed above Refer to Oracle Support Note "Certified Software on Oracle VM" Oracle Solaris Containers/Zones IBM AIX LPARs Microsoft Hyper-V |
Oracle Database Server 12cR1 (version 12.1.0.1+)
Oracle Database Server 11gR2 (version 11.2.0.3+) Oracle Database Server 11gR1 (version 11.1.0.7+) Note: Enterprise Edition, Standard Edition, Standard Edition One certified Note: Oracle Standard Edition One does not support RAC. Note: It is required to have Oracle Enterprise Edition for the PLM Source DB to use PLM Data Mart. |
| Application Server | Same as Database Server (see above)
Note: Oracle Exalogic Certified |
Oracle WebLogic Server 12c (version 12.1.1)
Note: Only 64-bit JDK 7 certified. Note: WebLogic Suite, WebLogic Server Enterprise Edition, WebLogic Server Standard Edition certified. Note: HP-UX 11.31 on Itanium64 requires WebLogic Server 12.1.2 |
| File Manager (DFM) | Same as Application Server (see above) | Apache Tomcat 7.0.26 bundled (uses JDK bundled with Agile PLM) |
| AutoVue for Agile
PLM (AutoVue Server) (Note: Refer to Oracle AutoVue documentation for latest system requirements.) |
Oracle Enterprise Linux 6 and 5u6+ (64-bit - AutoVue running in 32-bit mode)
Red Hat Enterprise Linux 6 and 5u6+ (64-bit - AutoVue running in 32-bit mode) Microsoft Windows Server 2008 R2 (AutoVue running in 32-bit mode) |
Oracle AutoVue 20.2.2 for Agile PLM |
| Web Server (Proxy) | Oracle Solaris 11 and 10 (SPARC64, x86-64)
Oracle Linux 6 and 5 Red Hat Enterprise Linux 6 and 5 SUSE Linux 11 and 10 |
Apache HTTP Server 2.x
Oracle HTTP Server (OHS) 11g |
| Microsoft Windows Server 2008 R2 | IIS (bundled with Windows)
Oracle HTTP Server (OHS) 11g |
|
| Web Client | Microsoft Windows 8 and 7 (64-bit, 32-bit) | Google Chrome 27 and 18
Microsoft Internet Explorer 11 (see Support Note 1967712.1) and 10 and 9 Mozilla Firefox 21 and 10 Java SE 8 (see Support Note 1967684.1) and 7 |
| Web Client | Oracle Solaris 11 and 10 | Mozilla Firefox 21 and 10
Java SE 7 |
| Web Client | Apple Mac OS 10.8 (Mountain Lion) | Safari 6 and 5
Java SE 8 (see Support Note 1967684.1) and 7 |
| Java Client | Microsoft Windows 8 and 7 (64-bit, 32-bit) | Google Chrome 27 and 18
Microsoft Internet Explorer 11 (see Support Note 1967712.1) and 10 and 9 Mozilla Firefox 21 and 10 Java SE 8 (see Support Note 1967684.1) and 7 |
| Java Client | Oracle Solaris 11 and 10 | Mozilla Firefox 21 and 10
Java SE 7 |
| SDK Client | Microsoft Windows 8 and 7 (64-bit, 32-bit)
Oracle Solaris 11 and 10 |
JDK bundled with Agile PLM |
| SDK Client | Apple Mac OS 10.8 (Mountain Lion) | Java SE 7 |
| EC Services | Same as Application Server (see above) | NA |
| Excel Integration for Import/Export | Microsoft Windows 8 and 7 (64-bit, 32-bit) | Microsoft Excel 2013, 2010, 2007 and 2003 |
| Excel Integration for PG&C | Microsoft Windows 8 and 7 (64-bit, 32-bit) | Microsoft Excel 2013, 2010, 2007 and 2003 |
| Project Integration for PPM | Microsoft Windows 8 and 7 (64-bit, 32-bit) | Microsoft Project 2013 and 2010 |
| Directory Servers (LDAP) | Same as Application Server (see above) | Oracle Internet Directory (OID) 11g (version 11.1.1.5+)
Oracle Virtual Directory (OVD) 11g (version 11.1.1.5+) |
| Directory Servers (LDAP) | Oracle Solaris | Oracle Directory Server Enterprise Edition (p.k.a. Sun Java System Directory Server) |
| Directory Servers (LDAP) | Microsoft Windows Server 2008 R2 | Microsoft Active Directory and ADLDS (bundled) |
| SSO - Oracle Access Manager | Oracle Solaris 11 and 10 (SPARC64, x86-64)
Oracle Linux 6 and 5 Red Hat Enterprise Linux 6 and 5 SuSE Linux 11 and 10 Microsoft Windows Server 2008 R2 |
Oracle Access Manager (OAM) 11gR2 (version 11.1.2.0+), 11g (version 11.1.1.5+) |
| SSO-NTLM (Windows) | Microsoft Windows 8 and 7 (64-bit, 32- bit)
Note: Java SE 7 update 10 or later is required. Note: Not supported with Google Chrome browser. |
Microsoft Windows Server 2008 R2 (IIS Web Server) |
| Enterprise Manager | (same as Application, Database, and Web Server) | Oracle Enterprise Manager 12c (version 12.1.0.1+)Oracle Enterprise Manager 11g (version 11.1.0.1+) |
| User Productivity Kit (UPK) | Microsoft Windows Server 2003 SP2 (32-bit) | Oracle UPK 11.1 |
| ACS | (same as Application Server) | Oracle WebLogic JMS (WLS 12.1.x) |
| Reporting | (same as Application Server) | Oracle BI Publisher 11g (version 11.1.1.6). |
| Scripting | (same as Application Server) | Groovy 1.5.6 |
The table below shows the minimum hardware needed to deploy an Agile PLM 9.3.3 system.
| Agile Server | Hardware Requirements |
|---|---|
| Application Server | Dual CPU Intel Xeon 3 GHz and above OR Dual CPU Ultra Sparc IV+ 1.50 GHz and above (or equivalent)
2 MB L2 cache 4 GB RAM |
| Database Server | Dual CPU Intel Xeon 1.8 GHz OR Dual CPU Ultra Sparc-IIIi 1.1GHz (or equivalent)
512 KB L2 Cache 2 GB RAM (minimum), 4GB (recommended) |
| File Manager and AutoVue for Agile PLM | Dual CPU Intel Xeon OR Dual CPU Ultra Sparc IV+ (or equivalent)
512 KB L2 cache 2 GB RAM |
| Web Server | Intel Xeon 2.8 GHz OR Ultra Sparc III (or equivalent)
512 KB L2 Cache 1 GB RAM |
|
Note: CPU utilization for Agile PLM tends to be relatively high for the application server component and can be relatively light for other components (especially for file manager and database, AutoVue CPU utilization depends heavily on usage including number and size of files being rendered). Therefore, scalability is often focused on the application server component. Also for this reason, the application server is most sensitive to CPU clock speed (the faster the core clockspeed, the better the throughput and scalability). Thus, in general, if you deploy on a slower core you can expect the application to scale somewhat worse and conversely, if you deploy on a faster core you can expect the application to scale somewhat better. |
The following table shows the typical hardware recommendations for production deployments:
| Database Server | at least 8 cores and 8 GB physical memory per instance |
| Application Server | at least 4 cores and 4 GB physical memory for each application server (JVM) instance running Agile PLM |
| File Manager | at least 1 core and 1 GB physical memory for each Agile PLM File Manager instance |
| AutoVue Server | at least 1 core and 1 GB physical memory for each AutoVue Server instance (increase as usage dictates) |
| Web Server | at least 1 core and 1 GB physical memory for each instance (increase as usage dictates) |
|
Note: When running more than one application server (JVM) against a single Agile PLM schema, the application server instances must be clustered. An application server cluster typically has at least two application server instances (JVMs) running the Agile PLM application. Clustering introduces some measurable overhead (estimated at approximately 10%) for things like cache synchronization over JMS, and so on and thus the application does not scale completely linearly as application server instances are added. This is especially noticeable when going from one application server instance (standalone) to two or more application server instances (clustered). |
