Using the MetaFilesRemover Utility
Is the file manager space growing significantly in your Agile PLM deployment? Are you using AutoVue? If so, this blog may be just what you’ve been looking for!
In addition to storing attachments, the Agile PLM file manager also stores AutoVue cache files, also called metafiles or streaming files. Over time, these cache files can build up and occupy a significant amount of disk space. The good news is that these can be removed without affecting the system allowing you to recover that lost disk space.
Is your Agile PLM environment starting to slow down or are you looking to monitor its performance? There are a number of tools out there to help with this, including the Java Console that comes with the Java Development Kit (JDK). This blog will provide basic instructions on how to enable the Agile PLM server deployment for remote monitoring. Once you have this basic knowledge, you will be capable of finding additional resources online to add features like authentication for the monitoring connection.
Need to move content between your Agile PLM environments? If only configuration needs to be moved, then Agile Configuration Propogation (ACP) tool should be the tool of choice. For configuration and data, Agile PLM provides scripts to import and export dump files through a regular imp/exp commands and the data pump. This blog will provide information on using the agile9imp command to import the Agile PLM database so that it can be imported into another environment or archived as a backup.
There are a couple of ways to move content between your Agile PLM environments. If only configuration needs to be moved, then Agile Configuration Propogation (ACP) tool should be the tool of choice. For configuration and data, Agile PLM provides two scripts to create dump file through a regular export and the data pump. This blog will provide information on using the export command to export the Agile PLM database so that it can be imported into another environment or archived as a backup.
In my last blog article, Process Extension Development – Demoting a Change Order, I offered some source code that demotes a change order when one of the affected items on the change has an obsolete item on its BOM. There were a few follow up posts in the LinkedIn discussion about how to create a process extension, also called a PX. This blog will help outline the steps to package the source code, create the ICustomAction and configure Agile PLM to trigger the process extension (PX) on the submitted workflow step.
Demoting a change with an obsolete part on the BOM of an affected item
I often go through the Agile PLM SDK group in LinkedIn. On a recent visit, someone was having an issue with obsolete parts showing on the BOM of an item on a change order. To be clear, the issue is not that parts on the change were obsolete, it is that parts on the BOM of the affected items of a change were obsolete. A process extension (PX) was proposed by another group member to remedy this business rule. This blog illustrates the implementation of that process extension.