Wiki - User contributions [en]

IBM Sterling Connect:Direct : Secure+ Sample file

2026-05-20T01:54:47Z

Ebasso:

Sample spconfig.txt

<nowiki>
sync netmap
path=/home/ajc_test/cdunix/ndm/cfg/cdu_silent/netmap.cfg
name=*

;
Import KeyCert
File="/home/ajc_test/cd_install/cdu/silent/cdu_silent_06252025_keycert.pem"
Passphrase=password
Label=cdu_silent_06252025_keycert
ImportMode=Add
;
Import TrustedCert
File="/home/ajc_test/cd_install/cdu/silent/capgemini_ajc_ecdsa_intermediate_ca.pem"
Label=capgemini_ajc_ecdsa_intermediate_ca
ImportMode=Add
;
Update LocalNode
Protocol=TLS1.2,TLS1.3
SecurityMode=FIPS140-2
Override=Y
AuthTimeout=120
KeyCertLabel=cdu_silent_06252025_keycert
EncryptData=Y
ClientAuth=Y
CipherSuites=TLS_AES_256_GCM_SHA384,TLS_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384
SeaEnable=N
SeaCertValDef=null
;

Update Client
Protocol=DefaultToLN
SecurityMode=DefaultToLN
Override=N
AuthTimeout=120
KeyCertLabel=null
ClientAuth=DefaultToLN
CipherSuites=null
;

Update RemoteNode
Name=cdu_silent
Protocol=DefaultToLN
SecurityMode=DefaultToLN
Override=N
AuthTimeout=120
KeyCertLabel=null
EncryptData=DefaultToLN
ClientAuth=DefaultToLN
CertCommonName=cdu_silent_key_cert_06252025
CipherSuites=null
SeaEnable=N
SeaCertValDef=null
;

Update RemoteNode
Name=robin_cd63
Protocol=DefaultToLN
SecurityMode=DefaultToLN
Override=N
AuthTimeout=120
KeyCertLabel=null
EncryptData=DefaultToLN
ClientAuth=DefaultToLN
CertCommonName=robin.ustxlab.aricent.com
CipherSuites=null
SeaEnable=N
SeaCertValDef=null
;
</nowiki>

Note the first command is to synchronize with the Netmap. This will be the Netmap created from your custom netmap.silent file.

= Ver também =

* [[IBM Sterling| Artigos sobre IBM Sterling]]
* [[Tecnologias| Mais Artigos sobre Cloud / WebDev / Tecnologias]]
* [[IBM Sterling Connect:Direct]]

[[Category:IBM Sterling]]
[[Category:Connect:Direct]]
[[Category:B2B Integrator]]

IBM Sterling Connect:Direct : Secure+ Sample file

2026-05-20T01:53:55Z

Ebasso: Created page with " Sample spconfig.txt <nowiki> sync netmap path=/home/ajc_test/cdunix/ndm/cfg/cdu_silent/netmap.cfg name=* ; Import KeyCert File="/home/ajc_test/cd_install/cdu/silent/cdu_silent_06252025_keycert.pem" Passphrase=password Label=cdu_silent_06252025_keycert ImportMode=Add ; Import TrustedCert File="/home/ajc_test/cd_install/cdu/silent/capgemini_ajc_ecdsa_intermediate_ca.pem" Label=capgemini_ajc_ecdsa_intermediate_ca ImportMode=Add ; Upda..."

Sample spconfig.txt

<nowiki>
sync netmap
path=/home/ajc_test/cdunix/ndm/cfg/cdu_silent/netmap.cfg
name=*

;
Import KeyCert
File="/home/ajc_test/cd_install/cdu/silent/cdu_silent_06252025_keycert.pem"
Passphrase=password
Label=cdu_silent_06252025_keycert
ImportMode=Add
;
Import TrustedCert
File="/home/ajc_test/cd_install/cdu/silent/capgemini_ajc_ecdsa_intermediate_ca.pem"
Label=capgemini_ajc_ecdsa_intermediate_ca
ImportMode=Add
;
Update LocalNode
Protocol=TLS1.2,TLS1.3
SecurityMode=FIPS140-2
Override=Y
AuthTimeout=120
KeyCertLabel=cdu_silent_06252025_keycert
EncryptData=Y
ClientAuth=Y
CipherSuites=TLS_AES_256_GCM_SHA384,TLS_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384
SeaEnable=N
SeaCertValDef=null
;

Update Client
Protocol=DefaultToLN
SecurityMode=DefaultToLN
Override=N
AuthTimeout=120
KeyCertLabel=null
ClientAuth=DefaultToLN
CipherSuites=null
;

Update RemoteNode
Name=cdu_silent
Protocol=DefaultToLN
SecurityMode=DefaultToLN
Override=N
AuthTimeout=120
KeyCertLabel=null
EncryptData=DefaultToLN
ClientAuth=DefaultToLN
CertCommonName=cdu_silent_key_cert_06252025
CipherSuites=null
SeaEnable=N
SeaCertValDef=null
;

Update RemoteNode
Name=robin_cd63
Protocol=DefaultToLN
SecurityMode=DefaultToLN
Override=N
AuthTimeout=120
KeyCertLabel=null
EncryptData=DefaultToLN
ClientAuth=DefaultToLN
CertCommonName=robin.ustxlab.aricent.com
CipherSuites=null
SeaEnable=N
SeaCertValDef=null
;
</nowiki>

= Ver também =

* [[IBM Sterling| Artigos sobre IBM Sterling]]
* [[Tecnologias| Mais Artigos sobre Cloud / WebDev / Tecnologias]]
* [[IBM Sterling Connect:Direct]]

[[Category:IBM Sterling]]
[[Category:Connect:Direct]]
[[Category:B2B Integrator]]

IBM Sterling Connect:Direct

2026-05-20T01:51:44Z

Ebasso: /* Secure+ */

<big>IBM Connect:Direct, IBM C:D WebServices e C:D File Agent</big>

= IBM Connect:Direct =

== Main Applications==

[[file:Connect-direct-communication-path.png]]

{| class="wikitable"
|-
! Process !! Description
|-
| cdpmgr || main application daemon process
|-
| cdstatm || the stats daemon that launches along with the cdpmgr
|-
| ndmcmgr ||
command manager which is spawned off from cdpmgr

The ndmcmgr is defined in the netmap local.node api perimeter and normally limited to 16. If these are long time running then most likely the session did not come down gracefully so they get zombied, which shows up as stuck temp files under the work/node directory. You should code the api timeout perimeter in the local.node entry in the netmap.
|-
| ndmsmgr || the session manager
|-
| ndmumgr || the user manager for the lack of better words. You will see this when a download/upload is coded for the proxy or local id
|}

== Install, Commands and Configurations ==

* [[IBM Sterling Connect:Direct : Instalação]]

* [[IBM Sterling Connect:Direct : Silent Install]]

* [[IBM Sterling Connect:Direct : Silent Install without provide certificates]]

* [[IBM Sterling Connect:Direct : Start/Stop Script with SystemD Support]]

* [[IBM Sterling Connect:Direct : Instalação da versão C:D Container]]

* [[IBM Sterling Connect:Direct: Configurando a conexão para um Node C:D ou C:D Server Adapter]]

* [[IBM Sterling Connect:Direct : Principais Comandos e Arquivos]]

* [[IBM Sterling Connect:Direct : Dicas do comando Select Statistics|IBM Sterling Connect:Direct : Dicas do comando 'Select Statistics' ]]

* [[IBM Sterling Connect:Direct: Error LTQA032I - database corruption]]

* [[IBM Sterling Connect:Direct: Run Task ends with 0000000C/SRTS008I on C:D zOS ]]

* [[IBM Sterling Connect:Direct: Configuring C:D to use AWS S3 Storage]]

* [[IBM Sterling Connect:Direct: Configuring C:D to use Minio S3 Storage]]

* [[IBM Sterling Connect:Direct: Configuring C:D to use Azure Blob Storage]]

* [[IBM Sterling Connect:Direct: Configuring C:D to use AWS S3 Storage provide an AWS credentials file as a volume]]

* [[IBM Sterling Connect:Direct: Using extraVolume and extraVolumeMounts in IBM Connect:Direct Deployments]]

== Secure+ ==

* [[IBM Sterling Connect:Direct : Secure+ Sample file]]

* [https://www.ibm.com/support/pages/setting-basic-secure-configuration-using-secure-command-line-interface-spcli?view=full Setting Up A Basic Secure+ Configuration Using The Secure+ Command Line Interface (SPCLI)]

* [https://www.ibm.com/support/pages/how-do-silent-install-connectdirect-unix How to do a Silent Install of Connect:Direct for UNIX]

== Performance Tips and High Availability==

* [[IBM Sterling Connect:Direct : Run Load Test on IBM Sterling Connect:Direct]]

* [[IBM Sterling Connect:Direct : Simulating Latency and Packet Loss in IBM Connect:Direct]]

* [[IBM Sterling Connect:Direct : Performance on AIX]] Draft!!!!

* [https://public.dhe.ibm.com/software/commerce/doc/mft/cdunix/whitepapers/CDU_VCS_Whitepaper.pdf Connect:Direct for UNIX in the Veritas Cluster Server Environment]

* [https://www.ibm.com/docs/en/connect-direct/6.3.0?topic=v63-high-availability#ID1753 High-Availability in C:D]

* [https://www.ibm.com/support/pages/system/files/inline-files/Running_CD_UNIX_behind_a_load_balancer_0.pdf Considerations for Running Connect:Direct for UNIX Behind a Load Balancer]

* [[IBM Sterling Connect:Direct : Script to get process in HOLD and WAIT queue]]

* [https://github.com/ebasso/sterling-b2b-samples/tree/master/connect-direct/cd-watch-shell Script to monitor Connect:Direct Unix 'cdwatch.sh' ]

* [[IBM Sterling Connect:Direct : Horizontal Pod Autoscaling for IBM Sterling Connect:Direct Unix Containers]]

== CD Process Files - Samples==

* [[IBM Sterling Connect:Direct : CD Process Files#CD-UNIX_to_Sterling_B2B_Mailbox | Send file from C:D UNIX to Sterling B2B Mailbox]]
* [[IBM Sterling Connect:Direct : CD Process Files#CD-UNIX_to_Sterling_B2B_Business_Process | Send file from C:D UNIX to Sterling B2B Business Process]]
* [[IBM Sterling Connect:Direct : Submit a file using a command line in C:D MS-Windows | Submit a file using a command line in C:D MS-Windows]]
* [[IBM Sterling Connect:Direct: Configuring C:D to use AWS S3 Storage#Put a file in S3 Bucket | Put a file in S3 Bucket]]
* [[IBM Sterling Connect:Direct: Configuring C:D to use AWS S3 Storage#Get a file from S3 Bucket | Get a file from S3 Bucket]]

== Containers and Kubernetes ==

* [https://github.com/ebasso/sterling-b2b-oncloud IBM Sterling: Deploy Connect:Direct on OpenShift at IBM Cloud - English Version] posted on GitHub

* [[IBM Sterling Connect:Direct : Solving CrashLoopBackOff problems when deploying in Kubernetes/OpenShift]]

= IBM Connect:Direct WebServices =

* [[IBM Sterling Connect:Direct : Install C:D Web Services]]

* [[IBM Sterling Connect:Direct : Enable tracing in C:D using C:D Web Services]]

* [[IBM Sterling Connect:Direct : Create User (Functional Authority) using C:D Web Services]]

* [[IBM Sterling Connect:Direct : Create a Transfer using C:D Web Services]]

* (YouTube) [https://www.youtube.com/watch?v=QgiiOtjHDeY Process Library Management using C:D WebService, create and store CD Process files]

* [https://www.ibm.com/docs/en/connect-direct/6.2.0?topic=file-local-user-information-record-format You can grant specific privileges to the users using the userfile record].
** Anyone that wants to login to the CDU server via the CDWS Web Console will need to have a 'local user' record in the userfile.cfg file.

* [[IBM Sterling Connect:Direct : Certificate-Based Authentication Setup using C:D Web Services]]

* [[IBM Sterling Connect:Direct : C:D WebService - Annotations to Create a Network Load Balancer (NLB) service]]

== Manage C:D Nodes and Partners ==

* [[IBM Sterling Connect:Direct: Trocando a chave TLS do C:D]]

* [[IBM Sterling Connect:Direct : Add a Connect:Direct Node in C:D WebService (Container Version)]]

* [[IBM Sterling Connect:Direct : Import C:D certificates on C:D WebService]]

* (YouTube) [https://www.youtube.com/watch?v=y_tPtxRW4b4 Adding a Connect:Direct Node in C:D WebService]

* (YouTube) [https://www.youtube.com/watch?v=inRb0qMemBc Add a partner manually using C:D WebService, include Secure+ configuration]

* (YouTube) [https://www.youtube.com/watch?v=rL91Oiru_Nc Change a partner using C:D WebService, include Secure+ configuration]

* (YouTube) [https://www.youtube.com/watch?v=VT7MIKXUAkE Trusted Certificate Management From Connect:Direct Node]

== Manage Integrated File Agent==

* [[IBM Sterling Connect:Direct Integrated File Agent]]

* [https://www.youtube.com/watch?v=hE-su8DNDJE Configure Integrate FileAgent using C:D WebService - Basic]

* [https://www.youtube.com/watch?v=heyPqKCr0ng Configure Integrate FileAgent using C:D WebService - Add Rule]

* [https://www.youtube.com/watch?v=CyZ4JJJl-EI Configure Integrate FileAgent using C:D WebService - Watch Directory Mgmt]

== Usando a REST API do C:D WebServices ==
* [[IBM Sterling Connect:Direct : Usando a REST API do C:D WebService]]

= Ver também =

* [[Cloud| Artigos sobre Cloud]]
* [[Tecnologias| Mais Artigos sobre Cloud / WebDev / Tecnologias]]

[[Category:IBM Sterling]]
[[Category:Connect:Direct]]
[[Category:B2B Integrator]]
[[Category:CDP]]

IBM Sterling Connect:Direct

2026-05-20T01:49:13Z

Ebasso: /* Secure+ */

<big>IBM Connect:Direct, IBM C:D WebServices e C:D File Agent</big>

= IBM Connect:Direct =

== Main Applications==

[[file:Connect-direct-communication-path.png]]

{| class="wikitable"
|-
! Process !! Description
|-
| cdpmgr || main application daemon process
|-
| cdstatm || the stats daemon that launches along with the cdpmgr
|-
| ndmcmgr ||
command manager which is spawned off from cdpmgr

The ndmcmgr is defined in the netmap local.node api perimeter and normally limited to 16. If these are long time running then most likely the session did not come down gracefully so they get zombied, which shows up as stuck temp files under the work/node directory. You should code the api timeout perimeter in the local.node entry in the netmap.
|-
| ndmsmgr || the session manager
|-
| ndmumgr || the user manager for the lack of better words. You will see this when a download/upload is coded for the proxy or local id
|}

== Install, Commands and Configurations ==

* [[IBM Sterling Connect:Direct : Instalação]]

* [[IBM Sterling Connect:Direct : Silent Install]]

* [[IBM Sterling Connect:Direct : Silent Install without provide certificates]]

* [[IBM Sterling Connect:Direct : Start/Stop Script with SystemD Support]]

* [[IBM Sterling Connect:Direct : Instalação da versão C:D Container]]

* [[IBM Sterling Connect:Direct: Configurando a conexão para um Node C:D ou C:D Server Adapter]]

* [[IBM Sterling Connect:Direct : Principais Comandos e Arquivos]]

* [[IBM Sterling Connect:Direct : Dicas do comando Select Statistics|IBM Sterling Connect:Direct : Dicas do comando 'Select Statistics' ]]

* [[IBM Sterling Connect:Direct: Error LTQA032I - database corruption]]

* [[IBM Sterling Connect:Direct: Run Task ends with 0000000C/SRTS008I on C:D zOS ]]

* [[IBM Sterling Connect:Direct: Configuring C:D to use AWS S3 Storage]]

* [[IBM Sterling Connect:Direct: Configuring C:D to use Minio S3 Storage]]

* [[IBM Sterling Connect:Direct: Configuring C:D to use Azure Blob Storage]]

* [[IBM Sterling Connect:Direct: Configuring C:D to use AWS S3 Storage provide an AWS credentials file as a volume]]

* [[IBM Sterling Connect:Direct: Using extraVolume and extraVolumeMounts in IBM Connect:Direct Deployments]]

== Secure+ ==

* [https://www.ibm.com/support/pages/setting-basic-secure-configuration-using-secure-command-line-interface-spcli?view=full Setting Up A Basic Secure+ Configuration Using The Secure+ Command Line Interface (SPCLI)]

* [https://www.ibm.com/support/pages/how-do-silent-install-connectdirect-unix How to do a Silent Install of Connect:Direct for UNIX]

== Performance Tips and High Availability==

* [[IBM Sterling Connect:Direct : Run Load Test on IBM Sterling Connect:Direct]]

* [[IBM Sterling Connect:Direct : Simulating Latency and Packet Loss in IBM Connect:Direct]]

* [[IBM Sterling Connect:Direct : Performance on AIX]] Draft!!!!

* [https://public.dhe.ibm.com/software/commerce/doc/mft/cdunix/whitepapers/CDU_VCS_Whitepaper.pdf Connect:Direct for UNIX in the Veritas Cluster Server Environment]

* [https://www.ibm.com/docs/en/connect-direct/6.3.0?topic=v63-high-availability#ID1753 High-Availability in C:D]

* [https://www.ibm.com/support/pages/system/files/inline-files/Running_CD_UNIX_behind_a_load_balancer_0.pdf Considerations for Running Connect:Direct for UNIX Behind a Load Balancer]

* [[IBM Sterling Connect:Direct : Script to get process in HOLD and WAIT queue]]

* [https://github.com/ebasso/sterling-b2b-samples/tree/master/connect-direct/cd-watch-shell Script to monitor Connect:Direct Unix 'cdwatch.sh' ]

* [[IBM Sterling Connect:Direct : Horizontal Pod Autoscaling for IBM Sterling Connect:Direct Unix Containers]]

== CD Process Files - Samples==

* [[IBM Sterling Connect:Direct : CD Process Files#CD-UNIX_to_Sterling_B2B_Mailbox | Send file from C:D UNIX to Sterling B2B Mailbox]]
* [[IBM Sterling Connect:Direct : CD Process Files#CD-UNIX_to_Sterling_B2B_Business_Process | Send file from C:D UNIX to Sterling B2B Business Process]]
* [[IBM Sterling Connect:Direct : Submit a file using a command line in C:D MS-Windows | Submit a file using a command line in C:D MS-Windows]]
* [[IBM Sterling Connect:Direct: Configuring C:D to use AWS S3 Storage#Put a file in S3 Bucket | Put a file in S3 Bucket]]
* [[IBM Sterling Connect:Direct: Configuring C:D to use AWS S3 Storage#Get a file from S3 Bucket | Get a file from S3 Bucket]]

== Containers and Kubernetes ==

* [https://github.com/ebasso/sterling-b2b-oncloud IBM Sterling: Deploy Connect:Direct on OpenShift at IBM Cloud - English Version] posted on GitHub

* [[IBM Sterling Connect:Direct : Solving CrashLoopBackOff problems when deploying in Kubernetes/OpenShift]]

= IBM Connect:Direct WebServices =

* [[IBM Sterling Connect:Direct : Install C:D Web Services]]

* [[IBM Sterling Connect:Direct : Enable tracing in C:D using C:D Web Services]]

* [[IBM Sterling Connect:Direct : Create User (Functional Authority) using C:D Web Services]]

* [[IBM Sterling Connect:Direct : Create a Transfer using C:D Web Services]]

* (YouTube) [https://www.youtube.com/watch?v=QgiiOtjHDeY Process Library Management using C:D WebService, create and store CD Process files]

* [https://www.ibm.com/docs/en/connect-direct/6.2.0?topic=file-local-user-information-record-format You can grant specific privileges to the users using the userfile record].
** Anyone that wants to login to the CDU server via the CDWS Web Console will need to have a 'local user' record in the userfile.cfg file.

* [[IBM Sterling Connect:Direct : Certificate-Based Authentication Setup using C:D Web Services]]

* [[IBM Sterling Connect:Direct : C:D WebService - Annotations to Create a Network Load Balancer (NLB) service]]

== Manage C:D Nodes and Partners ==

* [[IBM Sterling Connect:Direct: Trocando a chave TLS do C:D]]

* [[IBM Sterling Connect:Direct : Add a Connect:Direct Node in C:D WebService (Container Version)]]

* [[IBM Sterling Connect:Direct : Import C:D certificates on C:D WebService]]

* (YouTube) [https://www.youtube.com/watch?v=y_tPtxRW4b4 Adding a Connect:Direct Node in C:D WebService]

* (YouTube) [https://www.youtube.com/watch?v=inRb0qMemBc Add a partner manually using C:D WebService, include Secure+ configuration]

* (YouTube) [https://www.youtube.com/watch?v=rL91Oiru_Nc Change a partner using C:D WebService, include Secure+ configuration]

* (YouTube) [https://www.youtube.com/watch?v=VT7MIKXUAkE Trusted Certificate Management From Connect:Direct Node]

== Manage Integrated File Agent==

* [[IBM Sterling Connect:Direct Integrated File Agent]]

* [https://www.youtube.com/watch?v=hE-su8DNDJE Configure Integrate FileAgent using C:D WebService - Basic]

* [https://www.youtube.com/watch?v=heyPqKCr0ng Configure Integrate FileAgent using C:D WebService - Add Rule]

* [https://www.youtube.com/watch?v=CyZ4JJJl-EI Configure Integrate FileAgent using C:D WebService - Watch Directory Mgmt]

== Usando a REST API do C:D WebServices ==
* [[IBM Sterling Connect:Direct : Usando a REST API do C:D WebService]]

= Ver também =

* [[Cloud| Artigos sobre Cloud]]
* [[Tecnologias| Mais Artigos sobre Cloud / WebDev / Tecnologias]]

[[Category:IBM Sterling]]
[[Category:Connect:Direct]]
[[Category:B2B Integrator]]
[[Category:CDP]]

IBM Sterling Connect:Direct

2026-05-20T01:48:28Z

Ebasso: /* Secure+ */

<big>IBM Connect:Direct, IBM C:D WebServices e C:D File Agent</big>

= IBM Connect:Direct =

== Main Applications==

[[file:Connect-direct-communication-path.png]]

{| class="wikitable"
|-
! Process !! Description
|-
| cdpmgr || main application daemon process
|-
| cdstatm || the stats daemon that launches along with the cdpmgr
|-
| ndmcmgr ||
command manager which is spawned off from cdpmgr

The ndmcmgr is defined in the netmap local.node api perimeter and normally limited to 16. If these are long time running then most likely the session did not come down gracefully so they get zombied, which shows up as stuck temp files under the work/node directory. You should code the api timeout perimeter in the local.node entry in the netmap.
|-
| ndmsmgr || the session manager
|-
| ndmumgr || the user manager for the lack of better words. You will see this when a download/upload is coded for the proxy or local id
|}

== Install, Commands and Configurations ==

* [[IBM Sterling Connect:Direct : Instalação]]

* [[IBM Sterling Connect:Direct : Silent Install]]

* [[IBM Sterling Connect:Direct : Silent Install without provide certificates]]

* [[IBM Sterling Connect:Direct : Start/Stop Script with SystemD Support]]

* [[IBM Sterling Connect:Direct : Instalação da versão C:D Container]]

* [[IBM Sterling Connect:Direct: Configurando a conexão para um Node C:D ou C:D Server Adapter]]

* [[IBM Sterling Connect:Direct : Principais Comandos e Arquivos]]

* [[IBM Sterling Connect:Direct : Dicas do comando Select Statistics|IBM Sterling Connect:Direct : Dicas do comando 'Select Statistics' ]]

* [[IBM Sterling Connect:Direct: Error LTQA032I - database corruption]]

* [[IBM Sterling Connect:Direct: Run Task ends with 0000000C/SRTS008I on C:D zOS ]]

* [[IBM Sterling Connect:Direct: Configuring C:D to use AWS S3 Storage]]

* [[IBM Sterling Connect:Direct: Configuring C:D to use Minio S3 Storage]]

* [[IBM Sterling Connect:Direct: Configuring C:D to use Azure Blob Storage]]

* [[IBM Sterling Connect:Direct: Configuring C:D to use AWS S3 Storage provide an AWS credentials file as a volume]]

* [[IBM Sterling Connect:Direct: Using extraVolume and extraVolumeMounts in IBM Connect:Direct Deployments]]

== Secure+ ==

[https://www.ibm.com/support/pages/setting-basic-secure-configuration-using-secure-command-line-interface-spcli?view=full Setting Up A Basic Secure+ Configuration Using The Secure+ Command Line Interface (SPCLI)]

== Performance Tips and High Availability==

* [[IBM Sterling Connect:Direct : Run Load Test on IBM Sterling Connect:Direct]]

* [[IBM Sterling Connect:Direct : Simulating Latency and Packet Loss in IBM Connect:Direct]]

* [[IBM Sterling Connect:Direct : Performance on AIX]] Draft!!!!

* [https://public.dhe.ibm.com/software/commerce/doc/mft/cdunix/whitepapers/CDU_VCS_Whitepaper.pdf Connect:Direct for UNIX in the Veritas Cluster Server Environment]

* [https://www.ibm.com/docs/en/connect-direct/6.3.0?topic=v63-high-availability#ID1753 High-Availability in C:D]

* [https://www.ibm.com/support/pages/system/files/inline-files/Running_CD_UNIX_behind_a_load_balancer_0.pdf Considerations for Running Connect:Direct for UNIX Behind a Load Balancer]

* [[IBM Sterling Connect:Direct : Script to get process in HOLD and WAIT queue]]

* [https://github.com/ebasso/sterling-b2b-samples/tree/master/connect-direct/cd-watch-shell Script to monitor Connect:Direct Unix 'cdwatch.sh' ]

* [[IBM Sterling Connect:Direct : Horizontal Pod Autoscaling for IBM Sterling Connect:Direct Unix Containers]]

== CD Process Files - Samples==

* [[IBM Sterling Connect:Direct : CD Process Files#CD-UNIX_to_Sterling_B2B_Mailbox | Send file from C:D UNIX to Sterling B2B Mailbox]]
* [[IBM Sterling Connect:Direct : CD Process Files#CD-UNIX_to_Sterling_B2B_Business_Process | Send file from C:D UNIX to Sterling B2B Business Process]]
* [[IBM Sterling Connect:Direct : Submit a file using a command line in C:D MS-Windows | Submit a file using a command line in C:D MS-Windows]]
* [[IBM Sterling Connect:Direct: Configuring C:D to use AWS S3 Storage#Put a file in S3 Bucket | Put a file in S3 Bucket]]
* [[IBM Sterling Connect:Direct: Configuring C:D to use AWS S3 Storage#Get a file from S3 Bucket | Get a file from S3 Bucket]]

== Containers and Kubernetes ==

* [https://github.com/ebasso/sterling-b2b-oncloud IBM Sterling: Deploy Connect:Direct on OpenShift at IBM Cloud - English Version] posted on GitHub

* [[IBM Sterling Connect:Direct : Solving CrashLoopBackOff problems when deploying in Kubernetes/OpenShift]]

= IBM Connect:Direct WebServices =

* [[IBM Sterling Connect:Direct : Install C:D Web Services]]

* [[IBM Sterling Connect:Direct : Enable tracing in C:D using C:D Web Services]]

* [[IBM Sterling Connect:Direct : Create User (Functional Authority) using C:D Web Services]]

* [[IBM Sterling Connect:Direct : Create a Transfer using C:D Web Services]]

* (YouTube) [https://www.youtube.com/watch?v=QgiiOtjHDeY Process Library Management using C:D WebService, create and store CD Process files]

* [https://www.ibm.com/docs/en/connect-direct/6.2.0?topic=file-local-user-information-record-format You can grant specific privileges to the users using the userfile record].
** Anyone that wants to login to the CDU server via the CDWS Web Console will need to have a 'local user' record in the userfile.cfg file.

* [[IBM Sterling Connect:Direct : Certificate-Based Authentication Setup using C:D Web Services]]

* [[IBM Sterling Connect:Direct : C:D WebService - Annotations to Create a Network Load Balancer (NLB) service]]

== Manage C:D Nodes and Partners ==

* [[IBM Sterling Connect:Direct: Trocando a chave TLS do C:D]]

* [[IBM Sterling Connect:Direct : Add a Connect:Direct Node in C:D WebService (Container Version)]]

* [[IBM Sterling Connect:Direct : Import C:D certificates on C:D WebService]]

* (YouTube) [https://www.youtube.com/watch?v=y_tPtxRW4b4 Adding a Connect:Direct Node in C:D WebService]

* (YouTube) [https://www.youtube.com/watch?v=inRb0qMemBc Add a partner manually using C:D WebService, include Secure+ configuration]

* (YouTube) [https://www.youtube.com/watch?v=rL91Oiru_Nc Change a partner using C:D WebService, include Secure+ configuration]

* (YouTube) [https://www.youtube.com/watch?v=VT7MIKXUAkE Trusted Certificate Management From Connect:Direct Node]

== Manage Integrated File Agent==

* [[IBM Sterling Connect:Direct Integrated File Agent]]

* [https://www.youtube.com/watch?v=hE-su8DNDJE Configure Integrate FileAgent using C:D WebService - Basic]

* [https://www.youtube.com/watch?v=heyPqKCr0ng Configure Integrate FileAgent using C:D WebService - Add Rule]

* [https://www.youtube.com/watch?v=CyZ4JJJl-EI Configure Integrate FileAgent using C:D WebService - Watch Directory Mgmt]

== Usando a REST API do C:D WebServices ==
* [[IBM Sterling Connect:Direct : Usando a REST API do C:D WebService]]

= Ver também =

* [[Cloud| Artigos sobre Cloud]]
* [[Tecnologias| Mais Artigos sobre Cloud / WebDev / Tecnologias]]

[[Category:IBM Sterling]]
[[Category:Connect:Direct]]
[[Category:B2B Integrator]]
[[Category:CDP]]

IBM Sterling Connect:Direct

2026-05-20T01:47:07Z

Ebasso: /* Install, Commands and Configurations */

<big>IBM Connect:Direct, IBM C:D WebServices e C:D File Agent</big>

= IBM Connect:Direct =

== Main Applications==

[[file:Connect-direct-communication-path.png]]

{| class="wikitable"
|-
! Process !! Description
|-
| cdpmgr || main application daemon process
|-
| cdstatm || the stats daemon that launches along with the cdpmgr
|-
| ndmcmgr ||
command manager which is spawned off from cdpmgr

The ndmcmgr is defined in the netmap local.node api perimeter and normally limited to 16. If these are long time running then most likely the session did not come down gracefully so they get zombied, which shows up as stuck temp files under the work/node directory. You should code the api timeout perimeter in the local.node entry in the netmap.
|-
| ndmsmgr || the session manager
|-
| ndmumgr || the user manager for the lack of better words. You will see this when a download/upload is coded for the proxy or local id
|}

== Install, Commands and Configurations ==

* [[IBM Sterling Connect:Direct : Instalação]]

* [[IBM Sterling Connect:Direct : Silent Install]]

* [[IBM Sterling Connect:Direct : Silent Install without provide certificates]]

* [[IBM Sterling Connect:Direct : Start/Stop Script with SystemD Support]]

* [[IBM Sterling Connect:Direct : Instalação da versão C:D Container]]

* [[IBM Sterling Connect:Direct: Configurando a conexão para um Node C:D ou C:D Server Adapter]]

* [[IBM Sterling Connect:Direct : Principais Comandos e Arquivos]]

* [[IBM Sterling Connect:Direct : Dicas do comando Select Statistics|IBM Sterling Connect:Direct : Dicas do comando 'Select Statistics' ]]

* [[IBM Sterling Connect:Direct: Error LTQA032I - database corruption]]

* [[IBM Sterling Connect:Direct: Run Task ends with 0000000C/SRTS008I on C:D zOS ]]

* [[IBM Sterling Connect:Direct: Configuring C:D to use AWS S3 Storage]]

* [[IBM Sterling Connect:Direct: Configuring C:D to use Minio S3 Storage]]

* [[IBM Sterling Connect:Direct: Configuring C:D to use Azure Blob Storage]]

* [[IBM Sterling Connect:Direct: Configuring C:D to use AWS S3 Storage provide an AWS credentials file as a volume]]

* [[IBM Sterling Connect:Direct: Using extraVolume and extraVolumeMounts in IBM Connect:Direct Deployments]]

== Secure+ ==

== Performance Tips and High Availability==

* [[IBM Sterling Connect:Direct : Run Load Test on IBM Sterling Connect:Direct]]

* [[IBM Sterling Connect:Direct : Simulating Latency and Packet Loss in IBM Connect:Direct]]

* [[IBM Sterling Connect:Direct : Performance on AIX]] Draft!!!!

* [https://public.dhe.ibm.com/software/commerce/doc/mft/cdunix/whitepapers/CDU_VCS_Whitepaper.pdf Connect:Direct for UNIX in the Veritas Cluster Server Environment]

* [https://www.ibm.com/docs/en/connect-direct/6.3.0?topic=v63-high-availability#ID1753 High-Availability in C:D]

* [https://www.ibm.com/support/pages/system/files/inline-files/Running_CD_UNIX_behind_a_load_balancer_0.pdf Considerations for Running Connect:Direct for UNIX Behind a Load Balancer]

* [[IBM Sterling Connect:Direct : Script to get process in HOLD and WAIT queue]]

* [https://github.com/ebasso/sterling-b2b-samples/tree/master/connect-direct/cd-watch-shell Script to monitor Connect:Direct Unix 'cdwatch.sh' ]

* [[IBM Sterling Connect:Direct : Horizontal Pod Autoscaling for IBM Sterling Connect:Direct Unix Containers]]

== CD Process Files - Samples==

* [[IBM Sterling Connect:Direct : CD Process Files#CD-UNIX_to_Sterling_B2B_Mailbox | Send file from C:D UNIX to Sterling B2B Mailbox]]
* [[IBM Sterling Connect:Direct : CD Process Files#CD-UNIX_to_Sterling_B2B_Business_Process | Send file from C:D UNIX to Sterling B2B Business Process]]
* [[IBM Sterling Connect:Direct : Submit a file using a command line in C:D MS-Windows | Submit a file using a command line in C:D MS-Windows]]
* [[IBM Sterling Connect:Direct: Configuring C:D to use AWS S3 Storage#Put a file in S3 Bucket | Put a file in S3 Bucket]]
* [[IBM Sterling Connect:Direct: Configuring C:D to use AWS S3 Storage#Get a file from S3 Bucket | Get a file from S3 Bucket]]

== Containers and Kubernetes ==

* [https://github.com/ebasso/sterling-b2b-oncloud IBM Sterling: Deploy Connect:Direct on OpenShift at IBM Cloud - English Version] posted on GitHub

* [[IBM Sterling Connect:Direct : Solving CrashLoopBackOff problems when deploying in Kubernetes/OpenShift]]

= IBM Connect:Direct WebServices =

* [[IBM Sterling Connect:Direct : Install C:D Web Services]]

* [[IBM Sterling Connect:Direct : Enable tracing in C:D using C:D Web Services]]

* [[IBM Sterling Connect:Direct : Create User (Functional Authority) using C:D Web Services]]

* [[IBM Sterling Connect:Direct : Create a Transfer using C:D Web Services]]

* (YouTube) [https://www.youtube.com/watch?v=QgiiOtjHDeY Process Library Management using C:D WebService, create and store CD Process files]

* [https://www.ibm.com/docs/en/connect-direct/6.2.0?topic=file-local-user-information-record-format You can grant specific privileges to the users using the userfile record].
** Anyone that wants to login to the CDU server via the CDWS Web Console will need to have a 'local user' record in the userfile.cfg file.

* [[IBM Sterling Connect:Direct : Certificate-Based Authentication Setup using C:D Web Services]]

* [[IBM Sterling Connect:Direct : C:D WebService - Annotations to Create a Network Load Balancer (NLB) service]]

== Manage C:D Nodes and Partners ==

* [[IBM Sterling Connect:Direct: Trocando a chave TLS do C:D]]

* [[IBM Sterling Connect:Direct : Add a Connect:Direct Node in C:D WebService (Container Version)]]

* [[IBM Sterling Connect:Direct : Import C:D certificates on C:D WebService]]

* (YouTube) [https://www.youtube.com/watch?v=y_tPtxRW4b4 Adding a Connect:Direct Node in C:D WebService]

* (YouTube) [https://www.youtube.com/watch?v=inRb0qMemBc Add a partner manually using C:D WebService, include Secure+ configuration]

* (YouTube) [https://www.youtube.com/watch?v=rL91Oiru_Nc Change a partner using C:D WebService, include Secure+ configuration]

* (YouTube) [https://www.youtube.com/watch?v=VT7MIKXUAkE Trusted Certificate Management From Connect:Direct Node]

== Manage Integrated File Agent==

* [[IBM Sterling Connect:Direct Integrated File Agent]]

* [https://www.youtube.com/watch?v=hE-su8DNDJE Configure Integrate FileAgent using C:D WebService - Basic]

* [https://www.youtube.com/watch?v=heyPqKCr0ng Configure Integrate FileAgent using C:D WebService - Add Rule]

* [https://www.youtube.com/watch?v=CyZ4JJJl-EI Configure Integrate FileAgent using C:D WebService - Watch Directory Mgmt]

== Usando a REST API do C:D WebServices ==
* [[IBM Sterling Connect:Direct : Usando a REST API do C:D WebService]]

= Ver também =

* [[Cloud| Artigos sobre Cloud]]
* [[Tecnologias| Mais Artigos sobre Cloud / WebDev / Tecnologias]]

[[Category:IBM Sterling]]
[[Category:Connect:Direct]]
[[Category:B2B Integrator]]
[[Category:CDP]]

IBM Sterling Connect:Direct : Silent Install

2026-05-20T01:43:40Z

Ebasso:

Updated to 6.4.0.5

Other versions:

* [[IBM Sterling Connect:Direct : Silent Install]]

* [[IBM Sterling Connect:Direct : Silent Install without provide certificates]]

IBM Articles:

* [https://www.ibm.com/support/pages/how-do-silent-install-connectdirect-unix How to do a Silent Install of Connect:Direct for UNIX]

= Extract installer =

mkdir /Binaries/CD

tar -xvf 6.4.0.5-IBMSterlingConnectDirectforUNIX-Linux-x86-iFix007.tar

will extract files cdinstall, cdinstall_a, cdunix.

= Install =

1) Generate Certificate

openssl req -x509 -nodes -days 3650 -newkey rsa:4096 -sha512 -subj "/CN=CDNODE02" -keyout cdcert.key -out cdcert.crt -batch

cat cdcert.crt cdcert.key > cdcert.pem

2) Setup OS

useradd -m cdadmin

mkdir -p /opt/cdunix

chown cdadmin:cdadmin /opt/cdunix

3) Setup silent install

Create dummy file for secure+

echo ""> spcmds.rsp

Create file silent_install.ini

<nowiki>cdai_installCmd=install
cdai_cpioFile=/Binaries/CD/cdunix
cdai_installDir=/opt/cdunix
cdai_localNodeName="CDNODE02"
cdai_acquireHostnameOrIP=ip4
cdai_trace=y
cdai_agentPort=1365
cdai_serverPort=1364
cdai_clientPort=1363
cdai_localCertFile=cdcert.pem
cdai_localCertLabel=cdinternal
cdai_adminUserid=cdadmin
cdai_keystorePassword=changeit
cdai_ignoreExistingInstallDir=y
cdai_spConfig=spcmds.rsp
cdai_installFA=y
cdai_fileAgentEnable=n</nowiki>

4) Run command

./cdinstall_a -f silent_install.ini

= Ver também =

* [[IBM Sterling| Artigos sobre IBM Sterling]]
* [[Tecnologias| Mais Artigos sobre Cloud / WebDev / Tecnologias]]
* [[IBM Sterling Connect:Direct]]

[[Category:IBM Sterling]]
[[Category:Connect:Direct]]
[[Category:B2B Integrator]]

IBM Sterling Connect:Direct : Silent Install

2026-05-20T01:42:02Z

Ebasso:

Updated to 6.4.0.5

Other versions:

* [[IBM Sterling Connect:Direct : Silent Install]]

* [[IBM Sterling Connect:Direct : Silent Install without provide certificates]]

= Extract installer =

mkdir /Binaries/CD

tar -xvf 6.4.0.5-IBMSterlingConnectDirectforUNIX-Linux-x86-iFix007.tar

will extract files cdinstall, cdinstall_a, cdunix.

= Install =

1) Generate Certificate

openssl req -x509 -nodes -days 3650 -newkey rsa:4096 -sha512 -subj "/CN=CDNODE02" -keyout cdcert.key -out cdcert.crt -batch

cat cdcert.crt cdcert.key > cdcert.pem

2) Setup OS

useradd -m cdadmin

mkdir -p /opt/cdunix

chown cdadmin:cdadmin /opt/cdunix

3) Setup silent install

Create dummy file for secure+

echo ""> spcmds.rsp

Create file silent_install.ini

<nowiki>cdai_installCmd=install
cdai_cpioFile=/Binaries/CD/cdunix
cdai_installDir=/opt/cdunix
cdai_localNodeName="CDNODE02"
cdai_acquireHostnameOrIP=ip4
cdai_trace=y
cdai_agentPort=1365
cdai_serverPort=1364
cdai_clientPort=1363
cdai_localCertFile=cdcert.pem
cdai_localCertLabel=cdinternal
cdai_adminUserid=cdadmin
cdai_keystorePassword=changeit
cdai_ignoreExistingInstallDir=y
cdai_spConfig=spcmds.rsp
cdai_installFA=y
cdai_fileAgentEnable=n</nowiki>

4) Run command

./cdinstall_a -f silent_install.ini

= Ver também =

* [[IBM Sterling| Artigos sobre IBM Sterling]]
* [[Tecnologias| Mais Artigos sobre Cloud / WebDev / Tecnologias]]
* [[IBM Sterling Connect:Direct]]

[[Category:IBM Sterling]]
[[Category:Connect:Direct]]
[[Category:B2B Integrator]]

IBM Sterling Connect:Direct : Silent Install without provide certificates

2026-05-20T01:41:04Z

Ebasso: Created page with "= Extract installer = mkdir /Binaries/CD tar -xvf 6.4.0.5-IBMSterlingConnectDirectforUNIX-Linux-x86-iFix007.tar will extract files cdinstall, cdinstall_a, cdunix. = Install = 1) Setup OS useradd -m cdadmin mkdir -p /opt/cdunix chown cdadmin:cdadmin /opt/cdunix 3) Setup silent install Create no_spconfig.txt echo "quit;"> no_spconfig.txt Create file silent_install.ini <nowiki>cdai_installCmd=install cdai_cpioFile=/Binaries/CD/cdunix cdai_installDi..."

= Extract installer =

mkdir /Binaries/CD

tar -xvf 6.4.0.5-IBMSterlingConnectDirectforUNIX-Linux-x86-iFix007.tar

will extract files cdinstall, cdinstall_a, cdunix.

= Install =

1) Setup OS

useradd -m cdadmin

mkdir -p /opt/cdunix

chown cdadmin:cdadmin /opt/cdunix

3) Setup silent install

Create no_spconfig.txt

echo "quit;"> no_spconfig.txt

Create file silent_install.ini

<nowiki>cdai_installCmd=install
cdai_cpioFile=/Binaries/CD/cdunix
cdai_installDir=/opt/cdunix
cdai_localNodeName="CDNODE10"
cdai_acquireHostnameOrIP=ip4
cdai_trace=y
cdai_agentPort=1365
cdai_serverPort=1364
cdai_clientPort=1363
cdai_adminUserid=cdadmin
cdai_keystorePassword=changeit
cdai_ignoreExistingInstallDir=y
cdai_spConfig=no_spconfig.txt
cdai_installFA=y
cdai_fileAgentEnable=n</nowiki>

4) Run command

./cdinstall_a -f silent_install.ini

= Ver também =

* [[IBM Sterling| Artigos sobre IBM Sterling]]
* [[Tecnologias| Mais Artigos sobre Cloud / WebDev / Tecnologias]]
* [[IBM Sterling Connect:Direct]]

[[Category:IBM Sterling]]
[[Category:Connect:Direct]]
[[Category:B2B Integrator]]

IBM Sterling Connect:Direct

2026-05-20T01:37:57Z

Ebasso: /* Install, Commands and Configurations */

<big>IBM Connect:Direct, IBM C:D WebServices e C:D File Agent</big>

= IBM Connect:Direct =

== Main Applications==

[[file:Connect-direct-communication-path.png]]

{| class="wikitable"
|-
! Process !! Description
|-
| cdpmgr || main application daemon process
|-
| cdstatm || the stats daemon that launches along with the cdpmgr
|-
| ndmcmgr ||
command manager which is spawned off from cdpmgr

The ndmcmgr is defined in the netmap local.node api perimeter and normally limited to 16. If these are long time running then most likely the session did not come down gracefully so they get zombied, which shows up as stuck temp files under the work/node directory. You should code the api timeout perimeter in the local.node entry in the netmap.
|-
| ndmsmgr || the session manager
|-
| ndmumgr || the user manager for the lack of better words. You will see this when a download/upload is coded for the proxy or local id
|}

== Install, Commands and Configurations ==

* [[IBM Sterling Connect:Direct : Instalação]]

* [[IBM Sterling Connect:Direct : Silent Install]]

* [[IBM Sterling Connect:Direct : Silent Install without provide certificates]]

* [[IBM Sterling Connect:Direct : Start/Stop Script with SystemD Support]]

* [[IBM Sterling Connect:Direct : Instalação da versão C:D Container]]

* [[IBM Sterling Connect:Direct: Configurando a conexão para um Node C:D ou C:D Server Adapter]]

* [[IBM Sterling Connect:Direct : Principais Comandos e Arquivos]]

* [[IBM Sterling Connect:Direct : Dicas do comando Select Statistics|IBM Sterling Connect:Direct : Dicas do comando 'Select Statistics' ]]

* [[IBM Sterling Connect:Direct: Error LTQA032I - database corruption]]

* [[IBM Sterling Connect:Direct: Run Task ends with 0000000C/SRTS008I on C:D zOS ]]

* [[IBM Sterling Connect:Direct: Configuring C:D to use AWS S3 Storage]]

* [[IBM Sterling Connect:Direct: Configuring C:D to use Minio S3 Storage]]

* [[IBM Sterling Connect:Direct: Configuring C:D to use Azure Blob Storage]]

* [[IBM Sterling Connect:Direct: Configuring C:D to use AWS S3 Storage provide an AWS credentials file as a volume]]

* [[IBM Sterling Connect:Direct: Using extraVolume and extraVolumeMounts in IBM Connect:Direct Deployments]]

== Performance Tips and High Availability==

* [[IBM Sterling Connect:Direct : Run Load Test on IBM Sterling Connect:Direct]]

* [[IBM Sterling Connect:Direct : Simulating Latency and Packet Loss in IBM Connect:Direct]]

* [[IBM Sterling Connect:Direct : Performance on AIX]] Draft!!!!

* [https://public.dhe.ibm.com/software/commerce/doc/mft/cdunix/whitepapers/CDU_VCS_Whitepaper.pdf Connect:Direct for UNIX in the Veritas Cluster Server Environment]

* [https://www.ibm.com/docs/en/connect-direct/6.3.0?topic=v63-high-availability#ID1753 High-Availability in C:D]

* [https://www.ibm.com/support/pages/system/files/inline-files/Running_CD_UNIX_behind_a_load_balancer_0.pdf Considerations for Running Connect:Direct for UNIX Behind a Load Balancer]

* [[IBM Sterling Connect:Direct : Script to get process in HOLD and WAIT queue]]

* [https://github.com/ebasso/sterling-b2b-samples/tree/master/connect-direct/cd-watch-shell Script to monitor Connect:Direct Unix 'cdwatch.sh' ]

* [[IBM Sterling Connect:Direct : Horizontal Pod Autoscaling for IBM Sterling Connect:Direct Unix Containers]]

== CD Process Files - Samples==

* [[IBM Sterling Connect:Direct : CD Process Files#CD-UNIX_to_Sterling_B2B_Mailbox | Send file from C:D UNIX to Sterling B2B Mailbox]]
* [[IBM Sterling Connect:Direct : CD Process Files#CD-UNIX_to_Sterling_B2B_Business_Process | Send file from C:D UNIX to Sterling B2B Business Process]]
* [[IBM Sterling Connect:Direct : Submit a file using a command line in C:D MS-Windows | Submit a file using a command line in C:D MS-Windows]]
* [[IBM Sterling Connect:Direct: Configuring C:D to use AWS S3 Storage#Put a file in S3 Bucket | Put a file in S3 Bucket]]
* [[IBM Sterling Connect:Direct: Configuring C:D to use AWS S3 Storage#Get a file from S3 Bucket | Get a file from S3 Bucket]]

== Containers and Kubernetes ==

* [https://github.com/ebasso/sterling-b2b-oncloud IBM Sterling: Deploy Connect:Direct on OpenShift at IBM Cloud - English Version] posted on GitHub

* [[IBM Sterling Connect:Direct : Solving CrashLoopBackOff problems when deploying in Kubernetes/OpenShift]]

= IBM Connect:Direct WebServices =

* [[IBM Sterling Connect:Direct : Install C:D Web Services]]

* [[IBM Sterling Connect:Direct : Enable tracing in C:D using C:D Web Services]]

* [[IBM Sterling Connect:Direct : Create User (Functional Authority) using C:D Web Services]]

* [[IBM Sterling Connect:Direct : Create a Transfer using C:D Web Services]]

* (YouTube) [https://www.youtube.com/watch?v=QgiiOtjHDeY Process Library Management using C:D WebService, create and store CD Process files]

* [https://www.ibm.com/docs/en/connect-direct/6.2.0?topic=file-local-user-information-record-format You can grant specific privileges to the users using the userfile record].
** Anyone that wants to login to the CDU server via the CDWS Web Console will need to have a 'local user' record in the userfile.cfg file.

* [[IBM Sterling Connect:Direct : Certificate-Based Authentication Setup using C:D Web Services]]

* [[IBM Sterling Connect:Direct : C:D WebService - Annotations to Create a Network Load Balancer (NLB) service]]

== Manage C:D Nodes and Partners ==

* [[IBM Sterling Connect:Direct: Trocando a chave TLS do C:D]]

* [[IBM Sterling Connect:Direct : Add a Connect:Direct Node in C:D WebService (Container Version)]]

* [[IBM Sterling Connect:Direct : Import C:D certificates on C:D WebService]]

* (YouTube) [https://www.youtube.com/watch?v=y_tPtxRW4b4 Adding a Connect:Direct Node in C:D WebService]

* (YouTube) [https://www.youtube.com/watch?v=inRb0qMemBc Add a partner manually using C:D WebService, include Secure+ configuration]

* (YouTube) [https://www.youtube.com/watch?v=rL91Oiru_Nc Change a partner using C:D WebService, include Secure+ configuration]

* (YouTube) [https://www.youtube.com/watch?v=VT7MIKXUAkE Trusted Certificate Management From Connect:Direct Node]

== Manage Integrated File Agent==

* [[IBM Sterling Connect:Direct Integrated File Agent]]

* [https://www.youtube.com/watch?v=hE-su8DNDJE Configure Integrate FileAgent using C:D WebService - Basic]

* [https://www.youtube.com/watch?v=heyPqKCr0ng Configure Integrate FileAgent using C:D WebService - Add Rule]

* [https://www.youtube.com/watch?v=CyZ4JJJl-EI Configure Integrate FileAgent using C:D WebService - Watch Directory Mgmt]

== Usando a REST API do C:D WebServices ==
* [[IBM Sterling Connect:Direct : Usando a REST API do C:D WebService]]

= Ver também =

* [[Cloud| Artigos sobre Cloud]]
* [[Tecnologias| Mais Artigos sobre Cloud / WebDev / Tecnologias]]

[[Category:IBM Sterling]]
[[Category:Connect:Direct]]
[[Category:B2B Integrator]]
[[Category:CDP]]

IBM Sterling B2B: Configuring SSL in IBM Sterling B2B Integrator

2026-05-14T20:18:37Z

Ebasso: /* See also */

= Configuring IBM Sterling B2B Integrator for SSL =

1) Go to the properties directory

cd /home/siuser/SI/properties

1) Edit the file '''customer_overrides.properties''' and add:

noapp.HTTPS_REDIRECT_WARS=ALL
noapp.SKIP_BASEPORT_DEPLOYMENT_WARS=ALL
noapp.HTTPS_LIST_PORT=5001

If you also want to change the certificate:

noapp.sslCert=<INTERNAL_CREATED_CERTIFICATE>

Save the file.

2) Edit the file '''sandbox.cfg''' and modify:

WEBAPP_LIST_PORT=5001
WEBAPP_PROTOCOL=https

Save the file.

3) Stop B2Bi/SFG

4) Run the following commands:

cd /home/siuser/SI/bin

./setupfiles.sh

./deployer.sh

5) Start B2Bi/SFG

== Older Version ==

1) Edit the file '''customer_overrides.properties''' and add:

noapp.HTTPS_REDIRECT_WARS=admin,dashboard,gbm,communitymanagement,myaft,portlets,filegateway,myfilegateway,myfg
noapp.SKIP_BASEPORT_DEPLOYMENT_WARS=admin,dashboard,gpm,communitymanagement,myaft,portlets,filegateway,myfilegateway,myfg
noapp.HTTPS_LIST_PORT=5001

= See also =

[[Category:customer_overrides.properties]]
[[Category:IBM Sterling]]
[[Category:IBM Sterling B2B]]

IBM Sterling B2B: Configuring SSL in IBM Sterling B2B Integrator

2026-05-14T20:17:23Z

Ebasso: Created page with "= Configuring IBM Sterling B2B Integrator for SSL = 1) Go to the properties directory cd /home/siuser/SI/properties 1) Edit the file '''customer_overrides.properties''' and add: noapp.HTTPS_REDIRECT_WARS=ALL noapp.SKIP_BASEPORT_DEPLOYMENT_WARS=ALL noapp.HTTPS_LIST_PORT=5001 If you also want to change the certificate: noapp.sslCert=<INTERNAL_CREATED_CERTIFICATE> Save the file. 2) Edit the file '''sandbox.cfg''' and modify: WEBAPP_LIST_PORT=5001 WEBA..."

IBM Sterling B2B Integrator

2026-05-14T20:16:37Z

Ebasso: /* Comandos, Dicas e Procedimentos */

{| class="wikitable"
|-
! Context !! Description
|-
| http://<server>:5000/dashboard || Sterling B2Bi Administration
|-
| http://<server>:5000/dashboard || Sterling File Gateway
|-
| http://<server>:5078/B2BAPIs/svc || Sterling B2Bi API
|-
| http://<server>:5078/propertyUI/app || Sterling B2Bi Customization Admin
|-
| http://<server>:5078/swiftapis || SWIFT REST API (available on version 6.2)
|-
| http://<server>:5078/pgpapis || PGP REST API (available on version 6.2)
|-
| http://<server>:5078/sfgapis || SFG REST API (available on version 6.2)
|}

== IBM Sterling B2Bi Container Network Topology ==
[[File:Ibm-sterling-openshift-network.png|center]]

== Performance Tuning e Troubleshooting ==

* [[IBM Sterling B2B: Usando o JMeter para realizar testes de carga]]

* [[IBM Sterling B2B: Run FTP Load Test on Sterling B2B Integrator]]

* [[IBM Sterling B2B: Run SFTP Load Test on Sterling B2B Integrator]]

* [[IBM Sterling B2B: Configuring SB2Bi to use S3 Storage Provider]]

* [[IBM Sterling B2B: Configuring SB2Bi to connect Microsoft Sharepoint]] Draft!!!

* [[IBM Sterling B2B: Create a BP to get a file in IBM Cloud Object Storage (S3 storage)]]

* [[IBM Sterling B2B: Meu arquivo customer_overrides.properties]]

* [[IBM Sterling B2B: Limpeza de Arquivos]]

* [[IBM Sterling B2B: Limpeza de Tabelas e DataSweeper]]

* Reduce log level on B2B

* [[IBM Sterling B2B: Archive e Purge]]

* [[IBM Sterling B2B: Analisando Logs]]

* [[IBM Sterling B2B: Execução do HealthCheck]]

* [[IBM Sterling B2B: Troubleshooting problemas com CPU Alta]]

== Comandos, Dicas e Procedimentos ==

* [[IBM Sterling B2B: Dicas e Ajustes Rápidos]]

* [[IBM Sterling B2B: Execução de um Business Process via Linha de Comando]]

* [[IBM Sterling B2B: Criando Usuários no B2Bi usando o XAPI]]

* [[IBM Sterling B2B: Autenticando no B2Bi via LDAP (sem o SEAS)]]

* [[IBM Sterling: Configurando o Single Sign-on entre o SSP, SEAS, B2BI e SFG]]

* [[IBM Sterling B2B: Map Editor]]

* [[IBM Sterling B2B: Permissões e Controle de Acesso]]

* [[IBM Sterling B2B: Principais comandos no Docker]]

* [[IBM Sterling B2B: Check-in de uma chave pública SSH (SSH Known Host Key)]]

* [[IBM Sterling B2B: Configurando o SSL no IBM Sterling B2B Integrator]]

* [[IBM Sterling B2B: Configuring SSL in IBM Sterling B2B Integrator]]

== Integração Sterling B2Bi com Connect:Direct ==

Criei uma nomenclatura para facilitar a utilização do protocolo C:D no Sterling B2B

- Sterling B2B
|- Deployment > Service > Configuration > CD Server Adapter
- CDSA Name: SINODE01
- CD Node Name: SINODE01
- Server Port: 5364
- Netmap: SINODE01_NETMAP

|- Deployment > Adapter Utilities > Sterling C:D > Nodes
- CD Node Name: CDNODE01
- IP/Port: 192.x.x.1:1364
- CD Node Name: CDNODE02
- IP/Port: 192.x.x.1:2364

|- Deployment > Adapter Utilities > Sterling C:D > NetMap
- Netmap Name: SINODE01_NETMAP

|- Deployment > Adapter Utilities > Sterling C:D > NetMap +REF
- Netmap Name: SINODE01_NETMAP
- Add Node Name: CDNODE01
- Add Node Name: CDNODE02

- Connect:Direct --> CDNODE01
|- Netmap.cfg:
SINODE01:\
...
:comm.info=SINODE01;5364:\

* [[IBM Sterling B2B: Criando um Connect:Direct Server Adapter]]
* [[IBM Sterling B2B: Configurando a conexão do B2Bi-SFG para um Node C:D]]
* [[IBM Sterling Connect:Direct: Configurando a conexão para um Node C:D ou C:D Server Adapter]]

== SQL Queries ==

* [[IBM Sterling B2B: SELECT a Code List]]

* [[IBM Sterling B2B: SELECT Queue, Lifespan, PersistentLevel of Business Process]]

* [[IBM Sterling B2B: Useful Database Queries for Monitoring and Statistics]]

* [[IBM Sterling B2B: Queries for Archive]]

* [[IBM Sterling B2B: Queries for Certificates Management]]

* [[IBM Sterling B2B: Queries to collect locked sessions of Connect:Direct]]

== Instalação ==

* [[IBM Sterling B2B: Instalação usando Installation Manager - Node 1]]

* [[IBM Sterling B2B: Instalação para Node secundário de cluster]]

* [[IBM Sterling B2B: Install on Linux - Console]]

* [[IBM Sterling B2B: Install on Docker for Development]]

= Portas utilizadas pelo Sterling B2B=

Muito útil quando pedir liberação de firewall

* '''<base_port>''': definido durante a instalação. Costumo utilizar a porta 5000

[https://www.ibm.com/support/pages/node/176423 How does Gentran Integration Suite use the ports allocated during installation? (SCI90362)]

{| class="wikitable sortable"
|-
! Origem !! Destino !! Porta(s) !! Função
|-
| Web Browser || B2Bi/SFG || 5000 (http)<br>5001 (https) || Definido durante a instalação. Acesso ao Dashboard do B2Bi, Filegateway, MyFilegateway 2.0. Costumo utilizar a porta 5000, <base_port>(http)<br><base_port + 1>(https)
|-
| Cliente SFTP || B2Bi/SFG || 5022 || Definido na configuração do SFTP Server Adapter.Costumo utilizar a porta 5022.
|-
| Cliente FTP/FTPs || B2Bi/SFG || 5021 || Definido na configuração do FTP Server Adapter.Costumo utilizar a porta 5021.
|-
| Cliente HTTP(s) || B2Bi/SFG || * || Definido na configuração do HTTP Server Adapter.
|-
| Mapper || B2Bi/SFG || 5033(MAPTEST_HTTP_SERVER_PORT) || Map Test
|-
| SOAP Client || B2Bi/SFG || 5040(SOA_PORT)<br>5041(SOA_SSL_PORT) || Definido na configuração do SOAP/HTTP Server Adapter
|-
| Rest Client || B2Bi/SFG || 5060<br>5061(secure) || Definido na configuração do Rest/HTTP Server Adapter
|-
| B2Bi/SFG || Perimeter Server || <base_port + 2> || Definido na instalação do Perimeter Server
|-
| B2Bi/SFG || LDAP || 389 (ldap)<br>636 (ldaps)<br>3268 (MSAD) ||
|-
| B2Bi/SFG || DB2 || 50000 ||
|-
| B2Bi/SFG || Oracle || 1521 ||
|-
| Admin Console (Web Browser) || Control Center Monitor|| 58082 (http)<br>58083 (https) || Acesso ao Dashboard Web do Control Center
|-
| Control Center Console || Control Center Monitor|| 58080 <br>58081 (secure) || Acesso ao Control Center
|-
| Control Center Monitor || DB2 || 50000 ||
|-
| Control Center Monitor|| Oracle || 1521 ||
|-
| Control Center Director|| C:D Server || 1365 ||
|-
| Admin Console (Web Browser) || SEAS || 9080 || Acesso ao console de administração
|-
| Seas GUI || SEAS || 61365 <br>61366 (secure) ||
|-
| B2Bi/SFG || SEAS || 61365 <br>61366 (secure) ||
|-
| SSP Engine || SEAS || 61365 <br>61366 (secure) ||
|-
| SEAS || LDAP || 389 (ldap), 636 (ldaps) ||
|-
| Admin Console (Web Browser) || SSP Configuration Manager || 8443 || Example
|-
| SSP Configuration Manager || SSP Engine || 63366 || Example
|-
| Cliente SFTP || SSP Engine || * || Definido na configuração do SFTP Proxy Server Adapter
|-
| Cliente FTPs || SSP Engine || * || Definido na configuração do FTP Proxy Server Adapter
|-
| Cliente HTTP(s) || SSP Engine || * || Definido na configuração do HTTP Proxy Server Adapter
|-
| Cliente C:D || SSP Engine || * || Definido na configuração do Connect:Direct Proxy Server Adapter
|-
| C:D Cliente || C:D Server || 1363|| port to listen for a Client connection request
|-
| C:D Server || C:D Server || 1364 || port to listen for a remote connection request
|}

= Ver também =

* [[IBM Sterling| Artigos sobre IBM Sterling]]
* [[Tecnologias| Mais Artigos sobre Cloud / WebDev / Tecnologias]]

[[Category:IBM Sterling]]
[[Category:B2B]]
[[Category:B2B Integrator]]

IBM Maximo: Migration to Maximo Application Suite (MAS)

2026-05-08T14:32:54Z

Ebasso: /* Articles */

= Architectures=

* [https://github.com/MicrosoftDocs/architecture-center/blob/main/docs/example-scenario/apps/deploy-ibm-maximo-application-suite-content.md Azure: IBM Maximo]

* [https://www.ibm.com/docs/en/masv-and-l/cd?topic=overview-installation-topology AWS: IBM Maximo]

= Maximo Manage in MAS =

[[File:Maximo manage in mas.png]]

Source: https://www.ibm.com/docs/en/masv-and-l/cd?topic=manage-deploying

= Articles =

* [[IBM Maximo: Maximo Manage development environment without OpenShift]]

* [[IBM Maximo: Provide you customization_binaries.zip on OpenShift (Nginx)]]

* [[IBM Maximo: Provide you customization_binaries.zip on OpenShift (Apache HTTP)]]

= Ver também =

* [[Cloud| Artigos sobre Cloud]]
* [[Tecnologias| Mais Artigos sobre Cloud / WebDev / Tecnologias]]

[[Category:IBM Maximo]]

IBM Maximo: Migration to Maximo Application Suite (MAS)

2026-05-08T14:32:38Z

Ebasso: /* Articles */

= Architectures=

* [https://github.com/MicrosoftDocs/architecture-center/blob/main/docs/example-scenario/apps/deploy-ibm-maximo-application-suite-content.md Azure: IBM Maximo]

* [https://www.ibm.com/docs/en/masv-and-l/cd?topic=overview-installation-topology AWS: IBM Maximo]

= Maximo Manage in MAS =

[[File:Maximo manage in mas.png]]

Source: https://www.ibm.com/docs/en/masv-and-l/cd?topic=manage-deploying

= Articles =

* [[IBM Maximo: Maximo Manage development environment without OpenShift]]

* [[IBM Maximo: Provide you customization_binaries.zip on OpenShift (nginx)]]

* [[IBM Maximo: Provide you customization_binaries.zip on OpenShift (Apache HTTP)]]

= Ver também =

* [[Cloud| Artigos sobre Cloud]]
* [[Tecnologias| Mais Artigos sobre Cloud / WebDev / Tecnologias]]

[[Category:IBM Maximo]]

IBM Maximo: Provide you customization binaries.zip on OpenShift (Apache HTTP)

2026-05-08T14:27:15Z

Ebasso: /* OR Configure a Customization Archive in Manage Deployment via Red Hat OpenShift Console */

Uploading customization_binaries.zip directly to OpenShift simplifies deployment by avoiding external image builds and registries. It enables faster updates and avoid problem with security teams.

= Provide customization_binaries.zip in a custom container =

Start by creating a new project:

oc new-project httpd-customization-binaries

Create a file httpd-customization-binaries.yaml, with this content:

<nowiki>
---
apiVersion: v1
kind: ConfigMap
metadata:
name: httpd-index
namespace: httpd-customization-binaries
labels:
app: httpd-custom-bin
data:
index.html: |
<!DOCTYPE html>
<html>
<head>
<title>Maximo Customization Server</title>
</head>
<body>
<h1>Hello World!</h1>
<p>Maximo Customization Binaries Server</p>
</body>
</html>

---
apiVersion: apps/v1
kind: Deployment
metadata:
name: httpd-custom-bin
namespace: httpd-customization-binaries
labels:
app: httpd-custom-bin
spec:
replicas: 1
selector:
matchLabels:
app: httpd-custom-bin
template:
metadata:
labels:
app: httpd-custom-bin
spec:
securityContext:
runAsNonRoot: true
seccompProfile:
type: RuntimeDefault

volumes:
- name: index-html
configMap:
name: httpd-index
defaultMode: 0644
- name: html-data
emptyDir: {}

containers:
- name: httpd
image: image-registry.openshift-image-registry.svc:5000/openshift/httpd:latest

ports:
- name: http
containerPort: 8080
protocol: TCP

volumeMounts:
- name: html-data
mountPath: /var/www/html
- name: index-html
mountPath: /var/www/html/index.html
subPath: index.html

securityContext:
allowPrivilegeEscalation: false
capabilities:
drop:
- ALL

resources:
requests:
memory: "128Mi"
cpu: "100m"
limits:
memory: "256Mi"
cpu: "200m"

livenessProbe:
httpGet:
path: /
port: 8080
initialDelaySeconds: 30
periodSeconds: 10

readinessProbe:
httpGet:
path: /
port: 8080
initialDelaySeconds: 5
periodSeconds: 5

---
apiVersion: v1
kind: Service
metadata:
name: httpd-custom-bin
namespace: httpd-customization-binaries
labels:
app: httpd-custom-bin
spec:
type: ClusterIP
selector:
app: httpd-custom-bin
ports:
- name: http
port: 8080
targetPort: 8080
protocol: TCP
sessionAffinity: None

---
apiVersion: route.openshift.io/v1
kind: Route
metadata:
name: httpd-custom-bin
namespace: httpd-customization-binaries
labels:
app: httpd-custom-bin
spec:
to:
kind: Service
name: httpd-custom-bin
weight: 100

port:
targetPort: http

wildcardPolicy: None
</nowiki>

Create a New App Using the NGINX Template

oc apply –f httpd-customization-binaries.yaml

Check the Pod Name

Look for the pod name that starts with nginx-custom-. You’ll need this for the next step.

Upload custominization_binaries.zip

oc cp customization_binaries.zip <pod-name>:/var/www/html/customization_binaries.zip

Check the Route to Access Your App

oc get routes

This will show the external URL where your custom HTTPD content is being served.

Try to download on your machine, appending customization_binaries.zip. Like:

<nowiki>http://xxxxxx/customization_binaries.zip</nowiki>

don't use https!!!

= Configure Customization Archive on IBM Maximo Application Suite Dashboard =

Access the Admin UI in IBM Maximo Application Suite:

1. Navigate to Catalog -> Manage:

2. Navigate to Actions -> Update Configuration:

3. Scroll down to Customization and click Edit:

4. Under Customization section, uncheck System Managed option then paste the URL to the customization archive:

<nowiki>http://httpd-custom-bin.httpd-customization-binaries.svc:8080/custominization_binaries.zip</nowiki>

where address is <service>.<namespace>.svc:<port>, internal access to service

5. Scroll up and click Apply Changes:

6. In the OCP Console, head to Workloads -> Pods, then filter by the mas-<MAS NAME>-manage project. You should see a new pod called admin-build-config-x-build being created:

7. Click the build pod, then select Logs tab

Wait for Complete

= OR Configure a Customization Archive in Manage Deployment via Red Hat OpenShift Console =

These steps explain how to configure a customization archive directly in a Manage Workspace instance, instead of using the MAS Admin UI console.

1. Log in to the OpenShift Console

2. Navigate to Administration > CustomResourceDefinitions, then search for and select ManageWorkspace.

3. Choose the ManageWorkspace instance associated with your MAS deployment.

4. Edit the YAML Configuration

Go to the YAML tab and append the customizationList property under spec.settings. This should include:

* customizationArchiveName: a name for your archive
* customizationArchiveUrl: the URL or path to your archive file

Example:

<small><nowiki>spec:
settings:
customizationList:
- customizationArchiveName: my-custom-archive
customizationArchiveUrl: http://httpd-custom-bin.httpd-customization-binaries.svc:8080/customization_binaries.zip</nowiki></small>

5. Save the YAML File

Once saved, the Manage deployment process will automatically reconcile and apply the new customization archive. This may take several minutes depending on the archive size. The Manage application servers will restart during this process, so plan for a potential downtime window.

= Ver também =

* [[Cloud| Artigos sobre Cloud]]
* [[Tecnologias| Mais Artigos sobre Cloud / WebDev / Tecnologias]]

[[Category:IBM Maximo]]

IBM Maximo: Provide you customization binaries.zip on OpenShift (Apache HTTP)

2026-05-08T14:26:59Z

Ebasso: /* OR Configure a Customization Archive in Manage Deployment via Red Hat OpenShift Console */

Uploading customization_binaries.zip directly to OpenShift simplifies deployment by avoiding external image builds and registries. It enables faster updates and avoid problem with security teams.

= Provide customization_binaries.zip in a custom container =

Start by creating a new project:

oc new-project httpd-customization-binaries

Create a file httpd-customization-binaries.yaml, with this content:

<nowiki>
---
apiVersion: v1
kind: ConfigMap
metadata:
name: httpd-index
namespace: httpd-customization-binaries
labels:
app: httpd-custom-bin
data:
index.html: |
<!DOCTYPE html>
<html>
<head>
<title>Maximo Customization Server</title>
</head>
<body>
<h1>Hello World!</h1>
<p>Maximo Customization Binaries Server</p>
</body>
</html>

---
apiVersion: apps/v1
kind: Deployment
metadata:
name: httpd-custom-bin
namespace: httpd-customization-binaries
labels:
app: httpd-custom-bin
spec:
replicas: 1
selector:
matchLabels:
app: httpd-custom-bin
template:
metadata:
labels:
app: httpd-custom-bin
spec:
securityContext:
runAsNonRoot: true
seccompProfile:
type: RuntimeDefault

volumes:
- name: index-html
configMap:
name: httpd-index
defaultMode: 0644
- name: html-data
emptyDir: {}

containers:
- name: httpd
image: image-registry.openshift-image-registry.svc:5000/openshift/httpd:latest

ports:
- name: http
containerPort: 8080
protocol: TCP

volumeMounts:
- name: html-data
mountPath: /var/www/html
- name: index-html
mountPath: /var/www/html/index.html
subPath: index.html

securityContext:
allowPrivilegeEscalation: false
capabilities:
drop:
- ALL

resources:
requests:
memory: "128Mi"
cpu: "100m"
limits:
memory: "256Mi"
cpu: "200m"

livenessProbe:
httpGet:
path: /
port: 8080
initialDelaySeconds: 30
periodSeconds: 10

readinessProbe:
httpGet:
path: /
port: 8080
initialDelaySeconds: 5
periodSeconds: 5

---
apiVersion: v1
kind: Service
metadata:
name: httpd-custom-bin
namespace: httpd-customization-binaries
labels:
app: httpd-custom-bin
spec:
type: ClusterIP
selector:
app: httpd-custom-bin
ports:
- name: http
port: 8080
targetPort: 8080
protocol: TCP
sessionAffinity: None

---
apiVersion: route.openshift.io/v1
kind: Route
metadata:
name: httpd-custom-bin
namespace: httpd-customization-binaries
labels:
app: httpd-custom-bin
spec:
to:
kind: Service
name: httpd-custom-bin
weight: 100

port:
targetPort: http

wildcardPolicy: None
</nowiki>

Create a New App Using the NGINX Template

oc apply –f httpd-customization-binaries.yaml

Check the Pod Name

Look for the pod name that starts with nginx-custom-. You’ll need this for the next step.

Upload custominization_binaries.zip

oc cp customization_binaries.zip <pod-name>:/var/www/html/customization_binaries.zip

Check the Route to Access Your App

oc get routes

This will show the external URL where your custom HTTPD content is being served.

Try to download on your machine, appending customization_binaries.zip. Like:

<nowiki>http://xxxxxx/customization_binaries.zip</nowiki>

don't use https!!!

= Configure Customization Archive on IBM Maximo Application Suite Dashboard =

Access the Admin UI in IBM Maximo Application Suite:

1. Navigate to Catalog -> Manage:

2. Navigate to Actions -> Update Configuration:

3. Scroll down to Customization and click Edit:

4. Under Customization section, uncheck System Managed option then paste the URL to the customization archive:

<nowiki>http://httpd-custom-bin.httpd-customization-binaries.svc:8080/custominization_binaries.zip</nowiki>

where address is <service>.<namespace>.svc:<port>, internal access to service

5. Scroll up and click Apply Changes:

6. In the OCP Console, head to Workloads -> Pods, then filter by the mas-<MAS NAME>-manage project. You should see a new pod called admin-build-config-x-build being created:

7. Click the build pod, then select Logs tab

Wait for Complete

= OR Configure a Customization Archive in Manage Deployment via Red Hat OpenShift Console =

These steps explain how to configure a customization archive directly in a Manage Workspace instance, instead of using the MAS Admin UI console.

1. Log in to the OpenShift Console

2. Navigate to Administration > CustomResourceDefinitions, then search for and select ManageWorkspace.

3. Choose the ManageWorkspace instance associated with your MAS deployment.

4. Edit the YAML Configuration

Go to the YAML tab and append the customizationList property under spec.settings. This should include:

* customizationArchiveName: a name for your archive
* customizationArchiveUrl: the URL or path to your archive file

Example:

<nowiki>spec:
settings:
customizationList:
- customizationArchiveName: my-custom-archive
customizationArchiveUrl: http://httpd-custom-bin.httpd-customization-binaries.svc:8080/customization_binaries.zip</nowiki>

5. Save the YAML File

Once saved, the Manage deployment process will automatically reconcile and apply the new customization archive. This may take several minutes depending on the archive size. The Manage application servers will restart during this process, so plan for a potential downtime window.

= Ver também =

* [[Cloud| Artigos sobre Cloud]]
* [[Tecnologias| Mais Artigos sobre Cloud / WebDev / Tecnologias]]

[[Category:IBM Maximo]]

IBM Maximo: Provide you customization binaries.zip on OpenShift (Apache HTTP)

2026-05-08T14:26:05Z

Ebasso: /* Configure Customization Archive on IBM Maximo Application Suite Dashboard */

Uploading customization_binaries.zip directly to OpenShift simplifies deployment by avoiding external image builds and registries. It enables faster updates and avoid problem with security teams.

= Provide customization_binaries.zip in a custom container =

Start by creating a new project:

oc new-project httpd-customization-binaries

Create a file httpd-customization-binaries.yaml, with this content:

<nowiki>
---
apiVersion: v1
kind: ConfigMap
metadata:
name: httpd-index
namespace: httpd-customization-binaries
labels:
app: httpd-custom-bin
data:
index.html: |
<!DOCTYPE html>
<html>
<head>
<title>Maximo Customization Server</title>
</head>
<body>
<h1>Hello World!</h1>
<p>Maximo Customization Binaries Server</p>
</body>
</html>

---
apiVersion: apps/v1
kind: Deployment
metadata:
name: httpd-custom-bin
namespace: httpd-customization-binaries
labels:
app: httpd-custom-bin
spec:
replicas: 1
selector:
matchLabels:
app: httpd-custom-bin
template:
metadata:
labels:
app: httpd-custom-bin
spec:
securityContext:
runAsNonRoot: true
seccompProfile:
type: RuntimeDefault

volumes:
- name: index-html
configMap:
name: httpd-index
defaultMode: 0644
- name: html-data
emptyDir: {}

containers:
- name: httpd
image: image-registry.openshift-image-registry.svc:5000/openshift/httpd:latest

ports:
- name: http
containerPort: 8080
protocol: TCP

volumeMounts:
- name: html-data
mountPath: /var/www/html
- name: index-html
mountPath: /var/www/html/index.html
subPath: index.html

securityContext:
allowPrivilegeEscalation: false
capabilities:
drop:
- ALL

resources:
requests:
memory: "128Mi"
cpu: "100m"
limits:
memory: "256Mi"
cpu: "200m"

livenessProbe:
httpGet:
path: /
port: 8080
initialDelaySeconds: 30
periodSeconds: 10

readinessProbe:
httpGet:
path: /
port: 8080
initialDelaySeconds: 5
periodSeconds: 5

---
apiVersion: v1
kind: Service
metadata:
name: httpd-custom-bin
namespace: httpd-customization-binaries
labels:
app: httpd-custom-bin
spec:
type: ClusterIP
selector:
app: httpd-custom-bin
ports:
- name: http
port: 8080
targetPort: 8080
protocol: TCP
sessionAffinity: None

---
apiVersion: route.openshift.io/v1
kind: Route
metadata:
name: httpd-custom-bin
namespace: httpd-customization-binaries
labels:
app: httpd-custom-bin
spec:
to:
kind: Service
name: httpd-custom-bin
weight: 100

port:
targetPort: http

wildcardPolicy: None
</nowiki>

Create a New App Using the NGINX Template

oc apply –f httpd-customization-binaries.yaml

Check the Pod Name

Look for the pod name that starts with nginx-custom-. You’ll need this for the next step.

Upload custominization_binaries.zip

oc cp customization_binaries.zip <pod-name>:/var/www/html/customization_binaries.zip

Check the Route to Access Your App

oc get routes

This will show the external URL where your custom HTTPD content is being served.

Try to download on your machine, appending customization_binaries.zip. Like:

<nowiki>http://xxxxxx/customization_binaries.zip</nowiki>

don't use https!!!

= Configure Customization Archive on IBM Maximo Application Suite Dashboard =

Access the Admin UI in IBM Maximo Application Suite:

1. Navigate to Catalog -> Manage:

2. Navigate to Actions -> Update Configuration:

3. Scroll down to Customization and click Edit:

4. Under Customization section, uncheck System Managed option then paste the URL to the customization archive:

<nowiki>http://httpd-custom-bin.httpd-customization-binaries.svc:8080/custominization_binaries.zip</nowiki>

where address is <service>.<namespace>.svc:<port>, internal access to service

5. Scroll up and click Apply Changes:

6. In the OCP Console, head to Workloads -> Pods, then filter by the mas-<MAS NAME>-manage project. You should see a new pod called admin-build-config-x-build being created:

7. Click the build pod, then select Logs tab

Wait for Complete

= OR Configure a Customization Archive in Manage Deployment via Red Hat OpenShift Console =

These steps explain how to configure a customization archive directly in a Manage Workspace instance, instead of using the MAS Admin UI console.

1. Log in to the OpenShift Console

2. Navigate to Administration > CustomResourceDefinitions, then search for and select ManageWorkspace.

3. Choose the ManageWorkspace instance associated with your MAS deployment.

4. Edit the YAML Configuration

Go to the YAML tab and append the customizationList property under spec.settings. This should include:

* customizationArchiveName: a name for your archive
* customizationArchiveUrl: the URL or path to your archive file

Example:

<nowiki>spec:
settings:
customizationList:
- customizationArchiveName: my-custom-archive
customizationArchiveUrl: https://example.com/customization_binaries.zip</nowiki>

5. Save the YAML File

Once saved, the Manage deployment process will automatically reconcile and apply the new customization archive. This may take several minutes depending on the archive size. The Manage application servers will restart during this process, so plan for a potential downtime window.

= Ver também =

* [[Cloud| Artigos sobre Cloud]]
* [[Tecnologias| Mais Artigos sobre Cloud / WebDev / Tecnologias]]

[[Category:IBM Maximo]]

IBM Maximo: Provide you customization binaries.zip on OpenShift (Apache HTTP)

2026-05-08T14:23:36Z

Ebasso: /* Configure Customization Archive on IBM Maximo Application Suite Dashboard */

Uploading customization_binaries.zip directly to OpenShift simplifies deployment by avoiding external image builds and registries. It enables faster updates and avoid problem with security teams.

= Provide customization_binaries.zip in a custom container =

Start by creating a new project:

oc new-project httpd-customization-binaries

Create a file httpd-customization-binaries.yaml, with this content:

<nowiki>
---
apiVersion: v1
kind: ConfigMap
metadata:
name: httpd-index
namespace: httpd-customization-binaries
labels:
app: httpd-custom-bin
data:
index.html: |
<!DOCTYPE html>
<html>
<head>
<title>Maximo Customization Server</title>
</head>
<body>
<h1>Hello World!</h1>
<p>Maximo Customization Binaries Server</p>
</body>
</html>

---
apiVersion: apps/v1
kind: Deployment
metadata:
name: httpd-custom-bin
namespace: httpd-customization-binaries
labels:
app: httpd-custom-bin
spec:
replicas: 1
selector:
matchLabels:
app: httpd-custom-bin
template:
metadata:
labels:
app: httpd-custom-bin
spec:
securityContext:
runAsNonRoot: true
seccompProfile:
type: RuntimeDefault

volumes:
- name: index-html
configMap:
name: httpd-index
defaultMode: 0644
- name: html-data
emptyDir: {}

containers:
- name: httpd
image: image-registry.openshift-image-registry.svc:5000/openshift/httpd:latest

ports:
- name: http
containerPort: 8080
protocol: TCP

volumeMounts:
- name: html-data
mountPath: /var/www/html
- name: index-html
mountPath: /var/www/html/index.html
subPath: index.html

securityContext:
allowPrivilegeEscalation: false
capabilities:
drop:
- ALL

resources:
requests:
memory: "128Mi"
cpu: "100m"
limits:
memory: "256Mi"
cpu: "200m"

livenessProbe:
httpGet:
path: /
port: 8080
initialDelaySeconds: 30
periodSeconds: 10

readinessProbe:
httpGet:
path: /
port: 8080
initialDelaySeconds: 5
periodSeconds: 5

---
apiVersion: v1
kind: Service
metadata:
name: httpd-custom-bin
namespace: httpd-customization-binaries
labels:
app: httpd-custom-bin
spec:
type: ClusterIP
selector:
app: httpd-custom-bin
ports:
- name: http
port: 8080
targetPort: 8080
protocol: TCP
sessionAffinity: None

---
apiVersion: route.openshift.io/v1
kind: Route
metadata:
name: httpd-custom-bin
namespace: httpd-customization-binaries
labels:
app: httpd-custom-bin
spec:
to:
kind: Service
name: httpd-custom-bin
weight: 100

port:
targetPort: http

wildcardPolicy: None
</nowiki>

Create a New App Using the NGINX Template

oc apply –f httpd-customization-binaries.yaml

Check the Pod Name

Look for the pod name that starts with nginx-custom-. You’ll need this for the next step.

Upload custominization_binaries.zip

oc cp customization_binaries.zip <pod-name>:/var/www/html/customization_binaries.zip

Check the Route to Access Your App

oc get routes

This will show the external URL where your custom HTTPD content is being served.

Try to download on your machine, appending customization_binaries.zip. Like:

<nowiki>http://xxxxxx/customization_binaries.zip</nowiki>

don't use https!!!

= Configure Customization Archive on IBM Maximo Application Suite Dashboard =

Access the Admin UI in IBM Maximo Application Suite:

1. Navigate to Catalog -> Manage:

2. Navigate to Actions -> Update Configuration:

3. Scroll down to Customization and click Edit:

4. Under Customization section, uncheck System Managed option then paste the URL to the customization archive:

<nowiki>http://xxxxxx/custominization_binaries.zip</nowiki>

5. Scroll up and click Apply Changes:

6. In the OCP Console, head to Workloads -> Pods, then filter by the mas-<MAS NAME>-manage project. You should see a new pod called admin-build-config-x-build being created:

7. Click the build pod, then select Logs tab

Wait for Complete

= OR Configure a Customization Archive in Manage Deployment via Red Hat OpenShift Console =

These steps explain how to configure a customization archive directly in a Manage Workspace instance, instead of using the MAS Admin UI console.

1. Log in to the OpenShift Console

2. Navigate to Administration > CustomResourceDefinitions, then search for and select ManageWorkspace.

3. Choose the ManageWorkspace instance associated with your MAS deployment.

4. Edit the YAML Configuration

Go to the YAML tab and append the customizationList property under spec.settings. This should include:

* customizationArchiveName: a name for your archive
* customizationArchiveUrl: the URL or path to your archive file

Example:

<nowiki>spec:
settings:
customizationList:
- customizationArchiveName: my-custom-archive
customizationArchiveUrl: https://example.com/customization_binaries.zip</nowiki>

5. Save the YAML File

Once saved, the Manage deployment process will automatically reconcile and apply the new customization archive. This may take several minutes depending on the archive size. The Manage application servers will restart during this process, so plan for a potential downtime window.

= Ver também =

* [[Cloud| Artigos sobre Cloud]]
* [[Tecnologias| Mais Artigos sobre Cloud / WebDev / Tecnologias]]

[[Category:IBM Maximo]]

IBM Maximo: Provide you customization binaries.zip on OpenShift (Apache HTTP)

2026-05-08T14:22:58Z

Ebasso: Created page with "Uploading customization_binaries.zip directly to OpenShift simplifies deployment by avoiding external image builds and registries. It enables faster updates and avoid problem with security teams. = Provide customization_binaries.zip in a custom container = Start by creating a new project: oc new-project httpd-customization-binaries Create a file httpd-customization-binaries.yaml, with this content: <nowiki> --- apiVersion: v1 kind: ConfigMap metadata: name: htt..."

Uploading customization_binaries.zip directly to OpenShift simplifies deployment by avoiding external image builds and registries. It enables faster updates and avoid problem with security teams.

= Provide customization_binaries.zip in a custom container =

Start by creating a new project:

oc new-project httpd-customization-binaries

Create a file httpd-customization-binaries.yaml, with this content:

<nowiki>
---
apiVersion: v1
kind: ConfigMap
metadata:
name: httpd-index
namespace: httpd-customization-binaries
labels:
app: httpd-custom-bin
data:
index.html: |
<!DOCTYPE html>
<html>
<head>
<title>Maximo Customization Server</title>
</head>
<body>
<h1>Hello World!</h1>
<p>Maximo Customization Binaries Server</p>
</body>
</html>

---
apiVersion: apps/v1
kind: Deployment
metadata:
name: httpd-custom-bin
namespace: httpd-customization-binaries
labels:
app: httpd-custom-bin
spec:
replicas: 1
selector:
matchLabels:
app: httpd-custom-bin
template:
metadata:
labels:
app: httpd-custom-bin
spec:
securityContext:
runAsNonRoot: true
seccompProfile:
type: RuntimeDefault

volumes:
- name: index-html
configMap:
name: httpd-index
defaultMode: 0644
- name: html-data
emptyDir: {}

containers:
- name: httpd
image: image-registry.openshift-image-registry.svc:5000/openshift/httpd:latest

ports:
- name: http
containerPort: 8080
protocol: TCP

volumeMounts:
- name: html-data
mountPath: /var/www/html
- name: index-html
mountPath: /var/www/html/index.html
subPath: index.html

securityContext:
allowPrivilegeEscalation: false
capabilities:
drop:
- ALL

resources:
requests:
memory: "128Mi"
cpu: "100m"
limits:
memory: "256Mi"
cpu: "200m"

livenessProbe:
httpGet:
path: /
port: 8080
initialDelaySeconds: 30
periodSeconds: 10

readinessProbe:
httpGet:
path: /
port: 8080
initialDelaySeconds: 5
periodSeconds: 5

---
apiVersion: v1
kind: Service
metadata:
name: httpd-custom-bin
namespace: httpd-customization-binaries
labels:
app: httpd-custom-bin
spec:
type: ClusterIP
selector:
app: httpd-custom-bin
ports:
- name: http
port: 8080
targetPort: 8080
protocol: TCP
sessionAffinity: None

---
apiVersion: route.openshift.io/v1
kind: Route
metadata:
name: httpd-custom-bin
namespace: httpd-customization-binaries
labels:
app: httpd-custom-bin
spec:
to:
kind: Service
name: httpd-custom-bin
weight: 100

port:
targetPort: http

wildcardPolicy: None
</nowiki>

Create a New App Using the NGINX Template

oc apply –f httpd-customization-binaries.yaml

Check the Pod Name

Look for the pod name that starts with nginx-custom-. You’ll need this for the next step.

Upload custominization_binaries.zip

oc cp customization_binaries.zip <pod-name>:/var/www/html/customization_binaries.zip

Check the Route to Access Your App

oc get routes

This will show the external URL where your custom HTTPD content is being served.

Try to download on your machine, appending customization_binaries.zip. Like:

<nowiki>http://xxxxxx/customization_binaries.zip</nowiki>

don't use https!!!

= Configure Customization Archive on IBM Maximo Application Suite Dashboard =

Access the Admin UI in IBM Maximo Application Suite: e.g.: '''<nowiki>https://admin.apps.<CLUSTER NAME></nowiki>'''

1. Navigate to Catalog -> Manage:

2. Navigate to Actions -> Update Configuration:

3. Scroll down to Customization and click Edit:

4. Under Customization section, uncheck System Managed option then paste the URL to the customization archive:

<nowiki>http://xxxxxx/custominization_binaries.zip</nowiki>

5. Scroll up and click Apply Changes:

6. In the OCP Console, head to Workloads -> Pods, then filter by the mas-<MAS NAME>-manage project. You should see a new pod called admin-build-config-x-build being created:

7. Click the build pod, then select Logs tab

Wait for Complete

= OR Configure a Customization Archive in Manage Deployment via Red Hat OpenShift Console =

These steps explain how to configure a customization archive directly in a Manage Workspace instance, instead of using the MAS Admin UI console.

1. Log in to the OpenShift Console

2. Navigate to Administration > CustomResourceDefinitions, then search for and select ManageWorkspace.

3. Choose the ManageWorkspace instance associated with your MAS deployment.

4. Edit the YAML Configuration

Go to the YAML tab and append the customizationList property under spec.settings. This should include:

* customizationArchiveName: a name for your archive
* customizationArchiveUrl: the URL or path to your archive file

Example:

<nowiki>spec:
settings:
customizationList:
- customizationArchiveName: my-custom-archive
customizationArchiveUrl: https://example.com/customization_binaries.zip</nowiki>

5. Save the YAML File

Once saved, the Manage deployment process will automatically reconcile and apply the new customization archive. This may take several minutes depending on the archive size. The Manage application servers will restart during this process, so plan for a potential downtime window.

= Ver também =

* [[Cloud| Artigos sobre Cloud]]
* [[Tecnologias| Mais Artigos sobre Cloud / WebDev / Tecnologias]]

[[Category:IBM Maximo]]

IBM Maximo

2026-05-08T14:17:32Z

Ebasso: /* Migration to Maximo Application Suite (MAS) */

O IBM Maximo é um pacote de software de gerenciamento de ativos corporativos (EAM) oferecido pela IBM. O IBM Maximo fornece monitoramento de ativos remotos, manutenção e aplicativos de confiabilidade em uma única plataforma que permite aumentar o tempo de atividade, melhorar a produtividade, reduzir os custos de manutenção e construir operações mais resilientes.

Com sua versão mais recente, o Maximo Application Suite (MAS), o sistema oferece vários aplicativos:

{| class="wikitable"
|-
! Produto !! Descrição
|-
| Maximo Application Suite (MAS) ||
Composto por vários aplicativos, o produto ao qual a maioria dos usuários se refere como Maximo agora é chamado de “MAM”.
|-
| [[IBM Maximo: MAS Manage|MAS Manage]] ||
O MAS Manage foi projetado para reduzir o tempo de inatividade e os custos, otimizando o gerenciamento de ativos e os processos de manutenção para melhorar o desempenho operacional. O seu uso podem alavancar a experiência da indústria incorporada com modelos de dados de práticas recomendadas e fluxos de trabalho para acelerar a transformação da indústria. O MAM unifica o ciclo de vida do ativo e as atividades de gerenciamento de manutenção, fornecendo uma visão de todos os ativos, condições e processos de trabalho da empresa para obter um melhor planejamento e controle.
|-
| [[IBM Maximo Visual Inspection|Maximo Visual Inspection (MVI)]] ||
O MVI é uma plataforma de analise de imagens e videos, que permite criar modelos de Machine Learning
|-
| Maximo Monitor ||
Melhore a disponibilidade operacional e de ativos com monitoramento remoto avançado de ativos com Inteligência Artificial (IA) em escala. Os usuários podem coletar dados de seus sistemas OT existentes e convergir sistemas de TI e sistemas operacionais em um único data lake para detectar anomalias.
|-
| Maximo Health ||
Gerenciar o funcionamento de ativos usando dados IoT de sensores de ativos, registros de ativos e histórico de trabalho para aumentar a disponibilidade de ativos e melhorar o planejamento de substituição é o objetivo principal deste aplicativo. Ele fornece uma visualização do funcionamento do ativo por meio de exibições de painel para fornecer evidências para basear as decisões operacionais.
|-
| Maximo Predict ||
Em vez de reagir, o Predict fornece a capacidade de usar ações baseadas em condições para prever a probabilidade de falhas futuras aplicando aprendizado de máquina e análise de dados para reduzir custos e falhas de ativos. Com base no poder de outros recursos do Maximo, os usuários podem tomar decisões baseadas em dados e construir modelos preditivos.
|}

= Artigos e Blogs =

= Migration to Maximo Application Suite (MAS) =

* [[IBM Maximo: Install Maximo Application Suite using MAS CLI]]
** [[IBM Maximo: MAS CLI Options]]
** [[IBM Maximo: Installing MAS Core + Manage + DB2 Container]]
** [[IBM Maximo: Installing MAS Core + Manage + Oracle DB Container]]

* [[IBM Maximo: Migrate MAXDB to RH OpenShift (DB2 Version)]]

* [[IBM Maximo: Steps to Upgrade a Maximo 7.6 Database to MAS 9 after MAS Installation]]

* [[IBM Maximo: Disconnecting MAS Manage from the database for DB Maintenance]]

* [[IBM Maximo: Provide you customization_binaries.zip on OpenShift (Nginx)]]

* [[IBM Maximo: Provide you customization_binaries.zip on OpenShift (Apache HTTP)]]

* [[IBM Maximo: Migration to Maximo Application Suite (MAS)]]

* [[IBM Maximo: Creating Maximo Database on Oracle Database Free Edition (Container)]]

* [[IBM Maximo: Deploying Kafka after Maximo Manage]]

= Referencias =
* Blog: [https://bportaluri.com/blog Bruno Portaluri]
** [https://bportaluri.com/2021/10/maximo-bulk-update-list-view.html Atualização de uma lista - bulk update ]
* Blog: [https://maximosecrets.com Maximo Secrets]
* Yasutaka Nishimura
**[https://www.linkedin.com/pulse/apache-kafka-message-provider-maximo-yasutaka-nishimura/ Apache Kafka as a Message Provider in Maximo]
**[https://www.linkedin.com/pulse/custom-autoscript-end-point-realizes-access-oauth2-yasutaka-nishimura/ Custom autoscript end point realizes to access OAuth2 protected resources]
**[https://www.linkedin.com/pulse/running-maximo-manage-stand-alone-openshift-server-red-nishimura/ Running Maximo Manage on stand-alone OpenShift server with Red Hat Code Ready Containers]
**[https://www.linkedin.com/pulse/send-notifications-slack-via-maximo-integration-yasutaka-nishimura/ Send notifications to Slack via Maximo Integration Framework]

= API Rest, Documentação, Artigos e Exemplos =

* [[IBM Maximo: Maximo Manage development environment without OpenShift]]

* [[IBM Maximo: Dicas de APIs Rest]]

* [[IBM Maximo: Automation Scripts]]

* '''maximomize.com''': [https://www.maximomize.com/writing-your-first-crontask-for-maximo-in-jython Writing your first crontask for Maximo in Jython]
* '''maximomize.com''': [https://www.maximomize.com/writing-your-first-crontask-for-maximo-in-java Writing your First CronTask for Maximo in Java]
* '''a3jgroup.com''': [https://a3jgroup.com/run-an-automation-script-from-a-cron-task-in-maximo/ Run an Automation Script from a Cron Task in Maximo]

= Performance and Best Practice =

* Best Practice: [[IBM Maximo: My Configuration Tips]]

* Best Practice: [[IBM Maximo: SQL Queries - CRONTASKS & ESCALATIONS]] - Dica de Configuração de Performance

* Best Practice: [[IBM Maximo: Cleanup of Start Center]] - Dica de Manutenção de Performance

* Best Practice: [[IBM Maximo: Integrity Check Tool]] - Reporting data integrity issues

* Best Practice: [[IBM Maximo: Resizing JPEG Files in doclinks]]

* [[IBM Maximo: Identificar SQLs de longa duração]]
* [[IBM Maximo: Java Virtual Machine Properties for IBM WebSphere]
* [[IBM Maximo: System Properties para Monitor e diagnosticar problemas de Performance]]
* [[IBM Maximo: System Properties]]
* [[IBM Maximo: Isolar a Funcionalidade do Servidor]]
* [[IBM Maximo: Analisando a crontask PMWoGenCronTask]]

== SQL Queries ==

* [[IBM Maximo: SQL Queries]]
* [[IBM Maximo: SQL Queries - CRONTASKS & ESCALATIONS]]
* [[IBM Maximo: SQL Queries - WORKFLOW]]

* [[IBM Maximo: Identificar SQLs de longa duração]]
* [[IBM Maximo: Monitorar o número de DB Connections]]
* [[IBM Maximo: Tabelas que contêm consultas para revisar]]
* [[IBM Maximo: System Properties]]
* [[IBM Maximo: BMXAA6720W - Slow SQL Entries]]
* [[IBM Maximo: Exportando um relatório (BIRT) do banco de dados do Maximo]]
* [[IBM Maximo: Listar a quantidade de logins únicos por dia]]

=== Outras Tabelas ===
* [[IBM Maximo: SQL Queries - tabela CRONTASKHISTORY]]
* [[IBM Maximo: SQL Queries - tabela ESCREPEATTRACK]]
* [[IBM Maximo: SQL Queries - tabela ESCSTATUS]]
* [[IBM Maximo: SQL Queries - tabela LOGINTRACK]]
* [[IBM Maximo: SQL Queries - tabela QUERY]]
* [[IBM Maximo: SQL Queries - tabela WFINSTANCE]]

= Mensagens BMXAA =

* [[IBM Maximo: BMXAA6720W - Slow SQL Entries]]

* [[IBM Maximo: BMXAA4038E - Cannot log in to perform this action on Forgot Password link]]

= Instalação e Configuração Maximo EAM =

* [[IBM Maximo: Instalação do Maximo EAM no Linux via Linha de Comando]]
* [[IBM Maximo: Verificando pré-requisitos de instalação e upgrade do Maximo EAM]]

* [[IBM Maximo: Running Maximo EAM as Container]]

* [[IBM Maximo: Criando a database manualmente para o Maximo]]
* [[IBM Maximo: Criando as filas JMS Queues manualmente para o Maximo EAM]]
* [[IBM Maximo: Criando as filas JMS Queues via linha de comando para o Maximo EAM]]

= Relatórios =

* [[IBM Maximo: Exportando um relatório (BIRT) do banco de dados do Maximo]]
* [https://www.ibm.com/support/pages/maximo-76-report-booklet Lista de Relatórios do Maximo 7.6 (BIRT)]
* [https://www.ibm.com/support/pages/maximo-76designer-431-report-development-guide Guia de Desenvolvimento de Relatórios do Maximo 7.6 (BIRT)]
* [https://www.ibm.com/support/pages/maximo-76-reporting-options-and-comparisons Reporting Options and Comparisons (BIRT)]
* [https://www.ibm.com/support/pages/maximo-cognos-content-bi-packs Lista de Relatórios Cognos "Maximo Cognos Content - BI Packs" (Cognos)]
* [https://www.ibm.com/support/pages/maximo-76-cognos-feature-guide Maximo 76 Cognos Feature Guide]

= Ver também =

* [[Cloud| Artigos sobre Cloud]]
* [[Tecnologias| Mais Artigos sobre Cloud / WebDev / Tecnologias]]

[[Category:IBM Maximo]]

IBM Maximo: Provide you customization binaries.zip on OpenShift

2026-05-08T14:16:54Z

Ebasso: Ebasso moved page IBM Maximo: Provide you customization binaries.zip on OpenShift to IBM Maximo: Provide you customization binaries.zip on OpenShift (Nginx)

#REDIRECT [[IBM Maximo: Provide you customization binaries.zip on OpenShift (Nginx)]]

IBM Maximo: Provide you customization binaries.zip on OpenShift (Nginx)

2026-05-08T14:16:54Z

Ebasso: Ebasso moved page IBM Maximo: Provide you customization binaries.zip on OpenShift to IBM Maximo: Provide you customization binaries.zip on OpenShift (Nginx)

IBM Sterling Connect:Direct : Silent Install

2026-05-06T19:09:03Z

Ebasso: /* Install */

Updated to 6.4.0.5

= Extract installer =

mkdir /Binaries/CD

tar -xvf 6.4.0.5-IBMSterlingConnectDirectforUNIX-Linux-x86-iFix007.tar

will extract files cdinstall, cdinstall_a, cdunix.

= Install =

1) Generate Certificate

openssl req -x509 -nodes -days 3650 -newkey rsa:4096 -sha512 -subj "/CN=CDNODE02" -keyout cdcert.key -out cdcert.crt -batch

cat cdcert.crt cdcert.key > cdcert.pem

2) Setup OS

useradd -m cdadmin

mkdir -p /opt/cdunix

chown cdadmin:cdadmin /opt/cdunix

3) Setup silent install

Create dummy file for secure+

echo ""> spcmds.rsp

Create file silent_install.ini

<nowiki>cdai_installCmd=install
cdai_cpioFile=/Binaries/CD/cdunix
cdai_installDir=/opt/cdunix
cdai_localNodeName="CDNODE02"
cdai_acquireHostnameOrIP=ip4
cdai_trace=y
cdai_agentPort=1365
cdai_serverPort=1364
cdai_clientPort=1363
cdai_localCertFile=cdcert.pem
cdai_localCertLabel=cdinternal
cdai_adminUserid=cdadmin
cdai_keystorePassword=changeit
cdai_ignoreExistingInstallDir=y
cdai_spConfig=spcmds.rsp
cdai_installFA=y
cdai_fileAgentEnable=n</nowiki>

4) Run command

./cdinstall_a -f silent_install.ini

= Ver também =

* [[IBM Sterling| Artigos sobre IBM Sterling]]
* [[Tecnologias| Mais Artigos sobre Cloud / WebDev / Tecnologias]]
* [[IBM Sterling Connect:Direct]]

[[Category:IBM Sterling]]
[[Category:Connect:Direct]]
[[Category:B2B Integrator]]

IBM Sterling Connect:Direct : Silent Install

2026-05-06T19:08:52Z

Ebasso: /* Install */

Updated to 6.4.0.5

= Extract installer =

mkdir /Binaries/CD

tar -xvf 6.4.0.5-IBMSterlingConnectDirectforUNIX-Linux-x86-iFix007.tar

will extract files cdinstall, cdinstall_a, cdunix.

= Install =

1) Generate Certificate

openssl req -x509 -nodes -days 3650 -newkey rsa:4096 -sha512 -subj "/CN=CDNODE02" -keyout cdcert.key -out cdcert.crt -batch

cat cdcert.crt cdcert.key > cdcert.pem

2) Setup OS

useradd -m cdadmin

mkdir -p /opt/cdunix

chown cdadmin:cdadmin /opt/cdunix

3) Setup silent install

Create dummy file for secure+

echo ""> spcmds.rsp

Create file silent_install.ini

<nowiki>cdai_installCmd=install
cdai_cpioFile=/Binaries/CD/cdunix
cdai_installDir=/opt/cdunix
cdai_localNodeName="CDNODE02"
cdai_acquireHostnameOrIP=ip4
cdai_trace=y
cdai_agentPort=1365
cdai_serverPort=1364
cdai_clientPort=1363
cdai_localCertFile=cdcert.pem
cdai_localCertLabel=cdinternal
cdai_adminUserid=cdadmin
cdai_keystorePassword=changeit
cdai_ignoreExistingInstallDir=y
cdai_spConfig=spcmds.rsp
cdai_installFA=y
cdai_fileAgentEnable=n</nowiki>

4) Run command
./cdinstall_a -f silent_install.ini

= Ver também =

* [[IBM Sterling| Artigos sobre IBM Sterling]]
* [[Tecnologias| Mais Artigos sobre Cloud / WebDev / Tecnologias]]
* [[IBM Sterling Connect:Direct]]

[[Category:IBM Sterling]]
[[Category:Connect:Direct]]
[[Category:B2B Integrator]]

IBM Sterling Connect:Direct : Silent Install

2026-05-06T19:08:05Z

Ebasso: /* Install */

Updated to 6.4.0.5

= Extract installer =

mkdir /Binaries/CD

tar -xvf 6.4.0.5-IBMSterlingConnectDirectforUNIX-Linux-x86-iFix007.tar

will extract files cdinstall, cdinstall_a, cdunix.

= Install =

1) Generate Certificate

openssl req -x509 -nodes -days 3650 -newkey rsa:4096 -sha512 -subj "/CN=CDNODE02" -keyout cdcert.key -out cdcert.crt -batch

cat cdcert.crt cdcert.key > cdcert.pem

2) Setup OS

useradd -m cdadmin

mkdir -p /opt/cdunix

chown cdadmin:cdadmin /opt/cdunix

3) Setup silent install

echo ""> spcmds.rsp

Create file silent_install.ini

<nowiki>cdai_installCmd=install
cdai_cpioFile=/Binaries/CD/cdunix
cdai_installDir=/opt/cdunix
cdai_localNodeName="CDNODE02"
cdai_acquireHostnameOrIP=ip4
cdai_trace=y
cdai_agentPort=1365
cdai_serverPort=1364
cdai_clientPort=1363
cdai_localCertFile=cdcert.pem
cdai_localCertLabel=cdinternal
cdai_adminUserid=cdadmin
cdai_keystorePassword=changeit
cdai_ignoreExistingInstallDir=y
cdai_spConfig=spcmds.rsp
cdai_installFA=y
cdai_fileAgentEnable=n</nowiki>

4) Run command
./cdinstall_a -f silent_install.ini

= Ver também =

* [[IBM Sterling| Artigos sobre IBM Sterling]]
* [[Tecnologias| Mais Artigos sobre Cloud / WebDev / Tecnologias]]
* [[IBM Sterling Connect:Direct]]

[[Category:IBM Sterling]]
[[Category:Connect:Direct]]
[[Category:B2B Integrator]]

IBM Sterling Connect:Direct : Silent Install

2026-05-06T19:07:52Z

Ebasso:

Updated to 6.4.0.5

= Extract installer =

mkdir /Binaries/CD

tar -xvf 6.4.0.5-IBMSterlingConnectDirectforUNIX-Linux-x86-iFix007.tar

will extract files cdinstall, cdinstall_a, cdunix.

= Install =

1) Generate Certificate

openssl req -x509 -nodes -days 1825 -newkey rsa:4096 -sha512 -subj "/CN=CDNODE02" -keyout cdcert.key -out cdcert.crt -batch

cat cdcert.crt cdcert.key > cdcert.pem

2) Setup OS

useradd -m cdadmin

mkdir -p /opt/cdunix

chown cdadmin:cdadmin /opt/cdunix

3) Setup silent install

echo ""> spcmds.rsp

Create file silent_install.ini

<nowiki>cdai_installCmd=install
cdai_cpioFile=/Binaries/CD/cdunix
cdai_installDir=/opt/cdunix
cdai_localNodeName="CDNODE02"
cdai_acquireHostnameOrIP=ip4
cdai_trace=y
cdai_agentPort=1365
cdai_serverPort=1364
cdai_clientPort=1363
cdai_localCertFile=cdcert.pem
cdai_localCertLabel=cdinternal
cdai_adminUserid=cdadmin
cdai_keystorePassword=changeit
cdai_ignoreExistingInstallDir=y
cdai_spConfig=spcmds.rsp
cdai_installFA=y
cdai_fileAgentEnable=n</nowiki>

4) Run command
./cdinstall_a -f silent_install.ini

= Ver também =

* [[IBM Sterling| Artigos sobre IBM Sterling]]
* [[Tecnologias| Mais Artigos sobre Cloud / WebDev / Tecnologias]]
* [[IBM Sterling Connect:Direct]]

[[Category:IBM Sterling]]
[[Category:Connect:Direct]]
[[Category:B2B Integrator]]

IBM Maximo

2026-05-05T11:57:32Z

Ebasso: /* Migration to Maximo Application Suite (MAS) */

O IBM Maximo é um pacote de software de gerenciamento de ativos corporativos (EAM) oferecido pela IBM. O IBM Maximo fornece monitoramento de ativos remotos, manutenção e aplicativos de confiabilidade em uma única plataforma que permite aumentar o tempo de atividade, melhorar a produtividade, reduzir os custos de manutenção e construir operações mais resilientes.

Com sua versão mais recente, o Maximo Application Suite (MAS), o sistema oferece vários aplicativos:

{| class="wikitable"
|-
! Produto !! Descrição
|-
| Maximo Application Suite (MAS) ||
Composto por vários aplicativos, o produto ao qual a maioria dos usuários se refere como Maximo agora é chamado de “MAM”.
|-
| [[IBM Maximo: MAS Manage|MAS Manage]] ||
O MAS Manage foi projetado para reduzir o tempo de inatividade e os custos, otimizando o gerenciamento de ativos e os processos de manutenção para melhorar o desempenho operacional. O seu uso podem alavancar a experiência da indústria incorporada com modelos de dados de práticas recomendadas e fluxos de trabalho para acelerar a transformação da indústria. O MAM unifica o ciclo de vida do ativo e as atividades de gerenciamento de manutenção, fornecendo uma visão de todos os ativos, condições e processos de trabalho da empresa para obter um melhor planejamento e controle.
|-
| [[IBM Maximo Visual Inspection|Maximo Visual Inspection (MVI)]] ||
O MVI é uma plataforma de analise de imagens e videos, que permite criar modelos de Machine Learning
|-
| Maximo Monitor ||
Melhore a disponibilidade operacional e de ativos com monitoramento remoto avançado de ativos com Inteligência Artificial (IA) em escala. Os usuários podem coletar dados de seus sistemas OT existentes e convergir sistemas de TI e sistemas operacionais em um único data lake para detectar anomalias.
|-
| Maximo Health ||
Gerenciar o funcionamento de ativos usando dados IoT de sensores de ativos, registros de ativos e histórico de trabalho para aumentar a disponibilidade de ativos e melhorar o planejamento de substituição é o objetivo principal deste aplicativo. Ele fornece uma visualização do funcionamento do ativo por meio de exibições de painel para fornecer evidências para basear as decisões operacionais.
|-
| Maximo Predict ||
Em vez de reagir, o Predict fornece a capacidade de usar ações baseadas em condições para prever a probabilidade de falhas futuras aplicando aprendizado de máquina e análise de dados para reduzir custos e falhas de ativos. Com base no poder de outros recursos do Maximo, os usuários podem tomar decisões baseadas em dados e construir modelos preditivos.
|}

= Artigos e Blogs =

= Migration to Maximo Application Suite (MAS) =

* [[IBM Maximo: Install Maximo Application Suite using MAS CLI]]
** [[IBM Maximo: MAS CLI Options]]
** [[IBM Maximo: Installing MAS Core + Manage + DB2 Container]]
** [[IBM Maximo: Installing MAS Core + Manage + Oracle DB Container]]

* [[IBM Maximo: Migrate MAXDB to RH OpenShift (DB2 Version)]]

* [[IBM Maximo: Steps to Upgrade a Maximo 7.6 Database to MAS 9 after MAS Installation]]

* [[IBM Maximo: Disconnecting MAS Manage from the database for DB Maintenance]]

* [[IBM Maximo: Provide you customization_binaries.zip on OpenShift]]

* [[IBM Maximo: Migration to Maximo Application Suite (MAS)]]

* [[IBM Maximo: Creating Maximo Database on Oracle Database Free Edition (Container)]]

* [[IBM Maximo: Deploying Kafka after Maximo Manage]]

= Referencias =
* Blog: [https://bportaluri.com/blog Bruno Portaluri]
** [https://bportaluri.com/2021/10/maximo-bulk-update-list-view.html Atualização de uma lista - bulk update ]
* Blog: [https://maximosecrets.com Maximo Secrets]
* Yasutaka Nishimura
**[https://www.linkedin.com/pulse/apache-kafka-message-provider-maximo-yasutaka-nishimura/ Apache Kafka as a Message Provider in Maximo]
**[https://www.linkedin.com/pulse/custom-autoscript-end-point-realizes-access-oauth2-yasutaka-nishimura/ Custom autoscript end point realizes to access OAuth2 protected resources]
**[https://www.linkedin.com/pulse/running-maximo-manage-stand-alone-openshift-server-red-nishimura/ Running Maximo Manage on stand-alone OpenShift server with Red Hat Code Ready Containers]
**[https://www.linkedin.com/pulse/send-notifications-slack-via-maximo-integration-yasutaka-nishimura/ Send notifications to Slack via Maximo Integration Framework]

= API Rest, Documentação, Artigos e Exemplos =

* [[IBM Maximo: Maximo Manage development environment without OpenShift]]

* [[IBM Maximo: Dicas de APIs Rest]]

* [[IBM Maximo: Automation Scripts]]

* '''maximomize.com''': [https://www.maximomize.com/writing-your-first-crontask-for-maximo-in-jython Writing your first crontask for Maximo in Jython]
* '''maximomize.com''': [https://www.maximomize.com/writing-your-first-crontask-for-maximo-in-java Writing your First CronTask for Maximo in Java]
* '''a3jgroup.com''': [https://a3jgroup.com/run-an-automation-script-from-a-cron-task-in-maximo/ Run an Automation Script from a Cron Task in Maximo]

= Performance and Best Practice =

* Best Practice: [[IBM Maximo: My Configuration Tips]]

* Best Practice: [[IBM Maximo: SQL Queries - CRONTASKS & ESCALATIONS]] - Dica de Configuração de Performance

* Best Practice: [[IBM Maximo: Cleanup of Start Center]] - Dica de Manutenção de Performance

* Best Practice: [[IBM Maximo: Integrity Check Tool]] - Reporting data integrity issues

* Best Practice: [[IBM Maximo: Resizing JPEG Files in doclinks]]

* [[IBM Maximo: Identificar SQLs de longa duração]]
* [[IBM Maximo: Java Virtual Machine Properties for IBM WebSphere]
* [[IBM Maximo: System Properties para Monitor e diagnosticar problemas de Performance]]
* [[IBM Maximo: System Properties]]
* [[IBM Maximo: Isolar a Funcionalidade do Servidor]]
* [[IBM Maximo: Analisando a crontask PMWoGenCronTask]]

== SQL Queries ==

* [[IBM Maximo: SQL Queries]]
* [[IBM Maximo: SQL Queries - CRONTASKS & ESCALATIONS]]
* [[IBM Maximo: SQL Queries - WORKFLOW]]

* [[IBM Maximo: Identificar SQLs de longa duração]]
* [[IBM Maximo: Monitorar o número de DB Connections]]
* [[IBM Maximo: Tabelas que contêm consultas para revisar]]
* [[IBM Maximo: System Properties]]
* [[IBM Maximo: BMXAA6720W - Slow SQL Entries]]
* [[IBM Maximo: Exportando um relatório (BIRT) do banco de dados do Maximo]]
* [[IBM Maximo: Listar a quantidade de logins únicos por dia]]

=== Outras Tabelas ===
* [[IBM Maximo: SQL Queries - tabela CRONTASKHISTORY]]
* [[IBM Maximo: SQL Queries - tabela ESCREPEATTRACK]]
* [[IBM Maximo: SQL Queries - tabela ESCSTATUS]]
* [[IBM Maximo: SQL Queries - tabela LOGINTRACK]]
* [[IBM Maximo: SQL Queries - tabela QUERY]]
* [[IBM Maximo: SQL Queries - tabela WFINSTANCE]]

= Mensagens BMXAA =

* [[IBM Maximo: BMXAA6720W - Slow SQL Entries]]

* [[IBM Maximo: BMXAA4038E - Cannot log in to perform this action on Forgot Password link]]

= Instalação e Configuração Maximo EAM =

* [[IBM Maximo: Instalação do Maximo EAM no Linux via Linha de Comando]]
* [[IBM Maximo: Verificando pré-requisitos de instalação e upgrade do Maximo EAM]]

* [[IBM Maximo: Running Maximo EAM as Container]]

* [[IBM Maximo: Criando a database manualmente para o Maximo]]
* [[IBM Maximo: Criando as filas JMS Queues manualmente para o Maximo EAM]]
* [[IBM Maximo: Criando as filas JMS Queues via linha de comando para o Maximo EAM]]

= Relatórios =

* [[IBM Maximo: Exportando um relatório (BIRT) do banco de dados do Maximo]]
* [https://www.ibm.com/support/pages/maximo-76-report-booklet Lista de Relatórios do Maximo 7.6 (BIRT)]
* [https://www.ibm.com/support/pages/maximo-76designer-431-report-development-guide Guia de Desenvolvimento de Relatórios do Maximo 7.6 (BIRT)]
* [https://www.ibm.com/support/pages/maximo-76-reporting-options-and-comparisons Reporting Options and Comparisons (BIRT)]
* [https://www.ibm.com/support/pages/maximo-cognos-content-bi-packs Lista de Relatórios Cognos "Maximo Cognos Content - BI Packs" (Cognos)]
* [https://www.ibm.com/support/pages/maximo-76-cognos-feature-guide Maximo 76 Cognos Feature Guide]

= Ver também =

* [[Cloud| Artigos sobre Cloud]]
* [[Tecnologias| Mais Artigos sobre Cloud / WebDev / Tecnologias]]

[[Category:IBM Maximo]]

IBM Maximo: Deploying Kafka after Maximo Manage

2026-05-05T11:56:33Z

Ebasso:

Kafka is an essential component of the IBM Maximo Application Suite (MAS), providing distributed messaging for applications such as IoT, Monitor, and Predict. The MAS CLI supports multiple Kafka providers, allowing flexibility in infrastructure selection.

The MAS CLI supports the following providers via the --kafka-provider parameter:

{| class="wikitable"
|-
! Provider !! Value !! Description
|-
| Strimzi || strimzi || Open-source Kafka operator for Kubernetes
|-
| Red Hat AMQ Streams || redhat || Red Hat version of Strimzi
|-
| IBM Event Streams || ibm || Managed Kafka on IBM Cloud
|-
| AWS MSK || aws || ExaAmazon Managed Streaming for Apache Kafkample
|}

= Procedure =

1) Run MAS CLI (Linux/Mac)

podman run -it --rm -v $(pwd):/mnt/home:Z --pull always quay.io/ibmmas/cli:latest

for Mac add --arch arm64

2) Login no OpenShift

oc login --token=<your-token> --server=<your-server>

3) Export IBM Entitlement Key

export IBM_ENTITLEMENT_KEY="your-entitlement-key"

4) Check your storage classes

oc get storageclass

4) Create file /mnt/home/kafka-playbook-install.yml

<syntaxhighlight lang="yaml">
---
- hosts: localhost
any_errors_fatal: true
vars:
kafka_action: install
kafka_storage_class: ocs-storagecluster-cephfs
kafka_storage_size: 100Gi
zookeeper_storage_class: ocs-storagecluster-cephfs
zookeeper_storage_size: 10Gi

# Generate a KafkaCfg template
mas_instance_id: lab01
mas_config_dir: /mnt/home/masconfigs
roles:
- ibm.mas_devops.kafka
</syntaxhighlight>

Change your variables for your environment: '''kafka_storage_class''', '''mas_instance_id''', '''mas_config_dir'''.

5) Run ansible-playbook

ansible-playbook /mnt/home/kafka-playbook-install.yml

The ansible script will generate a file like: '''kafka-maskafka-strimzi-kafka.yml''' on /mnt/home/masconfigs. This file has Secrets and KafkaCfg, with certificates. To be used to configure MAS

= Ver também =

[[Category:Kafka]]
[[Category:IBM Maximo]]
[[Category:IBM MAS]]

IBM Maximo: Deploying Kafka after Maximo Manage

2026-05-05T11:54:05Z

Ebasso: /* Procedure */

Kafka is an essential component of the IBM Maximo Application Suite (MAS), providing distributed messaging for applications such as IoT, Monitor, and Predict. The MAS CLI supports multiple Kafka providers, allowing flexibility in infrastructure selection.

The MAS CLI supports the following providers via the --kafka-provider parameter:

{| class="wikitable"
|-
! Provider !! Value !! Description
|-
| Strimzi || strimzi || Open-source Kafka operator for Kubernetes
|-
| Red Hat AMQ Streams || redhat || Red Hat version of Strimzi
|-
| IBM Event Streams || ibm || Managed Kafka on IBM Cloud
|-
| AWS MSK || aws || ExaAmazon Managed Streaming for Apache Kafkample
|}

= Procedure =

1) Run MAS CLI (Linux/Mac)

podman run -it --rm -v $(pwd):/mnt/home:Z --pull always quay.io/ibmmas/cli:latest

for Mac add --arch arm64

2) Login no OpenShift

oc login --token=<your-token> --server=<your-server>

3) Export IBM Entitlement Key

export IBM_ENTITLEMENT_KEY="your-entitlement-key"

4) Check your storage classes

oc get storageclass

4) Create file /mnt/home/kafka-playbook-install.yml

<syntaxhighlight lang="yaml">
---
- hosts: localhost
any_errors_fatal: true
vars:
kafka_action: install
kafka_storage_class: ocs-storagecluster-cephfs
kafka_storage_size: 100Gi
zookeeper_storage_class: ocs-storagecluster-cephfs
zookeeper_storage_size: 10Gi

# Generate a KafkaCfg template
mas_instance_id: lab01
mas_config_dir: /mnt/home/masconfigs
roles:
- ibm.mas_devops.kafka
</syntaxhighlight>

Change your variables for your environment: '''kafka_storage_class''', '''mas_instance_id''', '''mas_config_dir'''.

5) Run ansible-playbook

ansible-playbook /mnt/home/kafka-playbook-install.yml

= Ver também =

[[Category:Kafka]]
[[Category:IBM Maximo]]
[[Category:IBM MAS]]

IBM Maximo: Deploying Kafka after Maximo Manage

2026-05-05T11:52:44Z

Ebasso: Created page with "Kafka is an essential component of the IBM Maximo Application Suite (MAS), providing distributed messaging for applications such as IoT, Monitor, and Predict. The MAS CLI supports multiple Kafka providers, allowing flexibility in infrastructure selection. The MAS CLI supports the following providers via the --kafka-provider parameter: {| class="wikitable" |- ! Provider !! Value !! Description |- | Strimzi || strimzi || Open-source Kafka operator for Kubernetes |- | Re..."

Kafka is an essential component of the IBM Maximo Application Suite (MAS), providing distributed messaging for applications such as IoT, Monitor, and Predict. The MAS CLI supports multiple Kafka providers, allowing flexibility in infrastructure selection.

The MAS CLI supports the following providers via the --kafka-provider parameter:

{| class="wikitable"
|-
! Provider !! Value !! Description
|-
| Strimzi || strimzi || Open-source Kafka operator for Kubernetes
|-
| Red Hat AMQ Streams || redhat || Red Hat version of Strimzi
|-
| IBM Event Streams || ibm || Managed Kafka on IBM Cloud
|-
| AWS MSK || aws || ExaAmazon Managed Streaming for Apache Kafkample
|}

= Procedure =

1) Run MAS CLI (Linux/Mac)

podman run -it --rm -v $(pwd):/mnt/home:Z --pull always quay.io/ibmmas/cli:latest

for Mac add --arch arm64

2) Login no OpenShift

oc login --token=<your-token> --server=<your-server>

3) Export IBM Entitlement Key

export IBM_ENTITLEMENT_KEY="your-entitlement-key"

4) Create file /mnt/home/kafka-playbook-install.yml

<syntaxhighlight lang="yaml">
---
- hosts: localhost
any_errors_fatal: true
vars:
kafka_action: install
kafka_storage_class: ocs-storagecluster-cephfs
kafka_storage_size: 100Gi
zookeeper_storage_class: ocs-storagecluster-cephfs
zookeeper_storage_size: 10Gi

# Generate a KafkaCfg template
mas_instance_id: lab01
mas_config_dir: /mnt/home/masconfigs
roles:
- ibm.mas_devops.kafka
</syntaxhighlight>

Change you '''mas_instance_id''' and '''mas_config_dir'''.

5) Run ansible-playbook

ansible-playbook /mnt/home/kafka-playbook-install.yml

= Ver também =

[[Category:Kafka]]
[[Category:IBM Maximo]]
[[Category:IBM MAS]]

Kafka

2026-05-05T11:43:43Z

Ebasso:

* [[Kafka: Deploy Kafka as Container]]

* [[IBM Sterling B2B: Configuring SB2Bi to use Kafka]]

* [[IBM Maximo: Deploying Kafka after Maximo Manage]]

= Ver também =

[[Category:Kafka]]
[[Category:IBM Sterling]]
[[Category:IBM Sterling B2B]]
[[Category:File Gateway]]
[[Category:SFG]]

IBM Maximo: Maximo Manage development environment without OpenShift

2026-05-04T01:16:07Z

Ebasso: /* Customization Guidelines */

= Pull image from IBM Repository =

Go to this webpage to get your entitlement key: https://myibm.ibm.com/products-services/containerlibrary

Set the IBM Entitlement Registry Key

export ENTITLED_REGISTRY_KEY=eyJ...

Do a login to Podman

podman login cp.icr.io -u cp -p $ENTITLED_REGISTRY_KEY

List Available Tags for a Manage Admin with skopeo tool.

skopeo list-tags docker://cp.icr.io/cp/manage/manageadmin

Inspect a Manage Admin Image

skopeo inspect docker://cp.icr.io/cp/manage/manageadmin:9.0.0

Pull a Manage Admin Image

podman pull cp.icr.io/cp/manage/manageadmin:9.0.0

= Run Manage Admin =

Run container in background

podman run -d cp.icr.io/cp/manage/manageadmin:9.0.0

Check status

podman ps

The output is

<small>CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
'''40e118bf9318''' cp.icr.io/cp/manage/manageadmin:9.0.0 3 seconds ago Up 3 seconds pedantic_cerf</small>

Connect to container and you can check current directory

podman exec -it '''40e118bf9318''' sh

sh-4.5$ pwd

Update the properties in the

/opt/IBM/SMP/maximo/applications/maximo/properties/maximo.properties

file with the URL, user name, and password for your Maximo Manage database.

= Customization =

== Customization Guidelines ==

Your source code must have the same directory structure used by Maximo. Sample:

applications\maximo\businessobjects\classes\cust\app\asset\CXAsset.class
applications\maximo\businessobjects\classes\cust\app\asset\CXAssetSet.class
applications\maximo\properties\product\a_customer.xml
tools\maximo\en\cust\V7612_01.dbc
applications\maximo\commonweb\classes\com\ibm\tivoli\maximo\oslc\provider\MyPingServlet.class
deployment\was-liberty-default\config-deployment-descriptors\maximo-all\meaweb\webmodule\WEB-INF\web.xml

For server bundles with a bundle type of mea, ui, cron, report. You can use:

deployment\was-liberty-default\config-deployment-descriptors\maximo-mea\meaweb\webmodule\WEB-INF\web.xml
deployment\was-liberty-default\config-deployment-descriptors\maximo-ui\webmodule\WEB-INF\web.xml

== Copy files to container ==

Get your source code, create a zip file and copy to container

podman cp mycode.zip '''40e118bf9318:/tmp/mycode.zip'''

Access your Maximo Manager container

podman exec -it '''40e118bf9318''' sh

Prepare environment

mkdir -p /tmp/src /tmp/target

cd /tmp/src

unzip ../mycode.zip

== Compile Java customization and create customization_binaries.zip==

Inside the container, let's export environment variables

export JAVA_HOME=/opt/ibm/java
export LIB_DIR=/opt/IBM/SMP/maximo/applications/maximo/lib/*
export CLASS_DIR=/opt/IBM/SMP/maximo/applications/maximo/businessobjects/classes

add the list of java files to sources.txt file

cd /tmp

find . -name "*.java" | grep -v _ > sources.txt

Compile files

$JAVA_HOME/bin/javac -d target -cp "$LIB_DIR:$CLASS_DIR" @sources.txt

Confirm that you dont have errors

Copy Non-Java Files using rsync

rsync -av --exclude="*.java" src/ target/

If you dont have rsync try this:

find src/ -type f ! -name "*.java" -exec cp --parents \{\} target/ \;

Create customization archive

cd /tmp/target

zip --verbose -r ../customization_binaries.zip *

== Provide you customization_binaries.zip on OpenShift ==

See here: [[IBM Maximo: Provide you customization binaries.zip on OpenShift]]

== How to test ==

* Extract the content in the same directory structure as customization archive
* Deploy customization archive on a test environment , or
* Test customization archive use local container deployment for Manage without OpenShift and MAS for limited but fast testing

== Articles ==

* [https://www.ibm.com/docs/en/mas-cd/maximo-manage/continuous-delivery?topic=customizing-customization-archive-guidelines Customization archive guidelines]
* [https://www.ibm.com/docs/en/mas-cd/maximo-manage/continuous-delivery?topic=environment-building-deploying-development-images Building and deploying development images]

= Ver também =

* [[Cloud| Artigos sobre Cloud]]
* [[Tecnologias| Mais Artigos sobre Cloud / WebDev / Tecnologias]]

[[Category:IBM Maximo]]

IBM Maximo: Maximo Manage development environment without OpenShift

2026-05-04T01:15:22Z

Ebasso: /* Copy files to container */

= Pull image from IBM Repository =

Go to this webpage to get your entitlement key: https://myibm.ibm.com/products-services/containerlibrary

Set the IBM Entitlement Registry Key

export ENTITLED_REGISTRY_KEY=eyJ...

Do a login to Podman

podman login cp.icr.io -u cp -p $ENTITLED_REGISTRY_KEY

List Available Tags for a Manage Admin with skopeo tool.

skopeo list-tags docker://cp.icr.io/cp/manage/manageadmin

Inspect a Manage Admin Image

skopeo inspect docker://cp.icr.io/cp/manage/manageadmin:9.0.0

Pull a Manage Admin Image

podman pull cp.icr.io/cp/manage/manageadmin:9.0.0

= Run Manage Admin =

Run container in background

podman run -d cp.icr.io/cp/manage/manageadmin:9.0.0

Check status

podman ps

The output is

<small>CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
'''40e118bf9318''' cp.icr.io/cp/manage/manageadmin:9.0.0 3 seconds ago Up 3 seconds pedantic_cerf</small>

Connect to container and you can check current directory

podman exec -it '''40e118bf9318''' sh

sh-4.5$ pwd

Update the properties in the

/opt/IBM/SMP/maximo/applications/maximo/properties/maximo.properties

file with the URL, user name, and password for your Maximo Manage database.

= Customization =

== Customization Guidelines ==

Your source code must have the same directory structure used by Maximo. Sample:

applications\maximo\businessobjects\classes\cust\app\asset\Asset.class
applications\maximo\businessobjects\classes\cust\app\asset\AssetSet.class
applications\maximo\properties\product\a_customer.xml
tools\maximo\en\cust\V7612_01.dbc
applications\maximo\commonweb\classes\com\ibm\tivoli\maximo\oslc\provider\MyPingServlet.class
deployment\was-liberty-default\config-deployment-descriptors\maximo-all\meaweb\webmodule\WEB-INF\web.xml

For server bundles with a bundle type of mea, ui, cron, report. You can use:

deployment\was-liberty-default\config-deployment-descriptors\maximo-mea\meaweb\webmodule\WEB-INF\web.xml
deployment\was-liberty-default\config-deployment-descriptors\maximo-ui\webmodule\WEB-INF\web.xml

== Copy files to container ==

Get your source code, create a zip file and copy to container

podman cp mycode.zip '''40e118bf9318:/tmp/mycode.zip'''

Access your Maximo Manager container

podman exec -it '''40e118bf9318''' sh

Prepare environment

mkdir -p /tmp/src /tmp/target

cd /tmp/src

unzip ../mycode.zip

== Compile Java customization and create customization_binaries.zip==

Inside the container, let's export environment variables

export JAVA_HOME=/opt/ibm/java
export LIB_DIR=/opt/IBM/SMP/maximo/applications/maximo/lib/*
export CLASS_DIR=/opt/IBM/SMP/maximo/applications/maximo/businessobjects/classes

add the list of java files to sources.txt file

cd /tmp

find . -name "*.java" | grep -v _ > sources.txt

Compile files

$JAVA_HOME/bin/javac -d target -cp "$LIB_DIR:$CLASS_DIR" @sources.txt

Confirm that you dont have errors

Copy Non-Java Files using rsync

rsync -av --exclude="*.java" src/ target/

If you dont have rsync try this:

find src/ -type f ! -name "*.java" -exec cp --parents \{\} target/ \;

Create customization archive

cd /tmp/target

zip --verbose -r ../customization_binaries.zip *

== Provide you customization_binaries.zip on OpenShift ==

See here: [[IBM Maximo: Provide you customization binaries.zip on OpenShift]]

== How to test ==

* Extract the content in the same directory structure as customization archive
* Deploy customization archive on a test environment , or
* Test customization archive use local container deployment for Manage without OpenShift and MAS for limited but fast testing

== Articles ==

* [https://www.ibm.com/docs/en/mas-cd/maximo-manage/continuous-delivery?topic=customizing-customization-archive-guidelines Customization archive guidelines]
* [https://www.ibm.com/docs/en/mas-cd/maximo-manage/continuous-delivery?topic=environment-building-deploying-development-images Building and deploying development images]

= Ver também =

* [[Cloud| Artigos sobre Cloud]]
* [[Tecnologias| Mais Artigos sobre Cloud / WebDev / Tecnologias]]

[[Category:IBM Maximo]]

IBM Maximo: Maximo Manage development environment without OpenShift

2026-05-04T01:14:26Z

Ebasso: /* Copy files to container */

= Pull image from IBM Repository =

Go to this webpage to get your entitlement key: https://myibm.ibm.com/products-services/containerlibrary

Set the IBM Entitlement Registry Key

export ENTITLED_REGISTRY_KEY=eyJ...

Do a login to Podman

podman login cp.icr.io -u cp -p $ENTITLED_REGISTRY_KEY

List Available Tags for a Manage Admin with skopeo tool.

skopeo list-tags docker://cp.icr.io/cp/manage/manageadmin

Inspect a Manage Admin Image

skopeo inspect docker://cp.icr.io/cp/manage/manageadmin:9.0.0

Pull a Manage Admin Image

podman pull cp.icr.io/cp/manage/manageadmin:9.0.0

= Run Manage Admin =

Run container in background

podman run -d cp.icr.io/cp/manage/manageadmin:9.0.0

Check status

podman ps

The output is

<small>CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
'''40e118bf9318''' cp.icr.io/cp/manage/manageadmin:9.0.0 3 seconds ago Up 3 seconds pedantic_cerf</small>

Connect to container and you can check current directory

podman exec -it '''40e118bf9318''' sh

sh-4.5$ pwd

Update the properties in the

/opt/IBM/SMP/maximo/applications/maximo/properties/maximo.properties

file with the URL, user name, and password for your Maximo Manage database.

= Customization =

== Customization Guidelines ==

Your source code must have the same directory structure used by Maximo. Sample:

applications\maximo\businessobjects\classes\cust\app\asset\Asset.class
applications\maximo\businessobjects\classes\cust\app\asset\AssetSet.class
applications\maximo\properties\product\a_customer.xml
tools\maximo\en\cust\V7612_01.dbc
applications\maximo\commonweb\classes\com\ibm\tivoli\maximo\oslc\provider\MyPingServlet.class
deployment\was-liberty-default\config-deployment-descriptors\maximo-all\meaweb\webmodule\WEB-INF\web.xml

For server bundles with a bundle type of mea, ui, cron, report. You can use:

deployment\was-liberty-default\config-deployment-descriptors\maximo-mea\meaweb\webmodule\WEB-INF\web.xml
deployment\was-liberty-default\config-deployment-descriptors\maximo-ui\webmodule\WEB-INF\web.xml

== Copy files to container ==

Get your source code, create a zip file and copy to container

podman cp mycode.zip '''40e118bf9318:/home/maximoinstall/mycode.zip'''

Access your Maximo Manager container

podman exec -it '''40e118bf9318''' sh

Prepare environment

cd /tmp

mkdir src target

cd src

unzip mycode.zip

== Compile Java customization and create customization_binaries.zip==

Inside the container, let's export environment variables

export JAVA_HOME=/opt/ibm/java
export LIB_DIR=/opt/IBM/SMP/maximo/applications/maximo/lib/*
export CLASS_DIR=/opt/IBM/SMP/maximo/applications/maximo/businessobjects/classes

add the list of java files to sources.txt file

cd /tmp

find . -name "*.java" | grep -v _ > sources.txt

Compile files

$JAVA_HOME/bin/javac -d target -cp "$LIB_DIR:$CLASS_DIR" @sources.txt

Confirm that you dont have errors

Copy Non-Java Files using rsync

rsync -av --exclude="*.java" src/ target/

If you dont have rsync try this:

find src/ -type f ! -name "*.java" -exec cp --parents \{\} target/ \;

Create customization archive

cd /tmp/target

zip --verbose -r ../customization_binaries.zip *

== Provide you customization_binaries.zip on OpenShift ==

See here: [[IBM Maximo: Provide you customization binaries.zip on OpenShift]]

== How to test ==

* Extract the content in the same directory structure as customization archive
* Deploy customization archive on a test environment , or
* Test customization archive use local container deployment for Manage without OpenShift and MAS for limited but fast testing

== Articles ==

* [https://www.ibm.com/docs/en/mas-cd/maximo-manage/continuous-delivery?topic=customizing-customization-archive-guidelines Customization archive guidelines]
* [https://www.ibm.com/docs/en/mas-cd/maximo-manage/continuous-delivery?topic=environment-building-deploying-development-images Building and deploying development images]

= Ver também =

* [[Cloud| Artigos sobre Cloud]]
* [[Tecnologias| Mais Artigos sobre Cloud / WebDev / Tecnologias]]

[[Category:IBM Maximo]]

IBM Maximo: Maximo Manage development environment without OpenShift

2026-05-04T01:14:12Z

Ebasso: /* Compile Java customization and create customization_binaries.zip */

= Pull image from IBM Repository =

Go to this webpage to get your entitlement key: https://myibm.ibm.com/products-services/containerlibrary

Set the IBM Entitlement Registry Key

export ENTITLED_REGISTRY_KEY=eyJ...

Do a login to Podman

podman login cp.icr.io -u cp -p $ENTITLED_REGISTRY_KEY

List Available Tags for a Manage Admin with skopeo tool.

skopeo list-tags docker://cp.icr.io/cp/manage/manageadmin

Inspect a Manage Admin Image

skopeo inspect docker://cp.icr.io/cp/manage/manageadmin:9.0.0

Pull a Manage Admin Image

podman pull cp.icr.io/cp/manage/manageadmin:9.0.0

= Run Manage Admin =

Run container in background

podman run -d cp.icr.io/cp/manage/manageadmin:9.0.0

Check status

podman ps

The output is

<small>CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
'''40e118bf9318''' cp.icr.io/cp/manage/manageadmin:9.0.0 3 seconds ago Up 3 seconds pedantic_cerf</small>

Connect to container and you can check current directory

podman exec -it '''40e118bf9318''' sh

sh-4.5$ pwd

Update the properties in the

/opt/IBM/SMP/maximo/applications/maximo/properties/maximo.properties

file with the URL, user name, and password for your Maximo Manage database.

= Customization =

== Customization Guidelines ==

Your source code must have the same directory structure used by Maximo. Sample:

applications\maximo\businessobjects\classes\cust\app\asset\Asset.class
applications\maximo\businessobjects\classes\cust\app\asset\AssetSet.class
applications\maximo\properties\product\a_customer.xml
tools\maximo\en\cust\V7612_01.dbc
applications\maximo\commonweb\classes\com\ibm\tivoli\maximo\oslc\provider\MyPingServlet.class
deployment\was-liberty-default\config-deployment-descriptors\maximo-all\meaweb\webmodule\WEB-INF\web.xml

For server bundles with a bundle type of mea, ui, cron, report. You can use:

deployment\was-liberty-default\config-deployment-descriptors\maximo-mea\meaweb\webmodule\WEB-INF\web.xml
deployment\was-liberty-default\config-deployment-descriptors\maximo-ui\webmodule\WEB-INF\web.xml

== Copy files to container ==

Get your source code, create a zip file and copy to container

podman cp mycode.zip '''40e118bf9318:/home/maximoinstall/mycode.zip'''

Access your Maximo Manager container

podman exec -it '''40e118bf9318''' sh

Prepare environment

cd /home/maximoinstall

mkdir src target

cd src

unzip mycode.zip

== Compile Java customization and create customization_binaries.zip==

Inside the container, let's export environment variables

export JAVA_HOME=/opt/ibm/java
export LIB_DIR=/opt/IBM/SMP/maximo/applications/maximo/lib/*
export CLASS_DIR=/opt/IBM/SMP/maximo/applications/maximo/businessobjects/classes

add the list of java files to sources.txt file

cd /tmp

find . -name "*.java" | grep -v _ > sources.txt

Compile files

$JAVA_HOME/bin/javac -d target -cp "$LIB_DIR:$CLASS_DIR" @sources.txt

Confirm that you dont have errors

Copy Non-Java Files using rsync

rsync -av --exclude="*.java" src/ target/

If you dont have rsync try this:

find src/ -type f ! -name "*.java" -exec cp --parents \{\} target/ \;

Create customization archive

cd /tmp/target

zip --verbose -r ../customization_binaries.zip *

== Provide you customization_binaries.zip on OpenShift ==

See here: [[IBM Maximo: Provide you customization binaries.zip on OpenShift]]

== How to test ==

* Extract the content in the same directory structure as customization archive
* Deploy customization archive on a test environment , or
* Test customization archive use local container deployment for Manage without OpenShift and MAS for limited but fast testing

== Articles ==

* [https://www.ibm.com/docs/en/mas-cd/maximo-manage/continuous-delivery?topic=customizing-customization-archive-guidelines Customization archive guidelines]
* [https://www.ibm.com/docs/en/mas-cd/maximo-manage/continuous-delivery?topic=environment-building-deploying-development-images Building and deploying development images]

= Ver também =

* [[Cloud| Artigos sobre Cloud]]
* [[Tecnologias| Mais Artigos sobre Cloud / WebDev / Tecnologias]]

[[Category:IBM Maximo]]

IBM Maximo: Creating Maximo Database on Oracle Database Free Edition (Container)

2026-05-03T17:44:01Z

Ebasso: /* Sample JDBC Configuration */

This guide provides step-by-step instructions for deploying Oracle Database 23c Free Edition on OpenShift and creating a Maximo database with the required schema.

== Overview ==

Oracle Database 23c Free Edition is a fully-featured Oracle Database that can be used for development, testing, and small production deployments. This guide covers:

Follow the instructions, to create Oracle Database

* [[Oracle: Run Oracle DB on Redhat OpenShift]]

== Step 2: Create Maximo Schema in FREE Database ==

=== Step 2.1: Connect to Oracle Container ===

First, connect to the Oracle database container:

<syntaxhighlight lang="bash">
oc exec -it oracle-db-0 -- bash
</syntaxhighlight>

=== Step 2.2: Create Maximo Tablespaces ===

Connect to SQL*Plus and create the required tablespaces in the FREE database:

<syntaxhighlight lang="bash">
sqlplus sys/$ORACLE_PWD@FREE as sysdba
</syntaxhighlight>

Then execute the following SQL commands:

<syntaxhighlight lang="sql">
-- Create MAXDATA tablespace for Maximo data
CREATE TABLESPACE maxdata
DATAFILE '/opt/oracle/oradata/FREE/maxdata.dbf'
SIZE 1000M
AUTOEXTEND ON;

-- Create MAXINDEX tablespace for Maximo indexes
CREATE TABLESPACE maxindex
DATAFILE '/opt/oracle/oradata/FREE/maxindex.dbf'
SIZE 1000M
AUTOEXTEND ON;

-- Create MAXTEMP temporary tablespace
CREATE TEMPORARY TABLESPACE maxtemp
TEMPFILE '/opt/oracle/oradata/FREE/maxtemp.dbf'
SIZE 1000M
AUTOEXTEND ON
MAXSIZE UNLIMITED;

-- Create Maximo Schema and User
-- Allow creation of local users in CDB (Oracle 12c+ requirement)
ALTER SESSION SET "_ORACLE_SCRIPT"=true;

-- Create MAXIMO user/schema
CREATE USER MAXIMO
IDENTIFIED BY "Maximo_123"
DEFAULT TABLESPACE maxdata
TEMPORARY TABLESPACE maxtemp;

-- Grant basic privileges
GRANT CONNECT TO MAXIMO;
GRANT CREATE JOB TO MAXIMO;
GRANT CREATE TRIGGER TO MAXIMO;
GRANT CREATE SESSION TO MAXIMO;
GRANT CREATE SEQUENCE TO MAXIMO;
GRANT CREATE SYNONYM TO MAXIMO;
GRANT CREATE TABLE TO MAXIMO;
GRANT CREATE VIEW TO MAXIMO;
GRANT CREATE PROCEDURE TO MAXIMO;
GRANT ALTER SESSION TO MAXIMO;

-- Grant SYSDBA privilege
GRANT SYSDBA TO MAXIMO;

-- Grant execute on CTX_DDL for text search
GRANT EXECUTE ON ctxsys.ctx_ddl TO MAXIMO;

-- Grant unlimited quota on maxdata tablespace
ALTER USER MAXIMO QUOTA UNLIMITED ON maxdata;

-- Grant unlimited quota on maxindex tablespace (for indexes)
ALTER USER MAXIMO QUOTA UNLIMITED ON maxindex;

EXIT
</syntaxhighlight>

== Step 3: Verify Database Setup ==

All verification commands should be executed from within the container bash session.

=== Step 3.1: Verify Tablespaces ===

<syntaxhighlight lang="bash">
sqlplus sys/$ORACLE_PWD@FREE as sysdba
</syntaxhighlight>

<syntaxhighlight lang="sql">
SELECT tablespace_name, status, contents
FROM dba_tablespaces
WHERE tablespace_name IN ('MAXDATA', 'MAXINDEX', 'MAXTEMP');

EXIT
</syntaxhighlight>

Expected output:
<pre>
TABLESPACE_NAME STATUS CONTENTS
--------------- -------- ---------
MAXDATA ONLINE PERMANENT
MAXINDEX ONLINE PERMANENT
MAXTEMP ONLINE TEMPORARY
</pre>

=== Step 3.2: Verify Maximo Schema ===

<syntaxhighlight lang="bash">
sqlplus sys/$ORACLE_PWD@FREE as sysdba
</syntaxhighlight>

<syntaxhighlight lang="sql">
SELECT username, default_tablespace, temporary_tablespace, account_status
FROM dba_users
WHERE username = 'MAXIMO';

EXIT
</syntaxhighlight>

Expected output:
<pre>
USERNAME DEFAULT_TABLESPACE TEMPORARY_TABLESPACE ACCOUNT_STATUS
-------- ------------------ -------------------- --------------
MAXIMO MAXDATA MAXTEMP OPEN
</pre>

=== Step 3.3: Verify User Privileges ===

<syntaxhighlight lang="bash">
sqlplus sys/$ORACLE_PWD@FREE as sysdba
</syntaxhighlight>

<syntaxhighlight lang="sql">
SELECT privilege
FROM dba_sys_privs
WHERE grantee = 'MAXIMO'
ORDER BY privilege;

EXIT
</syntaxhighlight>

Expected privileges should include:
<pre>
ALTER SESSION
CONNECT
CREATE JOB
CREATE PROCEDURE
CREATE SEQUENCE
CREATE SESSION
CREATE SYNONYM
CREATE TABLE
CREATE TRIGGER
CREATE VIEW
SYSDBA
</pre>

=== Step 3.4: Verify SYSDBA Access ===

Test that MAXIMO can connect with SYSDBA privilege:

<syntaxhighlight lang="bash">
sqlplus MAXIMO/Maximo_123@FREE as sysdba
</syntaxhighlight>

<syntaxhighlight lang="sql">
SELECT USER, SYS_CONTEXT('USERENV', 'ISDBA') AS IS_DBA FROM DUAL;

EXIT
</syntaxhighlight>

=== Step 3.5: Test Maximo User Connection ===

<syntaxhighlight lang="bash">
sqlplus MAXIMO/Maximo_123@FREE
</syntaxhighlight>

<syntaxhighlight lang="sql">
SELECT USER FROM DUAL;

EXIT
</syntaxhighlight>

Expected output:
<pre>
USER
------
MAXIMO
</pre>

=== Step 3.6: Verify Tables in MAXIMO Schema ===

Check if any tables have been created in the MAXIMO schema:

<syntaxhighlight lang="bash">
sqlplus MAXIMO/Maximo_123@FREE
</syntaxhighlight>

<syntaxhighlight lang="sql">
-- Count total tables
SELECT COUNT(*) AS table_count FROM user_tables;

-- define line size
SET LINESIZE 200
COL TABLE_NAME FORMAT A30
COL NUM_ROWS FORMAT 9999999
COL TABLESPACE_NAME FORMAT A20

-- List all tables (if any exist)
SELECT table_name, num_rows, tablespace_name
FROM user_tables
ORDER BY table_name;

EXIT
</syntaxhighlight>

Expected output (before Maximo installation):
<pre>
TABLE_COUNT
-----------
0

no rows selected
</pre>

After Maximo installation, you should see Maximo tables like:
<pre>
TABLE_NAME NUM_ROWS TABLESPACE_NAME
------------------- -------- ---------------
ASSET 0 MAXDATA
PERSON 0 MAXDATA
WORKORDER 0 MAXDATA
...
</pre>

Alternative command to check tables from SYS user:

<syntaxhighlight lang="bash">
sqlplus sys/$ORACLE_PWD@FREE as sysdba
</syntaxhighlight>

<syntaxhighlight lang="sql">
-- Check tables owned by MAXIMO
SELECT owner, table_name, tablespace_name, num_rows
FROM dba_tables
WHERE owner = 'MAXIMO'
ORDER BY table_name;

-- Count tables by owner
SELECT owner, COUNT(*) AS table_count
FROM dba_tables
WHERE owner = 'MAXIMO'
GROUP BY owner;

EXIT
</syntaxhighlight>

=== Step 3.7: Exit Container ===

After verification, exit the container:

<syntaxhighlight lang="bash">
exit
</syntaxhighlight>

== Step 4: Configure Maximo Application Suite Connection ==

=== Connection Details ===

Use the following connection details in your Maximo Application Suite JDBC configuration:

* '''Database Type''': Oracle
* '''Host''': `oracle-db-svc` (or `oracle-db-svc.<namespace>.svc.cluster.local`)
* '''Port''': `1521`
* '''Service Name''': `FREE`
* '''Schema''': `MAXIMO`
* '''Username''': `MAXIMO`
* '''Password''': `Maximo_123`
* '''JDBC URL''': `jdbc:oracle:thin:@oracle-db-svc:1521/FREE`

=== Sample JDBC Configuration ===

this work for me!

File: jdbc-lab01-manage.yaml

<syntaxhighlight lang="yaml">
---
apiVersion: v1
kind: Secret
type: Opaque
metadata:
name: "jdbc-ws01-manage-credentials"
namespace: "mas-lab01-core"
stringData:
username: "MAXIMO"
password: "Maximo_123"
---
apiVersion: config.mas.ibm.com/v1
kind: JdbcCfg
metadata:
name: "lab01-jdbc-wsapp-ws01-manage"
namespace: "mas-lab01-core"
labels:
'mas.ibm.com/configScope': 'workspace-application'
'mas.ibm.com/instanceId': 'lab01'
'mas.ibm.com/workspaceId': 'ws01'
'mas.ibm.com/applicationId': 'manage'
spec:
displayName: "JDBC WS01 Manage"
config:
url: "jdbc:oracle:thin:@oracle-db-svc.oracle-maxdb.svc:1521/FREE"
sslEnabled: False
credentials:
secretName: "jdbc-ws01-manage-credentials"

</syntaxhighlight>

Another sample

=== Create JDBC Secret for MAS ===

<syntaxhighlight lang="bash">
oc create secret generic jdbc-ws01-manage-credentials \
--from-literal=username=MAXIMO \
--from-literal=password='Maximo_123' \
--from-literal=url='jdbc:oracle:thin:@oracle-db-svc:1521/FREE'
</syntaxhighlight>

<syntaxhighlight lang="yaml">
apiVersion: config.mas.ibm.com/v1
kind: JdbcCfg
metadata:
name: maximo-jdbc-config
namespace: mas-<instance-id>-core
spec:
certificates:
- alias: oracle-cert
crt: |
-----BEGIN CERTIFICATE-----
<certificate content if using SSL>
-----END CERTIFICATE-----
config:
credentials:
secretName: maximo-jdbc-secret
driverOptions: {}
sslEnabled: false
url: jdbc:oracle:thin:@oracle-db-svc:1521/FREE
displayName: Maximo Oracle Database
type: external
</syntaxhighlight>

= See Also =

* [[Cloud|Articles about Cloud]]
* [[IBM_Maximo|More Articles about IBM_Maximo]]

[[Category:IBM Maximo]]
[[Category:IBM MAS]]

IBM Maximo: Installing MAS Core + Manage + Oracle DB Container

2026-05-03T17:43:36Z

Ebasso: /* Create Sample JDBC Configuration */

= Prepare Oracle DB =

# [[Oracle: Run Oracle DB on Redhat OpenShift]]
# [[IBM Maximo: Creating Maximo Database on Oracle Database Free Edition (Container)]]

= Installing MAS Core via MAS CLI =

Run the container:

mkdir -p mas-cli-workspace/masconfig

cp license.dat mas-cli-workspace/.

===Create Sample JDBC Configuration===

File: mas-cli-workspace/masconfig/jdbc-lab01-manage.yaml

<syntaxhighlight lang="yaml">
---
apiVersion: v1
kind: Secret
type: Opaque
metadata:
name: "jdbc-ws01-manage-credentials"
namespace: "mas-lab01-core"
stringData:
username: "MAXIMO"
password: "Maximo_123"
---
apiVersion: config.mas.ibm.com/v1
kind: JdbcCfg
metadata:
name: "lab01-jdbc-wsapp-ws01-manage"
namespace: "mas-lab01-core"
labels:
'mas.ibm.com/configScope': 'workspace-application'
'mas.ibm.com/instanceId': 'lab01'
'mas.ibm.com/workspaceId': 'ws01'
'mas.ibm.com/applicationId': 'manage'
spec:
displayName: "JDBC WS01 Manage"
config:
url: "jdbc:oracle:thin:@oracle-db-svc.oracle-maxdb.svc:1521/FREE"
sslEnabled: False
credentials:
secretName: "jdbc-ws01-manage-credentials"

</syntaxhighlight>

= MAS Installation =

podman run -it --rm -v $(pwd)/mas-cli-workspace:/mnt/home:Z --pull always quay.io/ibmmas/cli:latest

for Mac (Apple Silicon M1) add '''--arch arm64'''

Run the MAS installation:

export IBM_ENTITLEMENT_KEY=x
export STORAGE_CLASS_RWO=ocs-storagecluster-cephfs
export STORAGE_CLASS_RWM=ocs-storagecluster-cephfs

mas install --mas-catalog-version v9-260430-amd64 --ibm-entitlement-key $IBM_ENTITLEMENT_KEY \
--mas-channel 9.1.x --mas-instance-id lab01 --mas-workspace-id ws01 --mas-workspace-name "Lab Workspace" \
'''--additional-configs "/mnt/home/masconfigs"''' \
<nowiki>--non-prod \
--storage-class-rwo $STORAGE_CLASS_RWO --storage-class-rwx $STORAGE_CLASS_RWM \
--storage-pipeline $STORAGE_CLASS_RWM --storage-accessmode "ReadWriteMany" \
--license-file "/mnt/home/license.dat" \
--contact-email "lab@company.com" --contact-firstname "Lab" --contact-lastname "User" \
--mongodb-namespace "mongoce" \
--grafana-v5-namespace "grafana5" \
--grafana-instance-storage-size "10Gi" \
--manage-channel "9.1.x" \
--manage-jdbc "workspace-application" \
--manage-components "base=latest" \
--manage-server-bundle-size "dev" \
--manage-demodata \
--manage-base-language "EN" \
--manage-secondary-languages "PT-BR" \
--accept-license --no-confirm
</nowiki>

= See Also =

* [[Cloud|Articles about Cloud]]
* [[IBM_Maximo|More Articles about IBM_Maximo]]

[[Category:IBM Maximo]]
[[Category:IBM MAS]]

IBM Maximo: MAS CLI Options

2026-05-03T16:26:33Z

Ebasso: /* Manage Bundel Sizes */

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 "ebasso@company.com" --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 Bundle Sizes =

mas install --mas-catalog-version v9-250501-amd64 --ibm-entitlement-key $IBM_ENTITLEMENT_KEY \
...
--manage-server-bundle-size "dev" \
...

The parameter <code>--manage-server-bundle-size {dev,snojms,small,jms}</code> selects the predefined Manage server bundle profile used during deployment.

* '''dev''': Development-oriented profile. Recommended for labs, demos, and small validation environments
* '''snojms''': Small profile without JMS. Helps reduce resource and storage requirements
* '''small''': Small standard profile. Suitable for compact environments that still want a more complete setup than <code>dev</code>

* '''jms''': Profile with JMS enabled. Use when Manage features or integrations require JMS queues
** Requires JMS-related storage configuration: --manage-jms

= Ver também =

* [[IBM Maximo: Instalação do Maximo Application Suite usando o MAS CLI]]
* [[Cloud| Artigos sobre Cloud]]
* [[Tecnologias| Mais Artigos sobre Cloud / WebDev / Tecnologias]]

[[Category:IBM Maximo]]

Rust: Struct,

2026-05-03T16:16:01Z

Ebasso: Created page with " struct User { username: String, email: String, sign_in_count: u64, active: bool, }"

struct User {
username: String,
email: String,
sign_in_count: u64,
active: bool,
}

Rust

2026-05-03T16:13:39Z

Ebasso: /* Aprendendo */

= Aprendendo =

* [https://livro.rustbr.org/title-page.html Livro Rust em Português]

* [https://exercism.io/tracks/rust exercism.io - Aprendendo com exercícios]

= Conceitos Importantes =

* [[Rust: Struct, ]]

= Linguagem Rust =

* [[Rust: Variáveis]]

* [[Rust: Funções]]

* [[Rust: Controle de Fluxo (Loop)]]

= Ver também =

* [[Python| Artigos sobre Python]]

IBM Maximo: Creating Maximo Database on Oracle Database Free Edition (Container)

2026-05-03T16:12:44Z

Ebasso: /* Ver também */

This guide provides step-by-step instructions for deploying Oracle Database 23c Free Edition on OpenShift and creating a Maximo database with the required schema.

== Overview ==

Oracle Database 23c Free Edition is a fully-featured Oracle Database that can be used for development, testing, and small production deployments. This guide covers:

Follow the instructions, to create Oracle Database

* [[Oracle: Run Oracle DB on Redhat OpenShift]]

== Step 2: Create Maximo Schema in FREE Database ==

=== Step 2.1: Connect to Oracle Container ===

First, connect to the Oracle database container:

<syntaxhighlight lang="bash">
oc exec -it oracle-db-0 -- bash
</syntaxhighlight>

=== Step 2.2: Create Maximo Tablespaces ===

Connect to SQL*Plus and create the required tablespaces in the FREE database:

<syntaxhighlight lang="bash">
sqlplus sys/$ORACLE_PWD@FREE as sysdba
</syntaxhighlight>

Then execute the following SQL commands:

<syntaxhighlight lang="sql">
-- Create MAXDATA tablespace for Maximo data
CREATE TABLESPACE maxdata
DATAFILE '/opt/oracle/oradata/FREE/maxdata.dbf'
SIZE 1000M
AUTOEXTEND ON;

-- Create MAXINDEX tablespace for Maximo indexes
CREATE TABLESPACE maxindex
DATAFILE '/opt/oracle/oradata/FREE/maxindex.dbf'
SIZE 1000M
AUTOEXTEND ON;

-- Create MAXTEMP temporary tablespace
CREATE TEMPORARY TABLESPACE maxtemp
TEMPFILE '/opt/oracle/oradata/FREE/maxtemp.dbf'
SIZE 1000M
AUTOEXTEND ON
MAXSIZE UNLIMITED;

-- Create Maximo Schema and User
-- Allow creation of local users in CDB (Oracle 12c+ requirement)
ALTER SESSION SET "_ORACLE_SCRIPT"=true;

-- Create MAXIMO user/schema
CREATE USER MAXIMO
IDENTIFIED BY "Maximo_123"
DEFAULT TABLESPACE maxdata
TEMPORARY TABLESPACE maxtemp;

-- Grant basic privileges
GRANT CONNECT TO MAXIMO;
GRANT CREATE JOB TO MAXIMO;
GRANT CREATE TRIGGER TO MAXIMO;
GRANT CREATE SESSION TO MAXIMO;
GRANT CREATE SEQUENCE TO MAXIMO;
GRANT CREATE SYNONYM TO MAXIMO;
GRANT CREATE TABLE TO MAXIMO;
GRANT CREATE VIEW TO MAXIMO;
GRANT CREATE PROCEDURE TO MAXIMO;
GRANT ALTER SESSION TO MAXIMO;

-- Grant SYSDBA privilege
GRANT SYSDBA TO MAXIMO;

-- Grant execute on CTX_DDL for text search
GRANT EXECUTE ON ctxsys.ctx_ddl TO MAXIMO;

-- Grant unlimited quota on maxdata tablespace
ALTER USER MAXIMO QUOTA UNLIMITED ON maxdata;

-- Grant unlimited quota on maxindex tablespace (for indexes)
ALTER USER MAXIMO QUOTA UNLIMITED ON maxindex;

EXIT
</syntaxhighlight>

== Step 3: Verify Database Setup ==

All verification commands should be executed from within the container bash session.

=== Step 3.1: Verify Tablespaces ===

<syntaxhighlight lang="bash">
sqlplus sys/$ORACLE_PWD@FREE as sysdba
</syntaxhighlight>

<syntaxhighlight lang="sql">
SELECT tablespace_name, status, contents
FROM dba_tablespaces
WHERE tablespace_name IN ('MAXDATA', 'MAXINDEX', 'MAXTEMP');

EXIT
</syntaxhighlight>

Expected output:
<pre>
TABLESPACE_NAME STATUS CONTENTS
--------------- -------- ---------
MAXDATA ONLINE PERMANENT
MAXINDEX ONLINE PERMANENT
MAXTEMP ONLINE TEMPORARY
</pre>

=== Step 3.2: Verify Maximo Schema ===

<syntaxhighlight lang="bash">
sqlplus sys/$ORACLE_PWD@FREE as sysdba
</syntaxhighlight>

<syntaxhighlight lang="sql">
SELECT username, default_tablespace, temporary_tablespace, account_status
FROM dba_users
WHERE username = 'MAXIMO';

EXIT
</syntaxhighlight>

Expected output:
<pre>
USERNAME DEFAULT_TABLESPACE TEMPORARY_TABLESPACE ACCOUNT_STATUS
-------- ------------------ -------------------- --------------
MAXIMO MAXDATA MAXTEMP OPEN
</pre>

=== Step 3.3: Verify User Privileges ===

<syntaxhighlight lang="bash">
sqlplus sys/$ORACLE_PWD@FREE as sysdba
</syntaxhighlight>

<syntaxhighlight lang="sql">
SELECT privilege
FROM dba_sys_privs
WHERE grantee = 'MAXIMO'
ORDER BY privilege;

EXIT
</syntaxhighlight>

Expected privileges should include:
<pre>
ALTER SESSION
CONNECT
CREATE JOB
CREATE PROCEDURE
CREATE SEQUENCE
CREATE SESSION
CREATE SYNONYM
CREATE TABLE
CREATE TRIGGER
CREATE VIEW
SYSDBA
</pre>

=== Step 3.4: Verify SYSDBA Access ===

Test that MAXIMO can connect with SYSDBA privilege:

<syntaxhighlight lang="bash">
sqlplus MAXIMO/Maximo_123@FREE as sysdba
</syntaxhighlight>

<syntaxhighlight lang="sql">
SELECT USER, SYS_CONTEXT('USERENV', 'ISDBA') AS IS_DBA FROM DUAL;

EXIT
</syntaxhighlight>

=== Step 3.5: Test Maximo User Connection ===

<syntaxhighlight lang="bash">
sqlplus MAXIMO/Maximo_123@FREE
</syntaxhighlight>

<syntaxhighlight lang="sql">
SELECT USER FROM DUAL;

EXIT
</syntaxhighlight>

Expected output:
<pre>
USER
------
MAXIMO
</pre>

=== Step 3.6: Verify Tables in MAXIMO Schema ===

Check if any tables have been created in the MAXIMO schema:

<syntaxhighlight lang="bash">
sqlplus MAXIMO/Maximo_123@FREE
</syntaxhighlight>

<syntaxhighlight lang="sql">
-- Count total tables
SELECT COUNT(*) AS table_count FROM user_tables;

-- define line size
SET LINESIZE 200
COL TABLE_NAME FORMAT A30
COL NUM_ROWS FORMAT 9999999
COL TABLESPACE_NAME FORMAT A20

-- List all tables (if any exist)
SELECT table_name, num_rows, tablespace_name
FROM user_tables
ORDER BY table_name;

EXIT
</syntaxhighlight>

Expected output (before Maximo installation):
<pre>
TABLE_COUNT
-----------
0

no rows selected
</pre>

After Maximo installation, you should see Maximo tables like:
<pre>
TABLE_NAME NUM_ROWS TABLESPACE_NAME
------------------- -------- ---------------
ASSET 0 MAXDATA
PERSON 0 MAXDATA
WORKORDER 0 MAXDATA
...
</pre>

Alternative command to check tables from SYS user:

<syntaxhighlight lang="bash">
sqlplus sys/$ORACLE_PWD@FREE as sysdba
</syntaxhighlight>

<syntaxhighlight lang="sql">
-- Check tables owned by MAXIMO
SELECT owner, table_name, tablespace_name, num_rows
FROM dba_tables
WHERE owner = 'MAXIMO'
ORDER BY table_name;

-- Count tables by owner
SELECT owner, COUNT(*) AS table_count
FROM dba_tables
WHERE owner = 'MAXIMO'
GROUP BY owner;

EXIT
</syntaxhighlight>

=== Step 3.7: Exit Container ===

After verification, exit the container:

<syntaxhighlight lang="bash">
exit
</syntaxhighlight>

== Step 4: Configure Maximo Application Suite Connection ==

=== Connection Details ===

Use the following connection details in your Maximo Application Suite JDBC configuration:

* '''Database Type''': Oracle
* '''Host''': `oracle-db-svc` (or `oracle-db-svc.<namespace>.svc.cluster.local`)
* '''Port''': `1521`
* '''Service Name''': `FREE`
* '''Schema''': `MAXIMO`
* '''Username''': `MAXIMO`
* '''Password''': `Maximo_123`
* '''JDBC URL''': `jdbc:oracle:thin:@oracle-db-svc:1521/FREE`

=== Sample JDBC Configuration ===

this work for me!

File: jdbc-lab01-manage.yaml

<syntaxhighlight lang="yaml">
---
apiVersion: v1
kind: Secret
type: Opaque
metadata:
name: "jdbc-ws01-manage-credentials"
namespace: "mas-lab01-core"
stringData:
username: "MAXIMO"
password: "Maximo_123"
---
apiVersion: config.mas.ibm.com/v1
kind: JdbcCfg
metadata:
name: "lab01-jdbc-wsapp-ws01-manage"
namespace: "mas-lab01-core"
labels:
'mas.ibm.com/configScope': 'system'
'mas.ibm.com/instanceId': 'lab01'
'mas.ibm.com/workspaceId': 'ws01'
'mas.ibm.com/applicationId': 'manage'
spec:
displayName: "JDBC WS01 Manage"
config:
url: "jdbc:oracle:thin:@oracle-db-svc.oracle-maxdb.svc:1521/FREE"
sslEnabled: False
credentials:
secretName: "jdbc-ws01-manage-credentials"

</syntaxhighlight>

Another sample

=== Create JDBC Secret for MAS ===

<syntaxhighlight lang="bash">
oc create secret generic jdbc-ws01-manage-credentials \
--from-literal=username=MAXIMO \
--from-literal=password='Maximo_123' \
--from-literal=url='jdbc:oracle:thin:@oracle-db-svc:1521/FREE'
</syntaxhighlight>

<syntaxhighlight lang="yaml">
apiVersion: config.mas.ibm.com/v1
kind: JdbcCfg
metadata:
name: maximo-jdbc-config
namespace: mas-<instance-id>-core
spec:
certificates:
- alias: oracle-cert
crt: |
-----BEGIN CERTIFICATE-----
<certificate content if using SSL>
-----END CERTIFICATE-----
config:
credentials:
secretName: maximo-jdbc-secret
driverOptions: {}
sslEnabled: false
url: jdbc:oracle:thin:@oracle-db-svc:1521/FREE
displayName: Maximo Oracle Database
type: external
</syntaxhighlight>

= See Also =

* [[Cloud|Articles about Cloud]]
* [[IBM_Maximo|More Articles about IBM_Maximo]]

[[Category:IBM Maximo]]
[[Category:IBM MAS]]

IBM Maximo: Installing MAS Core + Manage + Oracle DB Container

2026-05-03T16:12:39Z

Ebasso: /* See Also */

= Prepare Oracle DB =

# [[Oracle: Run Oracle DB on Redhat OpenShift]]
# [[IBM Maximo: Creating Maximo Database on Oracle Database Free Edition (Container)]]

= Installing MAS Core via MAS CLI =

Run the container:

mkdir -p mas-cli-workspace/masconfig

cp license.dat mas-cli-workspace/.

===Create Sample JDBC Configuration===

File: mas-cli-workspace/masconfig/jdbc-lab01-manage.yaml

<syntaxhighlight lang="yaml">
---
apiVersion: v1
kind: Secret
type: Opaque
metadata:
name: "jdbc-ws01-manage-credentials"
namespace: "mas-lab01-core"
stringData:
username: "MAXIMO"
password: "Maximo_123"
---
apiVersion: config.mas.ibm.com/v1
kind: JdbcCfg
metadata:
name: "lab01-jdbc-wsapp-ws01-manage"
namespace: "mas-lab01-core"
labels:
'mas.ibm.com/configScope': 'system'
'mas.ibm.com/instanceId': 'lab01'
'mas.ibm.com/workspaceId': 'ws01'
'mas.ibm.com/applicationId': 'manage'
spec:
displayName: "JDBC WS01 Manage"
config:
url: "jdbc:oracle:thin:@oracle-db-svc.oracle-maxdb.svc:1521/FREE"
sslEnabled: False
credentials:
secretName: "jdbc-ws01-manage-credentials"

</syntaxhighlight>

= MAS Installation =

podman run -it --rm -v $(pwd)/mas-cli-workspace:/mnt/home:Z --pull always quay.io/ibmmas/cli:latest

for Mac (Apple Silicon M1) add '''--arch arm64'''

Run the MAS installation:

export IBM_ENTITLEMENT_KEY=x
export STORAGE_CLASS_RWO=ocs-storagecluster-cephfs
export STORAGE_CLASS_RWM=ocs-storagecluster-cephfs

mas install --mas-catalog-version v9-260430-amd64 --ibm-entitlement-key $IBM_ENTITLEMENT_KEY \
--mas-channel 9.1.x --mas-instance-id lab01 --mas-workspace-id ws01 --mas-workspace-name "Lab Workspace" \
'''--additional-configs "/mnt/home/masconfigs"''' \
<nowiki>--non-prod \
--storage-class-rwo $STORAGE_CLASS_RWO --storage-class-rwx $STORAGE_CLASS_RWM \
--storage-pipeline $STORAGE_CLASS_RWM --storage-accessmode "ReadWriteMany" \
--license-file "/mnt/home/license.dat" \
--contact-email "lab@company.com" --contact-firstname "Lab" --contact-lastname "User" \
--mongodb-namespace "mongoce" \
--grafana-v5-namespace "grafana5" \
--grafana-instance-storage-size "10Gi" \
--manage-channel "9.1.x" \
--manage-jdbc "workspace-application" \
--manage-components "base=latest" \
--manage-server-bundle-size "dev" \
--manage-demodata \
--manage-base-language "EN" \
--manage-secondary-languages "PT-BR" \
--accept-license --no-confirm
</nowiki>

= See Also =

* [[Cloud|Articles about Cloud]]
* [[IBM_Maximo|More Articles about IBM_Maximo]]

[[Category:IBM Maximo]]
[[Category:IBM MAS]]

IBM Maximo: Installing MAS Core + Manage + Oracle DB Container

2026-05-03T16:12:11Z

Ebasso: /* See Also */

= Prepare Oracle DB =

# [[Oracle: Run Oracle DB on Redhat OpenShift]]
# [[IBM Maximo: Creating Maximo Database on Oracle Database Free Edition (Container)]]

= Installing MAS Core via MAS CLI =

Run the container:

mkdir -p mas-cli-workspace/masconfig

cp license.dat mas-cli-workspace/.

===Create Sample JDBC Configuration===

File: mas-cli-workspace/masconfig/jdbc-lab01-manage.yaml

<syntaxhighlight lang="yaml">
---
apiVersion: v1
kind: Secret
type: Opaque
metadata:
name: "jdbc-ws01-manage-credentials"
namespace: "mas-lab01-core"
stringData:
username: "MAXIMO"
password: "Maximo_123"
---
apiVersion: config.mas.ibm.com/v1
kind: JdbcCfg
metadata:
name: "lab01-jdbc-wsapp-ws01-manage"
namespace: "mas-lab01-core"
labels:
'mas.ibm.com/configScope': 'system'
'mas.ibm.com/instanceId': 'lab01'
'mas.ibm.com/workspaceId': 'ws01'
'mas.ibm.com/applicationId': 'manage'
spec:
displayName: "JDBC WS01 Manage"
config:
url: "jdbc:oracle:thin:@oracle-db-svc.oracle-maxdb.svc:1521/FREE"
sslEnabled: False
credentials:
secretName: "jdbc-ws01-manage-credentials"

</syntaxhighlight>

= MAS Installation =

podman run -it --rm -v $(pwd)/mas-cli-workspace:/mnt/home:Z --pull always quay.io/ibmmas/cli:latest

for Mac (Apple Silicon M1) add '''--arch arm64'''

Run the MAS installation:

export IBM_ENTITLEMENT_KEY=x
export STORAGE_CLASS_RWO=ocs-storagecluster-cephfs
export STORAGE_CLASS_RWM=ocs-storagecluster-cephfs

mas install --mas-catalog-version v9-260430-amd64 --ibm-entitlement-key $IBM_ENTITLEMENT_KEY \
--mas-channel 9.1.x --mas-instance-id lab01 --mas-workspace-id ws01 --mas-workspace-name "Lab Workspace" \
'''--additional-configs "/mnt/home/masconfigs"''' \
<nowiki>--non-prod \
--storage-class-rwo $STORAGE_CLASS_RWO --storage-class-rwx $STORAGE_CLASS_RWM \
--storage-pipeline $STORAGE_CLASS_RWM --storage-accessmode "ReadWriteMany" \
--license-file "/mnt/home/license.dat" \
--contact-email "lab@company.com" --contact-firstname "Lab" --contact-lastname "User" \
--mongodb-namespace "mongoce" \
--grafana-v5-namespace "grafana5" \
--grafana-instance-storage-size "10Gi" \
--manage-channel "9.1.x" \
--manage-jdbc "workspace-application" \
--manage-components "base=latest" \
--manage-server-bundle-size "dev" \
--manage-demodata \
--manage-base-language "EN" \
--manage-secondary-languages "PT-BR" \
--accept-license --no-confirm
</nowiki>

= See Also =

* [[Cloud|Articles about Cloud]]
* [[IBM_Maximo|More Articles about IBM_Maximo]]

[[Category:IBM Maximo]]

[[Category:IBM Maximo]]

IBM Maximo: Installing MAS Core + Manage + Oracle DB Container

2026-05-03T16:12:00Z

Ebasso: /* See Also */

= Prepare Oracle DB =

# [[Oracle: Run Oracle DB on Redhat OpenShift]]
# [[IBM Maximo: Creating Maximo Database on Oracle Database Free Edition (Container)]]

= Installing MAS Core via MAS CLI =

Run the container:

mkdir -p mas-cli-workspace/masconfig

cp license.dat mas-cli-workspace/.

===Create Sample JDBC Configuration===

File: mas-cli-workspace/masconfig/jdbc-lab01-manage.yaml

<syntaxhighlight lang="yaml">
---
apiVersion: v1
kind: Secret
type: Opaque
metadata:
name: "jdbc-ws01-manage-credentials"
namespace: "mas-lab01-core"
stringData:
username: "MAXIMO"
password: "Maximo_123"
---
apiVersion: config.mas.ibm.com/v1
kind: JdbcCfg
metadata:
name: "lab01-jdbc-wsapp-ws01-manage"
namespace: "mas-lab01-core"
labels:
'mas.ibm.com/configScope': 'system'
'mas.ibm.com/instanceId': 'lab01'
'mas.ibm.com/workspaceId': 'ws01'
'mas.ibm.com/applicationId': 'manage'
spec:
displayName: "JDBC WS01 Manage"
config:
url: "jdbc:oracle:thin:@oracle-db-svc.oracle-maxdb.svc:1521/FREE"
sslEnabled: False
credentials:
secretName: "jdbc-ws01-manage-credentials"

</syntaxhighlight>

= MAS Installation =

podman run -it --rm -v $(pwd)/mas-cli-workspace:/mnt/home:Z --pull always quay.io/ibmmas/cli:latest

for Mac (Apple Silicon M1) add '''--arch arm64'''

Run the MAS installation:

export IBM_ENTITLEMENT_KEY=x
export STORAGE_CLASS_RWO=ocs-storagecluster-cephfs
export STORAGE_CLASS_RWM=ocs-storagecluster-cephfs

mas install --mas-catalog-version v9-260430-amd64 --ibm-entitlement-key $IBM_ENTITLEMENT_KEY \
--mas-channel 9.1.x --mas-instance-id lab01 --mas-workspace-id ws01 --mas-workspace-name "Lab Workspace" \
'''--additional-configs "/mnt/home/masconfigs"''' \
<nowiki>--non-prod \
--storage-class-rwo $STORAGE_CLASS_RWO --storage-class-rwx $STORAGE_CLASS_RWM \
--storage-pipeline $STORAGE_CLASS_RWM --storage-accessmode "ReadWriteMany" \
--license-file "/mnt/home/license.dat" \
--contact-email "lab@company.com" --contact-firstname "Lab" --contact-lastname "User" \
--mongodb-namespace "mongoce" \
--grafana-v5-namespace "grafana5" \
--grafana-instance-storage-size "10Gi" \
--manage-channel "9.1.x" \
--manage-jdbc "workspace-application" \
--manage-components "base=latest" \
--manage-server-bundle-size "dev" \
--manage-demodata \
--manage-base-language "EN" \
--manage-secondary-languages "PT-BR" \
--accept-license --no-confirm
</nowiki>

= See Also =

* [[Cloud|Articles about Cloud]]
* [[IBM_Maximo|More Articles about IBM_Maximo]]

[[Category:IBM Maximo]]

= See Also =

* [[Cloud|Articles about Cloud]]
* [[Technologies|More Articles about Cloud / Web Development / Technologies]]

[[Category:IBM Maximo]]

IBM Maximo: Installing MAS Core + Manage + Oracle DB Container

2026-05-03T16:09:57Z

Ebasso: /* MAS Installation */

= Prepare Oracle DB =

# [[Oracle: Run Oracle DB on Redhat OpenShift]]
# [[IBM Maximo: Creating Maximo Database on Oracle Database Free Edition (Container)]]

= Installing MAS Core via MAS CLI =

Run the container:

mkdir -p mas-cli-workspace/masconfig

cp license.dat mas-cli-workspace/.

===Create Sample JDBC Configuration===

File: mas-cli-workspace/masconfig/jdbc-lab01-manage.yaml

<syntaxhighlight lang="yaml">
---
apiVersion: v1
kind: Secret
type: Opaque
metadata:
name: "jdbc-ws01-manage-credentials"
namespace: "mas-lab01-core"
stringData:
username: "MAXIMO"
password: "Maximo_123"
---
apiVersion: config.mas.ibm.com/v1
kind: JdbcCfg
metadata:
name: "lab01-jdbc-wsapp-ws01-manage"
namespace: "mas-lab01-core"
labels:
'mas.ibm.com/configScope': 'system'
'mas.ibm.com/instanceId': 'lab01'
'mas.ibm.com/workspaceId': 'ws01'
'mas.ibm.com/applicationId': 'manage'
spec:
displayName: "JDBC WS01 Manage"
config:
url: "jdbc:oracle:thin:@oracle-db-svc.oracle-maxdb.svc:1521/FREE"
sslEnabled: False
credentials:
secretName: "jdbc-ws01-manage-credentials"

</syntaxhighlight>

= MAS Installation =

podman run -it --rm -v $(pwd)/mas-cli-workspace:/mnt/home:Z --pull always quay.io/ibmmas/cli:latest

for Mac (Apple Silicon M1) add '''--arch arm64'''

Run the MAS installation:

export IBM_ENTITLEMENT_KEY=x
export STORAGE_CLASS_RWO=ocs-storagecluster-cephfs
export STORAGE_CLASS_RWM=ocs-storagecluster-cephfs

mas install --mas-catalog-version v9-260430-amd64 --ibm-entitlement-key $IBM_ENTITLEMENT_KEY \
--mas-channel 9.1.x --mas-instance-id lab01 --mas-workspace-id ws01 --mas-workspace-name "Lab Workspace" \
'''--additional-configs "/mnt/home/masconfigs"''' \
<nowiki>--non-prod \
--storage-class-rwo $STORAGE_CLASS_RWO --storage-class-rwx $STORAGE_CLASS_RWM \
--storage-pipeline $STORAGE_CLASS_RWM --storage-accessmode "ReadWriteMany" \
--license-file "/mnt/home/license.dat" \
--contact-email "lab@company.com" --contact-firstname "Lab" --contact-lastname "User" \
--mongodb-namespace "mongoce" \
--grafana-v5-namespace "grafana5" \
--grafana-instance-storage-size "10Gi" \
--manage-channel "9.1.x" \
--manage-jdbc "workspace-application" \
--manage-components "base=latest" \
--manage-server-bundle-size "dev" \
--manage-demodata \
--manage-base-language "EN" \
--manage-secondary-languages "PT-BR" \
--accept-license --no-confirm
</nowiki>

= See Also =

* [[Cloud|Articles about Cloud]]
* [[Technologies|More Articles about Cloud / Web Development / Technologies]]

[[Category:IBM Maximo]]

= See Also =

* [[Cloud|Articles about Cloud]]
* [[Technologies|More Articles about Cloud / Web Development / Technologies]]

[[Category:IBM Maximo]]

IBM Maximo: Installing MAS Core + Manage + Oracle DB Container

2026-05-03T16:09:45Z

Ebasso: /* MAS Installation */

= Prepare Oracle DB =

# [[Oracle: Run Oracle DB on Redhat OpenShift]]
# [[IBM Maximo: Creating Maximo Database on Oracle Database Free Edition (Container)]]

= Installing MAS Core via MAS CLI =

Run the container:

mkdir -p mas-cli-workspace/masconfig

cp license.dat mas-cli-workspace/.

===Create Sample JDBC Configuration===

File: mas-cli-workspace/masconfig/jdbc-lab01-manage.yaml

<syntaxhighlight lang="yaml">
---
apiVersion: v1
kind: Secret
type: Opaque
metadata:
name: "jdbc-ws01-manage-credentials"
namespace: "mas-lab01-core"
stringData:
username: "MAXIMO"
password: "Maximo_123"
---
apiVersion: config.mas.ibm.com/v1
kind: JdbcCfg
metadata:
name: "lab01-jdbc-wsapp-ws01-manage"
namespace: "mas-lab01-core"
labels:
'mas.ibm.com/configScope': 'system'
'mas.ibm.com/instanceId': 'lab01'
'mas.ibm.com/workspaceId': 'ws01'
'mas.ibm.com/applicationId': 'manage'
spec:
displayName: "JDBC WS01 Manage"
config:
url: "jdbc:oracle:thin:@oracle-db-svc.oracle-maxdb.svc:1521/FREE"
sslEnabled: False
credentials:
secretName: "jdbc-ws01-manage-credentials"

</syntaxhighlight>

= MAS Installation =

podman run -it --rm -v $(pwd)/mas-cli-workspace:/mnt/home:Z --pull always quay.io/ibmmas/cli:latest

for Mac (Apple Silicon M1) add '''--arch arm64'''

Run the MAS installation:

export IBM_ENTITLEMENT_KEY=x
export STORAGE_CLASS_RWO=ocs-storagecluster-cephfs
export STORAGE_CLASS_RWM=ocs-storagecluster-cephfs

mas install --mas-catalog-version v9-260430-amd64 --ibm-entitlement-key $IBM_ENTITLEMENT_KEY \
--mas-channel 9.1.x --mas-instance-id lab01 --mas-workspace-id ws01 --mas-workspace-name "Lab Workspace" \
'''--additional-configs "/mnt/home/masconfigs"''' \
<nowiki>--non-prod \
--storage-class-rwo $STORAGE_CLASS_RWO --storage-class-rwx $STORAGE_CLASS_RWM \
--storage-pipeline $STORAGE_CLASS_RWM --storage-accessmode "ReadWriteMany" \
--license-file "/mnt/home/license.dat" \
--contact-email "lab@company.com" --contact-firstname "Lab" --contact-lastname "User" \
--mongodb-namespace "mongoce" \
--grafana-v5-namespace "grafana5" \
--grafana-instance-storage-size "10Gi" \
--manage-channel "9.1.x" \
--manage-jdbc "workspace-application" \
--manage-components "base=latest" \
--manage-server-bundle-size "dev" \
--manage-demodata \
--manage-base-language "EN" \
--manage-secondary-languages "PT-BR" \
--accept-license --no-confirm
</nowiki>

= See Also =

* [[Cloud|Articles about Cloud]]
* [[Technologies|More Articles about Cloud / Web Development / Technologies]]

[[Category:IBM Maximo]]

= See Also =

* [[Cloud|Articles about Cloud]]
* [[Technologies|More Articles about Cloud / Web Development / Technologies]]

[[Category:IBM Maximo]]

IBM Maximo: Installing MAS Core + Manage + Oracle DB Container

2026-05-03T16:08:50Z

Ebasso: /* MAS Installation */

= Prepare Oracle DB =

# [[Oracle: Run Oracle DB on Redhat OpenShift]]
# [[IBM Maximo: Creating Maximo Database on Oracle Database Free Edition (Container)]]

= Installing MAS Core via MAS CLI =

Run the container:

mkdir -p mas-cli-workspace/masconfig

cp license.dat mas-cli-workspace/.

===Create Sample JDBC Configuration===

File: mas-cli-workspace/masconfig/jdbc-lab01-manage.yaml

<syntaxhighlight lang="yaml">
---
apiVersion: v1
kind: Secret
type: Opaque
metadata:
name: "jdbc-ws01-manage-credentials"
namespace: "mas-lab01-core"
stringData:
username: "MAXIMO"
password: "Maximo_123"
---
apiVersion: config.mas.ibm.com/v1
kind: JdbcCfg
metadata:
name: "lab01-jdbc-wsapp-ws01-manage"
namespace: "mas-lab01-core"
labels:
'mas.ibm.com/configScope': 'system'
'mas.ibm.com/instanceId': 'lab01'
'mas.ibm.com/workspaceId': 'ws01'
'mas.ibm.com/applicationId': 'manage'
spec:
displayName: "JDBC WS01 Manage"
config:
url: "jdbc:oracle:thin:@oracle-db-svc.oracle-maxdb.svc:1521/FREE"
sslEnabled: False
credentials:
secretName: "jdbc-ws01-manage-credentials"

</syntaxhighlight>

= MAS Installation =

podman run -it --rm -v $(pwd)/mas-cli-workspace:/mnt/home:Z --pull always quay.io/ibmmas/cli:latest

for Mac (Apple Silicon M1) add '''--arch arm64'''

Run the MAS installation:

export IBM_ENTITLEMENT_KEY=x
export STORAGE_CLASS_RWO=ocs-storagecluster-cephfs
export STORAGE_CLASS_RWM=ocs-storagecluster-cephfs

mas install --mas-catalog-version v9-260430-amd64 --ibm-entitlement-key $IBM_ENTITLEMENT_KEY \
--mas-channel 9.1.x --mas-instance-id lab01 --mas-workspace-id ws01 --mas-workspace-name "Lab Workspace" \
'''--additional-configs "/mnt/home/masconfigs"''' \
<nowiki>--non-prod \
--storage-class-rwo $STORAGE_CLASS_RWO --storage-class-rwx $STORAGE_CLASS_RWM \
--storage-pipeline $STORAGE_CLASS_RWM --storage-accessmode "ReadWriteMany" \
--license-file "/mnt/home/license.dat" \
--contact-email "lab@company.com" --contact-firstname "Lab" --contact-lastname "User" \
--mongodb-namespace "mongoce" \
--grafana-v5-namespace "grafana5" \
--grafana-instance-storage-size "10Gi" \
--manage-channel "9.1.x" \
--manage-jdbc "workspace-application" \
--manage-components "base=latest" \
--manage-server-bundle-size "dev" \
--manage-demodata \
--manage-base-language "EN" \
--manage-secondary-languages "PT-BR" \
--accept-license --no-confirm
</nowiki>

= See Also =

* [[Cloud|Articles about Cloud]]
* [[Technologies|More Articles about Cloud / Web Development / Technologies]]

[[Category:IBM Maximo]]

= See Also =

* [[Cloud|Articles about Cloud]]
* [[Technologies|More Articles about Cloud / Web Development / Technologies]]

[[Category:IBM Maximo]]

IBM Maximo: Installing MAS Core + Manage + Oracle DB Container

2026-05-03T16:08:06Z

Ebasso: /* MAS Installation */

= Prepare Oracle DB =

# [[Oracle: Run Oracle DB on Redhat OpenShift]]
# [[IBM Maximo: Creating Maximo Database on Oracle Database Free Edition (Container)]]

= Installing MAS Core via MAS CLI =

Run the container:

mkdir -p mas-cli-workspace/masconfig

cp license.dat mas-cli-workspace/.

===Create Sample JDBC Configuration===

File: mas-cli-workspace/masconfig/jdbc-lab01-manage.yaml

<syntaxhighlight lang="yaml">
---
apiVersion: v1
kind: Secret
type: Opaque
metadata:
name: "jdbc-ws01-manage-credentials"
namespace: "mas-lab01-core"
stringData:
username: "MAXIMO"
password: "Maximo_123"
---
apiVersion: config.mas.ibm.com/v1
kind: JdbcCfg
metadata:
name: "lab01-jdbc-wsapp-ws01-manage"
namespace: "mas-lab01-core"
labels:
'mas.ibm.com/configScope': 'system'
'mas.ibm.com/instanceId': 'lab01'
'mas.ibm.com/workspaceId': 'ws01'
'mas.ibm.com/applicationId': 'manage'
spec:
displayName: "JDBC WS01 Manage"
config:
url: "jdbc:oracle:thin:@oracle-db-svc.oracle-maxdb.svc:1521/FREE"
sslEnabled: False
credentials:
secretName: "jdbc-ws01-manage-credentials"

</syntaxhighlight>

= MAS Installation =

podman run -it --rm -v $(pwd)/mas-cli-workspace:/mnt/home:Z --pull always quay.io/ibmmas/cli:latest

for Mac (Apple Silicon M1) add '''--arch arm64'''

Run the MAS installation:

<nowiki>export IBM_ENTITLEMENT_KEY=x
export STORAGE_CLASS_RWO=ocs-storagecluster-cephfs
export STORAGE_CLASS_RWM=ocs-storagecluster-cephfs

mas install --mas-catalog-version v9-260430-amd64 --ibm-entitlement-key $IBM_ENTITLEMENT_KEY \
--mas-channel 9.1.x --mas-instance-id lab01 --mas-workspace-id ws01 --mas-workspace-name "Lab Workspace" \
/nowiki>
'''--additional-configs "/mnt/home/masconfigs"''' \
<nowiki>--non-prod \
--storage-class-rwo $STORAGE_CLASS_RWO --storage-class-rwx $STORAGE_CLASS_RWM \
--storage-pipeline $STORAGE_CLASS_RWM --storage-accessmode "ReadWriteMany" \
--license-file "/mnt/home/license.dat" \
--contact-email "lab@company.com" --contact-firstname "Lab" --contact-lastname "User" \
--mongodb-namespace "mongoce" \
--grafana-v5-namespace "grafana5" \
--grafana-instance-storage-size "10Gi" \
--manage-channel "9.1.x" \
--manage-jdbc "workspace-application" \
--manage-components "base=latest" \
--manage-server-bundle-size "dev" \
--manage-demodata \
--manage-base-language "EN" \
--manage-secondary-languages "PT-BR" \
--accept-license --no-confirm
</nowiki>

= See Also =

* [[Cloud|Articles about Cloud]]
* [[Technologies|More Articles about Cloud / Web Development / Technologies]]

[[Category:IBM Maximo]]

= See Also =

* [[Cloud|Articles about Cloud]]
* [[Technologies|More Articles about Cloud / Web Development / Technologies]]

[[Category:IBM Maximo]]

IBM Maximo: Installing MAS Core + Manage + Oracle DB Container

2026-05-03T16:07:38Z

Ebasso: /* MAS Installation */

= Prepare Oracle DB =

# [[Oracle: Run Oracle DB on Redhat OpenShift]]
# [[IBM Maximo: Creating Maximo Database on Oracle Database Free Edition (Container)]]

= Installing MAS Core via MAS CLI =

Run the container:

mkdir -p mas-cli-workspace/masconfig

cp license.dat mas-cli-workspace/.

===Create Sample JDBC Configuration===

File: mas-cli-workspace/masconfig/jdbc-lab01-manage.yaml

<syntaxhighlight lang="yaml">
---
apiVersion: v1
kind: Secret
type: Opaque
metadata:
name: "jdbc-ws01-manage-credentials"
namespace: "mas-lab01-core"
stringData:
username: "MAXIMO"
password: "Maximo_123"
---
apiVersion: config.mas.ibm.com/v1
kind: JdbcCfg
metadata:
name: "lab01-jdbc-wsapp-ws01-manage"
namespace: "mas-lab01-core"
labels:
'mas.ibm.com/configScope': 'system'
'mas.ibm.com/instanceId': 'lab01'
'mas.ibm.com/workspaceId': 'ws01'
'mas.ibm.com/applicationId': 'manage'
spec:
displayName: "JDBC WS01 Manage"
config:
url: "jdbc:oracle:thin:@oracle-db-svc.oracle-maxdb.svc:1521/FREE"
sslEnabled: False
credentials:
secretName: "jdbc-ws01-manage-credentials"

</syntaxhighlight>

= MAS Installation =

podman run -it --rm -v $(pwd)/mas-cli-workspace:/mnt/home:Z --pull always quay.io/ibmmas/cli:latest

for Mac (Apple Silicon M1) add '''--arch arm64'''

Run the MAS installation:

<nowiki>export IBM_ENTITLEMENT_KEY=x
export STORAGE_CLASS_RWO=ocs-storagecluster-cephfs
export STORAGE_CLASS_RWM=ocs-storagecluster-cephfs

mas install --mas-catalog-version v9-260430-amd64 --ibm-entitlement-key $IBM_ENTITLEMENT_KEY \
--mas-channel 9.1.x --mas-instance-id lab01 --mas-workspace-id ws01 --mas-workspace-name "Lab Workspace" \
'''--additional-configs "/mnt/home/masconfigs"''' \
--non-prod \
--storage-class-rwo $STORAGE_CLASS_RWO --storage-class-rwx $STORAGE_CLASS_RWM \
--storage-pipeline $STORAGE_CLASS_RWM --storage-accessmode "ReadWriteMany" \
--license-file "/mnt/home/license.dat" \
--contact-email "lab@company.com" --contact-firstname "Lab" --contact-lastname "User" \
--mongodb-namespace "mongoce" \
--grafana-v5-namespace "grafana5" \
--grafana-instance-storage-size "10Gi" \
--manage-channel "9.1.x" \
--manage-jdbc "workspace-application" \
--manage-components "base=latest" \
--manage-server-bundle-size "dev" \
--manage-demodata \
--manage-base-language "EN" \
--manage-secondary-languages "PT-BR" \
--accept-license --no-confirm
</nowiki>

= See Also =

* [[Cloud|Articles about Cloud]]
* [[Technologies|More Articles about Cloud / Web Development / Technologies]]

[[Category:IBM Maximo]]

= See Also =

* [[Cloud|Articles about Cloud]]
* [[Technologies|More Articles about Cloud / Web Development / Technologies]]

[[Category:IBM Maximo]]