Date: Thu, 28 Mar 2024 07:01:41 -0500 (CDT) Message-ID: <201626944.34487.1711627301645@olcflv1.outside.agileassets.com> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_34486_1330544120.1711627301642" ------=_Part_34486_1330544120.1711627301642 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
This section provides detailed, technical information on configu= ration of the AgileAssets Enterprise Asset Management Suite. I= t is intended for advanced users of the application, such as personnel who = configure the application for use. The following chart gives additional inf= ormation on the capabilities needed for administering and updating the Agil= eAssets System.
For Software | For Database | |
---|---|---|
Administrator Qualifications | The software is composed of a web archive (WAR) = file. Must be able to deploy and un-deploy a WAR file. | Must be a qualified Oracle DBA to support the Or= acle database and the Oracle schema for the AgileAssets application. |
System Components | The WAR file contains JavaScript files and Java = classes along with other required configuration files, packaged in a standa= rd format for Web servers. | The system is retained in a single Oracle schema= . The software links to this Oracle schema through the configuration file w= eb.xml existing in the WAR file. |
System Upgrades | A WAR file will be provided. To upgrade, un-depl= oy the current application from the web server and deploy the provided WAR = file. | A text file containing a series of SQL statement= s will be provided. To upgrade, run the file against the Oracle schema. |
Troubleshooting | Contact your AgileAssets project manager or tech= nical support. | Provide the log file for the SQL that was run, a= nd contact your AgileAssets project manager or technical support. |