Use of file system and global directory

Schema and WSDL files

The mxe.int.dynamicwsdlandschema property is no longer functional and will be removed during the upgrade process.

Temporary files

Although these processes use the file system, they do not require a common folder directory that supports all Control Desk servers.

File-based error management

File-based error management previously supported an option to download an extract file that had already been created and downloaded. This option is no longer available. If the extract has not been deleted from Message Reprocessing application, then the download file can be re-created and re-downloaded as needed. If necessary, save old versions of extract files as needed.

File-based end points (XML and flat)

For file-based (flat and XML) endpoints, processing can vary based on how the end point parameters are configured and how the channels (publish or invocation) are being initiated. Processing will use the file location specified on the end point parameter to write the file, but when not populated, it will use a default directory under the configured global directory (mxe.int.globaldir). The server that is processing the message must have access to the directory the file is being created in.

For a publish channel message, the server processing the message is the server the outbound JMS CRON task is running on. Depending upon your implementation configuration, that CRON task could run on different servers at different times.

For invocation channels that are configured with a file-based end point, the processing occurs on the server where the invocation was initiated.

You can use a common global directory to ensure that all files created in a single location. Without a common global directory, you may get files created on multiple servers.

Web service deployment to the application server container

Deployment of web services to the application server container involves the creation of a .dar file that is saved in a folder named jaxws under the global directory. If the global directory is not configured, it will be located under the default directory of the application servers where you performed the deployment step.

XSL files for customization

If you use XSL for integration customization and you deploy those files using the file system rather than the Maximo EAR file, the files must be located in a common folder where all servers that are processing channels and services can access those files.

XML and flat file import CRON tasks

The XML and flat file import CRON tasks require access to the location of the files to be imported. This location is defined in the SOURCEDIRECTORY parameter. If your CRON tasks are not configured to run on a specific server at all times, then using common folder directory is appropriate.

MXCOGNOS end point

The value of the MXCOGNOS end point parameter, proj_base_dir, is required and used to identify the directory location of the file to generate.

Message reprocessing - queue-based error messages

Queue-based error messages are now saved in the database instead of on the file system. Functionally, the management of error messages remains the same. However, the format of the message has changed. The External Record (known as <ER>) and the Internal Record (known as the <IR>) sections of an error message are viewed separately in the Message Reprocessing application. An administrator still has the capability to correct the <ER> data and reprocess the message.

Message tracking - messages persisted

You can configure Message Tracking to persist the message to the file system in addition to the metadata that tracks the flow of a message into and out of an integration queue.

In Control Desk version 7.6, when this option is configured, the message is stored in the database table along with the related metadata of the transaction.

Message upgrade - message reprocessing and message tracking

When you install Control Desk version 7.6, you upgrade all message reprocessing and message tracking messages that are currently on the file system. The upgrade process moves data in the files into the appropriate row in the database tables that support message reprocessing and message tracking. The upgrade leaves files on the file system, but integration processing no longer uses those files for any processing.

If you maintain a large volume of error messages on the file system, you can clean up and /removing messages that you have no intention of re-processing. For cleaning up old error messages we recommend that you do this using the Message Reprocessing application prior to performing your upgrade.

You are prompted to upgrade messages when you install Control Desk version 7.6. The Control Desk version 7.6 administrative workstation must have access to the global directory during the upgrade. If you choose to not upgrade messages during the installation process, you can initiate the upgrade manually after the install is complete. You MUST upgrade messages related to Message Reprocessing. If you do not upgrade Message Reprocessing messages, you cannot re-process or delete those messages using the Message Reprocessing application.

The volume of Message Tracking messages moved to the database could be significant and you should consider this as part of your database sizing configuration. If you upgrade messages manually, after you install Control Desk version 7.6, you have the option to not upgrade Message Tracking messages. For information about the Message Tracking Archiving utility, see the Maximo wiki.