Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Current »

The following functions can be enabled on the self service portal on a per-request basis. These functions are available for NON-PROD environments only. If you would like the below functionality enabled, please open a case to request access.

  • Stop Database Services (supported for DB2 only)
    This task will stop DB2 and its services on the target asset. This task does not stop the application servers prior to stopping DB2. This task takes no parameters and completes the following actions:
    db2stop force
    ipclean -a

  • Start Database Services (supported for DB2 only)
    This task will start up DB2 services on the target asset. This task does not start the application servers after starting the database services. This task takes no parameters and completes the following action:
    db2start

  • Stop Environment (supported for DB2 only)
    This task will stop the services that support the running of the application on the target asset. This includes both DB2 database and application server JVMs. This task takes no parameters.

  • Start Environment (supported for DB2 only)
    This task will start the services that support the running of the application. This includes first starting DB2 database, then starting the application server JVMs. This task takes no parameters.

  • Backup database to Object Storage (supported for DB2 only)
    This function requires the customer to have an IBM Cloud account with Cloud Object Storage (COS). COS is not included with the Maximo SaaS Flex subscription and must be obtained separately.
    This task exports an existing Maximo database and copies it to cloud object storage.
    It will stop the application server JVM’s and will then take an export of the DB2 database. All files in the export will be zipped, and then the zip file uploaded to the provided IBM Cloud object storage bucket in the path provided. This task will perform the following actions.
    1. Stop application server JVMs
    2. Complete a database export (db2look for schema capture, db2move to capture data)
    3. Zip the file and upload to customer owned IBM Cloud Object Storage in the provided bucket and path and filename
    This task requires that the customer supply an Access Key ID and Secret Access Key to the self service portal. These secrets are updated on the SSP customer object. This task requires supplying a bucket name which must conform to internet hostname standards, as well as a full path where the file should be stored under the bucket. This name should include both the path and file name in Unix directory separator formats.

  • Refresh Database from Object Storage (supported for DB2 only)
    This function requires the customer to have an IBM Cloud account with Cloud Object Storage (COS). COS is not included with the Maximo SaaS Flex subscription and must be obtained separately.
    This task imports a database export, including all schema objects and database content, replacing the existing Maximo database in the process. A zip file is downloaded from cloud object storage.
    It will stop the application server JVM’s and will then take an export of the DB2 database. All files in the export will be zipped, and then the zip file uploaded to the supplied IBM Cloud object storage bucket in the path provided. This task will perform the following actions.
    1. Stop application server JVMs
    2. Download the database export zip file from IBM cloud object storage
    3. Drop the existing Maximo database
    4. Import the database supplied in the zip file (db2look for schema capture, db2move to capture data)
    5. Update all Maximo sequences.
    6. Restart application server JVMs
    This task requires that the customer supply an Access Key ID and Secret Access Key to the self service portal. These secrets are updated on the SSP customer object. This task requires supplying a bucket name which must conform to internet hostname standards, as well as a full path where the file is stored under the bucket. This name should include both the path and file name in Unix directory separator formats.

  • Deploy EAR
    Issues an EAR build command followed by EAR deploy to Maximo.

  • Apply Database Updates (supported on DB2 only)
    The purpose of this task is to allow the customer to apply intermediary updates to the Maximo application that include updated icons, java classes, and database update content. An updatedb is run as part of this job and if supplied, a set of update tasks supplied in the form of updatedb scripts. The updates are supplied as a zip file either as an attachment to the task, or from IBM Cloud Object Storage. This task completes the following actions:
    1. Stop the application server JVM(s)
    2. Download the supplied zip file, and unzip to the Maximo tree.
    3. Runs updatedb
    4. Runs supplied runscript file for further database customization
    5. Builds the Maximo EAR
    6. Deploys Maximo EAR for single server environment.
    In order to apply custom updates to the database that are required for the application updates, this task will both run an updatedb for application updates, as well as a set of runscript files for any customization required.
    The zip file tree top level directory should be “Maximo”, and conform to the default Maximo tree. Customer customization should be placed in ‘maximo/tools/maximo/en/customer’ directory. All scripts in this directory will be run in order using runscriptfile. These should be normal db update style scripts (i.e. dbc and .sql/java classes). No file system backup of Maximo tree is taken before applying these update.

  • Run Updatedb
    This task completes the running of an updatedb against the target Maximo environment. The application server(s) are stopped prior the the task being run so updatedb can be completed successfully. Task steps are:
    1. Stop application servers JVM(s)
    2. Run Maximo updatedb
    3. Start application server JVM(s)



  • No labels

Disclaimer: Information provided in this wiki is for informational purposes only. Content is not to be considered part of any existing IBM®️ Maximo or TRIRIGA customer subscription, agreement, license or contract. From time to time, this site may contain technical inaccuracies or typographical errors, and IBM do not warrant the accuracy of any posted information. The information contained in this wiki is subject to change without notice. By visiting this wiki, you consent to use of cookies and other tracking technologies by IBM’s subcontractor, Atlassian, in accordance with the Atlassian Cookies & Tracking Notice found at https://www.atlassian.com/legal/cookies. If you do not consent to the collection of your data by Atlassian at any time, please leave the wiki and delete the cookies and other web-tracking technologies through your browser.