IBM Maximo: MAS CLI Options: Difference between revisions
| Line 67: | Line 67: | ||
** Lowest footprint among the available options | ** Lowest footprint among the available options | ||
* '''snojms'' | * '''snojms''' | ||
** Small profile without JMS | ** Small profile without JMS | ||
** Appropriate when JMS queues are not required | ** Appropriate when JMS queues are not required | ||
** Helps reduce resource and storage requirements | ** Helps reduce resource and storage requirements | ||
* '''small'' | * '''small''' | ||
** Small standard profile | ** Small standard profile | ||
** Suitable for compact environments that still want a more complete setup than <code>dev</code> | ** Suitable for compact environments that still want a more complete setup than <code>dev</code> | ||
Revision as of 14:38, 3 May 2026
Caso você deseja outras opções de instalação veja abaixo:
MAS Core
export IBM_ENTITLEMENT_KEY=... mas install --mas-catalog-version v9-250501-amd64 --ibm-entitlement-key $IBM_ENTITLEMENT_KEY \ --mas-channel 9.0.x --mas-instance-id inst1 --mas-workspace-id ws01 --mas-workspace-name "MAS Workspace 01" \ --non-prod \ --storage-class-rwo "ocs-storagecluster-ceph-rbd" --storage-class-rwx "ocs-storagecluster-cephfs" \ --storage-pipeline "ocs-storagecluster-cephfs" --storage-accessmode "ReadWriteMany" \ --license-file "/tmp/license.dat" \ --uds-email "[email protected]" --uds-firstname "Enio" --uds-lastname "Basso" \ --mongodb-namespace "mongoce" \ --accept-license --no-confirm
Manage Components options
for other componentes add to --manage-components variable:
- Asset Configuration Manager: acm=latest
- Aviation: aviation=latest
- Civil Infrastructure: civil=latest
- Envizi Connector: envizi=latest
- Health: health=latest
- Health, Safety and Environment (HSE): hse=latest
- Maximo IT: icd=latest
- Nuclear: nuclear=latest
- Oil & Gas: oilandgas=latest
- Connector for Oracle: oracleadapter=latest
- Connector for SAP: sapadapter=latest
- Service Provider: serviceprovider=latest
- Spatial: spatial=latest
- Reliability Strategies: strategize=latest
- Transportation: transportation=latest
- TRIRIGA Connector: tririga=latest
- Utilities: utilities=latest
- Workday Connector: workday=latest
mas install --mas-catalog-version v9-250501-amd64 --ibm-entitlement-key $IBM_ENTITLEMENT_KEY \ ... --manage-components "base=latest,health=latest" \ ...
Manage Languages
mas install --mas-catalog-version v9-250501-amd64 --ibm-entitlement-key $IBM_ENTITLEMENT_KEY \ ... --manage-base-language "EN" \ --manage-secondary-languages "PT-BR,ES" \ ...
Manage Bundel Sizes
mas install --mas-catalog-version v9-250501-amd64 --ibm-entitlement-key $IBM_ENTITLEMENT_KEY \ ... --manage-server-bundle-size "dev" \ ...
The parameter --manage-server-bundle-size {dev,snojms,small,jms} selects the predefined Manage server bundle profile used during deployment.
- dev
- Development-oriented profile
- Recommended for labs, demos, and small validation environments
- Lowest footprint among the available options
- snojms
- Small profile without JMS
- Appropriate when JMS queues are not required
- Helps reduce resource and storage requirements
- small
- Small standard profile
- Suitable for compact environments that still want a more complete setup than
dev
- jms
- Profile with JMS enabled
- Use when Manage features or integrations require JMS queues
- Typically requires JMS-related storage configuration
Related parameters
--manage-jms
JMS queue storage settings shown in logs: ** mas_app_settings_jms_queue_pvc_storage_class ** mas_app_settings_jms_queue_pvc_accessmode
References
Local CLI help captured in notes:
- sessao3_anotacoes.txt: lines showing
--manage-server-bundle-size {dev,snojms,small,jms}and related flags - sessao-2/sessao2_anatocoes.txt: lines showing the same option in command usage
- sessao3_anotacoes.txt: lines showing
Local example usage:
- sessao3_anotacoes.txt: example command using
--manage-server-bundle-size "dev"
- sessao3_anotacoes.txt: example command using
Local pipeline/log evidence:
- mas-lab/mas.log:
mas_app_settings_server_bundles_size - mas-lab/mas.log: resolved summary for server bundle size
- mas-lab/mas.log: JMS default summary
- mas-lab/mas.log: JMS PVC storage class
- mas-lab/mas.log: JMS PVC access mode
- mas-lab/mas.log:
Notes
The exact internal implementation of each profile is not described in the files available here. The definitions above are inferred from:
the CLI option names the related JMS flags the local pipeline/log parameters captured in this workspace