The correct logical sequence is as follows: Provision Hardware -> Perform Initial Middleware Configuration -> Install Maximo. Following this sequence helps ensure a smooth and successful Maximo installation, providing a stable and well-configured environment for the Maximo application to run efficiently.
When an organization does business in two currencies and has established a second base currency, a valid exchange rate for the currencies must also be defined. Exchange rates are used to convert financial transactions and balances between the two currencies. By defining valid exchange rates, the organization can accurately track and report financial data in both currencies. This is crucial for conducting business, financial planning, and reporting, especially when dealing with international transactions or subsidiaries operating in different countries with different base currencies.
Using two Application Servers (JVMs) on a four-CPU server strikes a balance between maximizing the utilization of available resources and avoiding overloading the server. This configuration can help ensure smooth and optimal performance for the Maximo application without putting excessive strain on the hardware.
This location is the default deployment directory for Maximo, where the built EAR files are generated and stored after the build process. The "IBM" folder represents the installation directory of IBM products, "SMP" represents the product name (IBM SmartCloud Control Desk or IBM Maximo Asset Management), and "maximo" refers to the application itself. After building the EAR files from the command line, you can find them in the specified directory and use them for deployment or further distribution to the target environments.
The Maximo upgrade toolkit is designed to facilitate the upgrade process from one version of Maximo to another, including major version upgrades. Upgrading to Maximo Multitenancy is one of the supported use cases for the Maximo upgrade toolkit.
A possible cause of the error "WebSphere server cannot be reached" during the Maximo installation is that the server running WebSphere does not have a fully-qualified domain name (FQDN). This issue can lead to connectivity problems when the installation workstation tries to communicate with the remote WebSphere server.
The mxe.int.globaldir system property represents the global integration directory in Maximo. By changing this property to the desired directory location, you can specify the target directory where the XML and flat files should be exported when using the publish channel.
Creating appropriate indexes on the columns commonly used in the application's default queries will optimize query performance and avoid full table scans. Indexes allow the database engine to quickly locate and retrieve specific data, significantly improving query response times.
By setting the log level to DEBUG for the maximo.sql.crontask.VMMSYNC package, you will see more detailed information in the Maximo log files related to the SQL statements executed during the VMMSYNC Cron Task. This can help you troubleshoot any issues and better understand why not all users are being created in Maximo from the LDAP directory server. Remember to set the log level back to its original value after troubleshooting to avoid excessive log file growth.
When the default Start Center in Maximo has an excessive number of portlets, it can significantly impact the loading time during login. Each portlet typically loads data from different sources or applications, and having too many of them can result in increased server-side processing and data retrieval. As a result, the user may experience delays while waiting for the Start Center page to load completely. This issue is more common in environments with slower network connections or under heavy server load.
By setting the mxe.doclink.doctypes.defpath property in the System Properties application, you specify the default file path where the attached documents will be stored. This property defines the location on the file system where Maximo will look for and store the attached documents.
To diagnose the poor performance and "out of memory" errors in Maximo Application Servers (JVMs), you can enable verbose garbage collection (GC). Verbose GC logging provides detailed information about the JVM's memory usage, garbage collection cycles, and memory allocation. This data can help identify memory-related issues and fine-tune the JVM's memory settings to prevent crashes and improve performance.
The useAppServerSecurity entry is a configuration parameter in the web.xml file of the Maximo application. Setting it to a value of 1 indicates that the application will utilize the security features provided by the application server (e.g., WebSphere, WebLogic) where Maximo is deployed.
Running version.bat will display the Maximo release version, which confirms the successful installation of Maximo on the server. This information is helpful for verification and documentation purposes and can be used to ensure that the correct version of Maximo is installed and running as expected.
By creating a process revision, you can make the necessary changes to the Workflow process without affecting the existing records that are currently using the process. The original version of the process will remain in use for the existing records, while the revised version will be used for new records going forward.
The function of Application Servers (JVMs) dedicated to run Cron jobs in Maximo is to execute scheduled tasks. In Maximo, Cron tasks are automated processes or jobs that run on a predefined schedule. These tasks can include maintenance activities, data imports or exports, report generation, and other background processes that need to be executed at specific intervals.
