Wiki - User contributions [en]

IBM Maximo: Migrate MAXDB to RH OpenShift

2026-04-08T00:17:26Z

Ebasso: /* Checking restored database */

= Create MAXDB database =

1) Install DB2 Operator

2) Create a New instance of DB2.

Open the DB2 Operator -> DB2 Cluster -> New cluster.

Get yaml file on this Article [[IBM Maximo: Migrate MAXDB to RH OpenShift (db2ucmas76-01.yaml)]]

Paste inside yaml form and click on create

= Copy backup file into Container =

Define db2 project on openshift

oc project db2u

Check pods

oc get pods

Copy backup file

oc cp MAXDB76.0.___.001.zip c-db2ucmas76-02-db2u-0:/mnt/backup/MAXDB76.0.___.001.zip

Login on container

oc rsh c-db2ucmas76-02-db2u-0

Extract file

cd /mnt/backup
unzip MAXDB76.0.___.001.zip
chmod a+rw MAX*

List

<nowiki>ls -l
total 7121740
-rw-rw-rw-. 1 db2uadm db2iadm1 7095119872 Sep 13 2022 MAXDB76.0.ctginst1.DBPART000.20220913055916.001
-rw-rw-rw-. 1 db2uadm db2iadm1 197538909 Apr 7 21:15 MAXDB76.0.ctginst1.DBPART000.20220913055916.001.zip
</nowiki>

Change user

su - db2inst1

Check backup

db2ckbkp -H /mnt/backup/MAXDB76.0.ctginst1.DBPART000.20220913055916.001

This command is generate the following file: [[IBM Maximo: Migrate MAXDB to RH OpenShift (db2ckbkp.out)]]

= Restore MAXDB76 backup file into Container =

This command will export data from backup file

su - db2inst1

cd /mnt/backup

db2 restore database MAXDB76 redirect generate script restoresql.sql

This command is generate the following file: [[IBM Maximo: Migrate MAXDB to RH OpenShift (restoresql.sql)]]

This can help to change parameters on restore.

Prepare db2

db2 force applications all
db2 terminate
db2 deactivate database MAXDB
db2 drop database MAXDB

Create directories

mkdir -p /mnt/bludata0/MAXDB
mkdir -p /mnt/tempts/c-db2ucmas76-05-db2u/MAXDB

Start RESTORE with REDIRECT

<nowiki>db2 "RESTORE DATABASE MAXDB76 FROM '/mnt/backup' TAKEN AT 20220913055916 INTO MAXDB REPLACE HISTORY FILE REPLACE EXISTING REDIRECT WITHOUT ROLLING FORWARD WITHOUT PROMPTING"</nowiki>

Configure Storage Group

db2 "SET STOGROUP PATHS FOR IBMSTOGROUP ON '/mnt/bludata0'"

Continue the RESTORE

db2 "RESTORE DATABASE MAXDB76 CONTINUE"

= Checking restored database =

Connect to database

db2 connect to MAXDB

Verify tablespaces

db2 list tablespaces show detail

Verify containers

db2 list tablespace containers for 0 show detail
db2 list tablespace containers for 5 show detail
db2 list tablespace containers for 6 show detail

Verify storage group

db2 "select * from syscat.stogroups"
db2 "select * from syscat.storagepaths"

Verify data (tables)

db2 "select count(*) from syscat.tables"

db2 "select tabschema, tabname, card from syscat.tables where tabschema not like 'SYS%' fetch first 10 rows only"

= Ver também =

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

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

IBM Maximo: Migrate MAXDB to RH OpenShift

2026-04-08T00:13:53Z

Ebasso: /* Restore MAXDB76 backup file into Container */

= Create MAXDB database =

1) Install DB2 Operator

2) Create a New instance of DB2.

Open the DB2 Operator -> DB2 Cluster -> New cluster.

Get yaml file on this Article [[IBM Maximo: Migrate MAXDB to RH OpenShift (db2ucmas76-01.yaml)]]

Paste inside yaml form and click on create

= Copy backup file into Container =

Define db2 project on openshift

oc project db2u

Check pods

oc get pods

Copy backup file

oc cp MAXDB76.0.___.001.zip c-db2ucmas76-02-db2u-0:/mnt/backup/MAXDB76.0.___.001.zip

Login on container

oc rsh c-db2ucmas76-02-db2u-0

Extract file

cd /mnt/backup
unzip MAXDB76.0.___.001.zip
chmod a+rw MAX*

List

<nowiki>ls -l
total 7121740
-rw-rw-rw-. 1 db2uadm db2iadm1 7095119872 Sep 13 2022 MAXDB76.0.ctginst1.DBPART000.20220913055916.001
-rw-rw-rw-. 1 db2uadm db2iadm1 197538909 Apr 7 21:15 MAXDB76.0.ctginst1.DBPART000.20220913055916.001.zip
</nowiki>

Change user

su - db2inst1

Check backup

db2ckbkp -H /mnt/backup/MAXDB76.0.ctginst1.DBPART000.20220913055916.001

This command is generate the following file: [[IBM Maximo: Migrate MAXDB to RH OpenShift (db2ckbkp.out)]]

= Restore MAXDB76 backup file into Container =

This command will export data from backup file

su - db2inst1

cd /mnt/backup

db2 restore database MAXDB76 redirect generate script restoresql.sql

This command is generate the following file: [[IBM Maximo: Migrate MAXDB to RH OpenShift (restoresql.sql)]]

This can help to change parameters on restore.

Prepare db2

db2 force applications all
db2 terminate
db2 deactivate database MAXDB
db2 drop database MAXDB

Create directories

mkdir -p /mnt/bludata0/MAXDB
mkdir -p /mnt/tempts/c-db2ucmas76-05-db2u/MAXDB

Start RESTORE with REDIRECT

<nowiki>db2 "RESTORE DATABASE MAXDB76 FROM '/mnt/backup' TAKEN AT 20220913055916 INTO MAXDB REPLACE HISTORY FILE REPLACE EXISTING REDIRECT WITHOUT ROLLING FORWARD WITHOUT PROMPTING"</nowiki>

Configure Storage Group

db2 "SET STOGROUP PATHS FOR IBMSTOGROUP ON '/mnt/bludata0'"

Continue the RESTORE

db2 "RESTORE DATABASE MAXDB76 CONTINUE"

= Checking restored database =

Connect to database

db2 connect to MAXDB

Verify tablespaces

db2 list tablespaces show detail

Verify containers

db2 list tablespace containers for 0 show detail
db2 list tablespace containers for 5 show detail
db2 list tablespace containers for 6 show detail

Verify storage group

db2 "select * from syscat.stogroups"
db2 "select * from syscat.storagepaths"

Verify data (tables)

db2 "select count(*) from syscat.tables"
db2 "select tabschema, tabname, card from syscat.tables where tabschema not like 'SYS%' fetch first 10 rows only"

= Ver também =

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

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

IBM Maximo: Migrate MAXDB to RH OpenShift

2026-04-08T00:11:36Z

Ebasso: /* Restore MAXDB76 backup file into Container */

= Create MAXDB database =

1) Install DB2 Operator

2) Create a New instance of DB2.

Open the DB2 Operator -> DB2 Cluster -> New cluster.

Get yaml file on this Article [[IBM Maximo: Migrate MAXDB to RH OpenShift (db2ucmas76-01.yaml)]]

Paste inside yaml form and click on create

= Copy backup file into Container =

Define db2 project on openshift

oc project db2u

Check pods

oc get pods

Copy backup file

oc cp MAXDB76.0.___.001.zip c-db2ucmas76-02-db2u-0:/mnt/backup/MAXDB76.0.___.001.zip

Login on container

oc rsh c-db2ucmas76-02-db2u-0

Extract file

cd /mnt/backup
unzip MAXDB76.0.___.001.zip
chmod a+rw MAX*

List

<nowiki>ls -l
total 7121740
-rw-rw-rw-. 1 db2uadm db2iadm1 7095119872 Sep 13 2022 MAXDB76.0.ctginst1.DBPART000.20220913055916.001
-rw-rw-rw-. 1 db2uadm db2iadm1 197538909 Apr 7 21:15 MAXDB76.0.ctginst1.DBPART000.20220913055916.001.zip
</nowiki>

Change user

su - db2inst1

Check backup

db2ckbkp -H /mnt/backup/MAXDB76.0.ctginst1.DBPART000.20220913055916.001

This command is generate the following file: [[IBM Maximo: Migrate MAXDB to RH OpenShift (db2ckbkp.out)]]

= Restore MAXDB76 backup file into Container =

This command will export data from backup file

su - db2inst1

cd /mnt/backup

db2 restore database MAXDB76 redirect generate script restoresql.sql

This command is generate the following file: [[IBM Maximo: Migrate MAXDB to RH OpenShift (restoresql.sql)]]

This can help to change parameters on restore.

Prepare db2

db2 force applications all
db2 terminate
db2 deactivate database MAXDB
db2 drop database MAXDB

Create directories

mkdir -p /mnt/bludata0/MAXDB
mkdir -p /mnt/tempts/c-db2ucmas76-05-db2u/MAXDB

Start RESTORE with REDIRECT

<nowiki>db2 "RESTORE DATABASE MAXDB76 FROM '/mnt/backup' TAKEN AT 20220913055916 INTO MAXDB REPLACE HISTORY FILE REPLACE EXISTING REDIRECT WITHOUT ROLLING FORWARD WITHOUT PROMPTING"</nowiki>

Configure Storage Group

db2 "SET STOGROUP PATHS FOR IBMSTOGROUP ON '/mnt/bludata0'"

Continue the RESTORE

db2 "RESTORE DATABASE MAXDB76 CONTINUE"

= Ver também =

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

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

IBM Maximo: Migrate MAXDB to RH OpenShift (restoresql.sql)

2026-04-08T00:10:53Z

Ebasso: Created page with " <nowiki> -- ***************************************************************************** -- ** automatically created redirect restore script -- ***************************************************************************** UPDATE COMMAND OPTIONS USING S ON Z ON MAXDB76_NODE0000.out V ON; SET CLIENT ATTACH_MEMBER 0; SET CLIENT CONNECT_MEMBER 0; -- ***************************************************************************** -- ** automatically created redirect restore..."

<nowiki>
-- *****************************************************************************
-- ** automatically created redirect restore script
-- *****************************************************************************
UPDATE COMMAND OPTIONS USING S ON Z ON MAXDB76_NODE0000.out V ON;
SET CLIENT ATTACH_MEMBER 0;
SET CLIENT CONNECT_MEMBER 0;
-- *****************************************************************************
-- ** automatically created redirect restore script
-- *****************************************************************************
RESTORE DATABASE MAXDB76
-- USER <username>
-- USING '<password>'
FROM '/mnt/backup'
TAKEN AT 20220913055916
-- ON '/home/ctginst1'
-- DBPATH ON '<target-directory>'
INTO MAXDB76
-- NEWLOGPATH DEFAULT
-- WITH <num-buff> BUFFERS
-- BUFFER <buffer-size>
-- REPLACE HISTORY FILE
-- REPLACE EXISTING
REDIRECT
-- PARALLELISM <n>
WITHOUT ROLLING FORWARD
-- WITHOUT PROMPTING
;
-- *****************************************************************************
-- ** storage group definition
-- ** Default storage group ID = 0
-- ** Number of storage groups = 1
-- *****************************************************************************
-- *****************************************************************************
-- ** Storage group name = IBMSTOGROUP
-- ** Storage group ID = 0
-- ** Data tag = None
-- *****************************************************************************
-- SET STOGROUP PATHS FOR IBMSTOGROUP
-- ON '/home/ctginst1'
-- ;
-- *****************************************************************************
-- ** table space definition
-- *****************************************************************************
-- *****************************************************************************
-- ** Tablespace name = SYSCATSPACE
-- ** Tablespace ID = 0
-- ** Tablespace Type = Database managed space
-- ** Tablespace Content Type = All permanent data. Regular table space.
-- ** Tablespace Page size (bytes) = 32768
-- ** Tablespace Extent size (pages) = 4
-- ** Using automatic storage = Yes
-- ** Storage group ID = 0
-- ** Source storage group ID = -1
-- ** Data tag = None
-- ** Auto-resize enabled = Yes
-- ** Total number of pages = 15360
-- ** Number of usable pages = 15356
-- ** High water mark (pages) = 15352
-- *****************************************************************************
-- *****************************************************************************
-- ** Tablespace name = TEMPSPACE1
-- ** Tablespace ID = 1
-- ** Tablespace Type = System managed space
-- ** Tablespace Content Type = System Temporary data
-- ** Tablespace Page size (bytes) = 32768
-- ** Tablespace Extent size (pages) = 32
-- ** Using automatic storage = Yes
-- ** Total number of pages = 1
-- *****************************************************************************
-- *****************************************************************************
-- ** Tablespace name = USERSPACE1
-- ** Tablespace ID = 2
-- ** Tablespace Type = Database managed space
-- ** Tablespace Content Type = All permanent data. Large table space.
-- ** Tablespace Page size (bytes) = 32768
-- ** Tablespace Extent size (pages) = 32
-- ** Using automatic storage = Yes
-- ** Storage group ID = 0
-- ** Source storage group ID = -1
-- ** Data tag = -1
-- ** Auto-resize enabled = Yes
-- ** Total number of pages = 1024
-- ** Number of usable pages = 992
-- ** High water mark (pages) = 96
-- *****************************************************************************
-- *****************************************************************************
-- ** Tablespace name = SYSTOOLSPACE
-- ** Tablespace ID = 3
-- ** Tablespace Type = Database managed space
-- ** Tablespace Content Type = All permanent data. Large table space.
-- ** Tablespace Page size (bytes) = 32768
-- ** Tablespace Extent size (pages) = 4
-- ** Using automatic storage = Yes
-- ** Storage group ID = 0
-- ** Source storage group ID = -1
-- ** Data tag = -1
-- ** Auto-resize enabled = Yes
-- ** Total number of pages = 1024
-- ** Number of usable pages = 1020
-- ** High water mark (pages) = 100
-- *****************************************************************************
-- *****************************************************************************
-- ** Tablespace name = SYSTOOLSTMPSPACE
-- ** Tablespace ID = 4
-- ** Tablespace Type = System managed space
-- ** Tablespace Content Type = User Temporary data
-- ** Tablespace Page size (bytes) = 32768
-- ** Tablespace Extent size (pages) = 4
-- ** Using automatic storage = Yes
-- ** Total number of pages = 1
-- *****************************************************************************
-- *****************************************************************************
-- ** Tablespace name = MAXDATA
-- ** Tablespace ID = 5
-- ** Tablespace Type = Database managed space
-- ** Tablespace Content Type = All permanent data. Regular table space.
-- ** Tablespace Page size (bytes) = 32768
-- ** Tablespace Extent size (pages) = 32
-- ** Using automatic storage = Yes
-- ** Storage group ID = 0
-- ** Source storage group ID = -1
-- ** Data tag = -1
-- ** Auto-resize enabled = Yes
-- ** Total number of pages = 160000
-- ** Number of usable pages = 159968
-- ** High water mark (pages) = 122048
-- *****************************************************************************
-- *****************************************************************************
-- ** Tablespace name = MAXINDEX
-- ** Tablespace ID = 6
-- ** Tablespace Type = Database managed space
-- ** Tablespace Content Type = All permanent data. Regular table space.
-- ** Tablespace Page size (bytes) = 32768
-- ** Tablespace Extent size (pages) = 32
-- ** Using automatic storage = Yes
-- ** Storage group ID = 0
-- ** Source storage group ID = -1
-- ** Data tag = -1
-- ** Auto-resize enabled = Yes
-- ** Total number of pages = 160000
-- ** Number of usable pages = 159968
-- ** High water mark (pages) = 93408
-- *****************************************************************************
-- *****************************************************************************
-- ** Tablespace name = MAXTEMP
-- ** Tablespace ID = 7
-- ** Tablespace Type = System managed space
-- ** Tablespace Content Type = System Temporary data
-- ** Tablespace Page size (bytes) = 32768
-- ** Tablespace Extent size (pages) = 32
-- ** Using automatic storage = Yes
-- ** Total number of pages = 1
-- *****************************************************************************
-- *****************************************************************************
-- ** start redirected restore
-- *****************************************************************************
RESTORE DATABASE MAXDB76 CONTINUE;
-- *****************************************************************************
-- ** end of file
-- *****************************************************************************

</nowiki>

= Ver também =

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

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

IBM Maximo: Migrate MAXDB to RH OpenShift

2026-04-08T00:09:53Z

Ebasso: /* Restore MAXDB76 backup file into Container */

= Create MAXDB database =

1) Install DB2 Operator

2) Create a New instance of DB2.

Open the DB2 Operator -> DB2 Cluster -> New cluster.

Get yaml file on this Article [[IBM Maximo: Migrate MAXDB to RH OpenShift (db2ucmas76-01.yaml)]]

Paste inside yaml form and click on create

= Copy backup file into Container =

Define db2 project on openshift

oc project db2u

Check pods

oc get pods

Copy backup file

oc cp MAXDB76.0.___.001.zip c-db2ucmas76-02-db2u-0:/mnt/backup/MAXDB76.0.___.001.zip

Login on container

oc rsh c-db2ucmas76-02-db2u-0

Extract file

cd /mnt/backup
unzip MAXDB76.0.___.001.zip
chmod a+rw MAX*

List

<nowiki>ls -l
total 7121740
-rw-rw-rw-. 1 db2uadm db2iadm1 7095119872 Sep 13 2022 MAXDB76.0.ctginst1.DBPART000.20220913055916.001
-rw-rw-rw-. 1 db2uadm db2iadm1 197538909 Apr 7 21:15 MAXDB76.0.ctginst1.DBPART000.20220913055916.001.zip
</nowiki>

Change user

su - db2inst1

Check backup

db2ckbkp -H /mnt/backup/MAXDB76.0.ctginst1.DBPART000.20220913055916.001

This command is generate the following file: [[IBM Maximo: Migrate MAXDB to RH OpenShift (db2ckbkp.out)]]

= Restore MAXDB76 backup file into Container =

This command will export data from backup file

su - db2inst1

cd /mnt/backup

db2 restore database MAXDB76 redirect generate script restoresql.sql

This command is generate the following file: [[IBM Maximo: Migrate MAXDB to RH OpenShift (restoresql.sql)]]

Prepare db2

db2 force applications all
db2 terminate
db2 deactivate database MAXDB
db2 drop database MAXDB

Create directories

mkdir -p /mnt/bludata0/MAXDB
mkdir -p /mnt/tempts/c-db2ucmas76-05-db2u/MAXDB

Start RESTORE with REDIRECT

<nowiki>db2 "RESTORE DATABASE MAXDB76 FROM '/mnt/backup' TAKEN AT 20220913055916 INTO MAXDB REPLACE HISTORY FILE REPLACE EXISTING REDIRECT WITHOUT ROLLING FORWARD WITHOUT PROMPTING"</nowiki>

Configure Storage Group

db2 "SET STOGROUP PATHS FOR IBMSTOGROUP ON '/mnt/bludata0'"

Continue the RESTORE

db2 "RESTORE DATABASE MAXDB76 CONTINUE"

= Ver também =

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

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

IBM Maximo: Migrate MAXDB to RH OpenShift

2026-04-08T00:09:09Z

Ebasso: /* Restore MAXDB76 backup file into Container */

= Create MAXDB database =

1) Install DB2 Operator

2) Create a New instance of DB2.

Open the DB2 Operator -> DB2 Cluster -> New cluster.

Get yaml file on this Article [[IBM Maximo: Migrate MAXDB to RH OpenShift (db2ucmas76-01.yaml)]]

Paste inside yaml form and click on create

= Copy backup file into Container =

Define db2 project on openshift

oc project db2u

Check pods

oc get pods

Copy backup file

oc cp MAXDB76.0.___.001.zip c-db2ucmas76-02-db2u-0:/mnt/backup/MAXDB76.0.___.001.zip

Login on container

oc rsh c-db2ucmas76-02-db2u-0

Extract file

cd /mnt/backup
unzip MAXDB76.0.___.001.zip
chmod a+rw MAX*

List

<nowiki>ls -l
total 7121740
-rw-rw-rw-. 1 db2uadm db2iadm1 7095119872 Sep 13 2022 MAXDB76.0.ctginst1.DBPART000.20220913055916.001
-rw-rw-rw-. 1 db2uadm db2iadm1 197538909 Apr 7 21:15 MAXDB76.0.ctginst1.DBPART000.20220913055916.001.zip
</nowiki>

Change user

su - db2inst1

Check backup

db2ckbkp -H /mnt/backup/MAXDB76.0.ctginst1.DBPART000.20220913055916.001

This command is generate the following file: [[IBM Maximo: Migrate MAXDB to RH OpenShift (db2ckbkp.out)]]

= Restore MAXDB76 backup file into Container =

This command will export data from backup file

su - db2inst1

cd /mnt/backup

db2 restore database MAXDB76 redirect generate script restoresql.sql

Prepare db2

db2 force applications all
db2 terminate
db2 deactivate database MAXDB
db2 drop database MAXDB

Create directories

mkdir -p /mnt/bludata0/MAXDB
mkdir -p /mnt/tempts/c-db2ucmas76-05-db2u/MAXDB

Start RESTORE with REDIRECT

<nowiki>db2 "RESTORE DATABASE MAXDB76 FROM '/mnt/backup' TAKEN AT 20220913055916 INTO MAXDB REPLACE HISTORY FILE REPLACE EXISTING REDIRECT WITHOUT ROLLING FORWARD WITHOUT PROMPTING"</nowiki>

Configure Storage Group

db2 "SET STOGROUP PATHS FOR IBMSTOGROUP ON '/mnt/bludata0'"

Continue the RESTORE

db2 "RESTORE DATABASE MAXDB76 CONTINUE"

= Ver também =

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

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

IBM Maximo: Migrate MAXDB to RH OpenShift

2026-04-08T00:05:23Z

Ebasso: /* Copy MAXDB76 backup file into Container */

IBM Maximo: Migrate MAXDB to RH OpenShift

2026-04-08T00:05:11Z

Ebasso:

IBM Maximo: Migrate MAXDB to RH OpenShift (db2ckbkp.out)

2026-04-08T00:02:48Z

Ebasso: Created page with " <nowiki> ===================== MEDIA HEADER REACHED: ===================== Server Database Name -- MAXDB76 Server Database Alias -- MAXDB76 Client Database Alias -- MAXDB76 Timestamp -- 20220913055916 Database Partition Number -- 0 Instance -- ctginst1 Database Configuration Type -- 0 (Non-shared data) Sequence Number -- 1 Database Member ID -- 0 Release..."

<nowiki>
=====================
MEDIA HEADER REACHED:
=====================
Server Database Name -- MAXDB76
Server Database Alias -- MAXDB76
Client Database Alias -- MAXDB76
Timestamp -- 20220913055916
Database Partition Number -- 0
Instance -- ctginst1
Database Configuration Type -- 0 (Non-shared data)
Sequence Number -- 1
Database Member ID -- 0
Release ID -- 0x1400 (DB2 v11.1.4.6)
AL version -- V:11 R:1 M:4 F:6 I:0 SB:0
Database Seed -- 0x7592E410
DB Comment's Codepage (Volume) -- 0
DB Comment (Volume) --
DB Comment's Codepage (System) -- 0
DB Comment (System) --
Authentication Value -- 255 (Not specified)
Backup Mode -- 0 (Offline)
Includes Logs -- 0 (No)
Compression -- 0 (No Library Applied)
Backup Type -- 0 (Database-level)
Backup Granularity -- 0 (Non-incremental)
Merged Backup Image -- 0 (No)
Status Flags -- 0x1
Consistent across all members
System Catalogs in this image -- 1 (Yes)
Catalog Partition Number -- 0
DB Codeset -- UTF-8
DB Territory -- US
LogID -- 1634337662
LogPath -- /home/ctginst1/ctginst1/NODE0000/SQL00001/LOGSTREAM0000/
Backup Buffer Size -- 6295552 (1537 4K pages)
Number of Sessions -- 1
Platform -- 0x1E (Linux-x86-64)
Encrypt Info Flags -- 0x0

The proper image file name would be:
MAXDB76.0.ctginst1.DBPART000.20220913055916.001
</nowiki>

= Ver também =

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

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

IBM Maximo: Migrate MAXDB to RH OpenShift

2026-04-08T00:02:10Z

Ebasso:

IBM Maximo: Migrate MAXDB to RH OpenShift

2026-04-07T23:59:26Z

Ebasso: /* Restore MAXDB76 backup file into Container */

IBM Maximo: Migrate MAXDB to RH OpenShift

2026-04-07T21:17:49Z

Ebasso: /* Restore MAXDB76 backup file into Container */

IBM Maximo: Migrate MAXDB to RH OpenShift

2026-04-07T20:15:25Z

Ebasso: /* Create MAXDB database */

IBM Maximo: Migrate MAXDB to RH OpenShift (db2ucmas76-01.yaml)

2026-04-07T20:14:28Z

Ebasso: Created page with " Paste the yaml below, change storageClassName: "lvms-vg1", to your storage class. <nowiki> apiVersion: db2u.databases.ibm.com/v1 kind: Db2uCluster metadata: name: db2ucmas76-01 namespace: db2u spec: license: accept: true account: privileged: true environment: database: settings: codeset: UTF-8 territory: US name: MAXDB ldap: enabled: false dbType: db2wh version: s11.5.9.0-cn2 podConfig: db2u:..."

Paste the yaml below, change storageClassName: "lvms-vg1", to your storage class.

<nowiki>
apiVersion: db2u.databases.ibm.com/v1
kind: Db2uCluster
metadata:
name: db2ucmas76-01
namespace: db2u
spec:
license:
accept: true
account:
privileged: true
environment:
database:
settings:
codeset: UTF-8
territory: US
name: MAXDB
ldap:
enabled: false
dbType: db2wh
version: s11.5.9.0-cn2
podConfig:
db2u:
resource:
db2u:
limits:
cpu: '6'
memory: 16Gi
requests:
cpu: 500m
memory: 3Gi
storage:
- name: meta
type: create
spec:
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 10Gi
storageClassName: lvms-vg1
- name: data
type: template
spec:
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 20Gi
storageClassName: lvms-vg1
- name: backup
type: create
spec:
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 10Gi
storageClassName: lvms-vg1
- name: tempts
type: template
spec:
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 10Gi
storageClassName: lvms-vg1
- name: archivelogs
type: create
spec:
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 10Gi
storageClassName: lvms-vg1
size: 1
</nowiki>

= Ver também =

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

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

IBM Maximo: Migrate MAXDB to RH OpenShift

2026-04-07T20:14:05Z

Ebasso: /* Create MAXDB database */

IBM Maximo: Migrate MAXDB to RH OpenShift

2026-04-07T20:13:55Z

Ebasso: /* Create MAXDB database */

= Create MAXDB database =

1) Install DB2 Operator

2) Create a New instance of DB2.

Open the DB2 Operator -> DB2 Cluster -> New cluster.

Get yaml file on this Article [IBM Maximo: Migrate MAXDB to RH OpenShift (db2ucmas76-01.yaml)]

= Restore MAXDB76 backup file into Container =

Define db2 project on openshift

oc project db2u

Check pods

oc get pods

Copy backup file

oc cp MAXDB76.0.___.001.zip c-db2ucmas76-02-db2u-0:/mnt/backup/MAXDB76.0.___.001.zip

Login on container

oc rsh c-db2ucmas76-02-db2u-0

Extract file

cd /mnt/backup
unzip MAXDB76.0.___.001.zip

= Ver também =

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

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

IBM Maximo: Migrate MAXDB to RH OpenShift

2026-04-07T20:12:18Z

Ebasso: /* Restore MAXDB76.backup.. to Container */

= Create MAXDB database =

1) Install DB2 Operator

2) Create a New instance of DB2.

Open the DB2 Operator -> DB2 Cluster -> New cluster.

Paste the yaml below, change storageClassName: "lvms-vg1", to your storage class.

<nowiki>
apiVersion: db2u.databases.ibm.com/v1
kind: Db2uCluster
metadata:
name: db2ucmas76-01
namespace: db2u
spec:
license:
accept: true
account:
privileged: true
environment:
database:
settings:
codeset: UTF-8
territory: US
name: MAXDB
ldap:
enabled: false
dbType: db2wh
version: s11.5.9.0-cn2
podConfig:
db2u:
resource:
db2u:
limits:
cpu: '6'
memory: 16Gi
requests:
cpu: 500m
memory: 3Gi
storage:
- name: meta
type: create
spec:
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 10Gi
storageClassName: lvms-vg1
- name: data
type: template
spec:
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 20Gi
storageClassName: lvms-vg1
- name: backup
type: create
spec:
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 10Gi
storageClassName: lvms-vg1
- name: tempts
type: template
spec:
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 10Gi
storageClassName: lvms-vg1
- name: archivelogs
type: create
spec:
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 10Gi
storageClassName: lvms-vg1
size: 1
</nowiki>

= Restore MAXDB76 backup file into Container =

Define db2 project on openshift

oc project db2u

Check pods

oc get pods

Copy backup file

oc cp MAXDB76.0.___.001.zip c-db2ucmas76-02-db2u-0:/mnt/backup/MAXDB76.0.___.001.zip

Login on container

oc rsh c-db2ucmas76-02-db2u-0

Extract file

cd /mnt/backup
unzip MAXDB76.0.___.001.zip

= Ver também =

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

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

IBM Maximo: Migrate MAXDB to RH OpenShift

2026-04-07T20:10:30Z

Ebasso: /* Restore MAXDB76.backup.. to Container */

= Create MAXDB database =

1) Install DB2 Operator

2) Create a New instance of DB2.

Open the DB2 Operator -> DB2 Cluster -> New cluster.

Paste the yaml below, change storageClassName: "lvms-vg1", to your storage class.

<nowiki>
apiVersion: db2u.databases.ibm.com/v1
kind: Db2uCluster
metadata:
name: db2ucmas76-01
namespace: db2u
spec:
license:
accept: true
account:
privileged: true
environment:
database:
settings:
codeset: UTF-8
territory: US
name: MAXDB
ldap:
enabled: false
dbType: db2wh
version: s11.5.9.0-cn2
podConfig:
db2u:
resource:
db2u:
limits:
cpu: '6'
memory: 16Gi
requests:
cpu: 500m
memory: 3Gi
storage:
- name: meta
type: create
spec:
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 10Gi
storageClassName: lvms-vg1
- name: data
type: template
spec:
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 20Gi
storageClassName: lvms-vg1
- name: backup
type: create
spec:
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 10Gi
storageClassName: lvms-vg1
- name: tempts
type: template
spec:
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 10Gi
storageClassName: lvms-vg1
- name: archivelogs
type: create
spec:
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 10Gi
storageClassName: lvms-vg1
size: 1
</nowiki>

= Restore MAXDB76.backup.. to Container =

Define db2 project on openshift

oc project db2u

Check pods

oc get pods

Copy backup file

oc cp MAXDB76.0.___.001.zip c-db2ucmas76-02-db2u-0:/mnt/backup/MAXDB76.0.___.001.zip

Login on container

oc rsh c-db2ucmas76-02-db2u-0

Extract file

cd /mnt/backup
unzip MAXDB76.0.___.001.zip

= Ver também =

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

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

IBM Maximo: Migrate MAXDB to RH OpenShift

2026-04-07T20:09:43Z

Ebasso: /* Restore MAXDB76.backup.. to Container */

= Create MAXDB database =

1) Install DB2 Operator

2) Create a New instance of DB2.

Open the DB2 Operator -> DB2 Cluster -> New cluster.

Paste the yaml below, change storageClassName: "lvms-vg1", to your storage class.

<nowiki>
apiVersion: db2u.databases.ibm.com/v1
kind: Db2uCluster
metadata:
name: db2ucmas76-01
namespace: db2u
spec:
license:
accept: true
account:
privileged: true
environment:
database:
settings:
codeset: UTF-8
territory: US
name: MAXDB
ldap:
enabled: false
dbType: db2wh
version: s11.5.9.0-cn2
podConfig:
db2u:
resource:
db2u:
limits:
cpu: '6'
memory: 16Gi
requests:
cpu: 500m
memory: 3Gi
storage:
- name: meta
type: create
spec:
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 10Gi
storageClassName: lvms-vg1
- name: data
type: template
spec:
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 20Gi
storageClassName: lvms-vg1
- name: backup
type: create
spec:
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 10Gi
storageClassName: lvms-vg1
- name: tempts
type: template
spec:
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 10Gi
storageClassName: lvms-vg1
- name: archivelogs
type: create
spec:
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 10Gi
storageClassName: lvms-vg1
size: 1
</nowiki>

= Restore MAXDB76.backup.. to Container =

Define db2 project on openshift

oc project db2u

Check pods

oc get pods

Copy backup file

oc cp MAXDB76.0.___.001.zip c-db2ucmas76-02-db2u 0:/mnt/backup/MAXDB76.0.___.001.zip

= Ver também =

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

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

IBM Maximo: Migrate MAXDB to RH OpenShift

2026-04-07T20:09:14Z

Ebasso: /* Restore MAXDB76.backup.. to Container */

= Create MAXDB database =

1) Install DB2 Operator

2) Create a New instance of DB2.

Open the DB2 Operator -> DB2 Cluster -> New cluster.

Paste the yaml below, change storageClassName: "lvms-vg1", to your storage class.

<nowiki>
apiVersion: db2u.databases.ibm.com/v1
kind: Db2uCluster
metadata:
name: db2ucmas76-01
namespace: db2u
spec:
license:
accept: true
account:
privileged: true
environment:
database:
settings:
codeset: UTF-8
territory: US
name: MAXDB
ldap:
enabled: false
dbType: db2wh
version: s11.5.9.0-cn2
podConfig:
db2u:
resource:
db2u:
limits:
cpu: '6'
memory: 16Gi
requests:
cpu: 500m
memory: 3Gi
storage:
- name: meta
type: create
spec:
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 10Gi
storageClassName: lvms-vg1
- name: data
type: template
spec:
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 20Gi
storageClassName: lvms-vg1
- name: backup
type: create
spec:
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 10Gi
storageClassName: lvms-vg1
- name: tempts
type: template
spec:
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 10Gi
storageClassName: lvms-vg1
- name: archivelogs
type: create
spec:
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 10Gi
storageClassName: lvms-vg1
size: 1
</nowiki>

= Restore MAXDB76.backup.. to Container =

Define db2 project on openshift

oc project db2u

Check pods

oc get pods

Copy backup file

oc cp MAXDB76.0.ctginst1.DBPART000.2022___.001.zip c-db2ucmas76-02-db2u 0:/mnt/backup/MAXDB76.0.ctginst1.DBPART000.2022___.001.zip

= Ver também =

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

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

IBM Maximo: Migrate MAXDB to RH OpenShift

2026-04-07T20:08:14Z

Ebasso: /* Restore MAXDB76.backup.. to Container */

= Create MAXDB database =

1) Install DB2 Operator

2) Create a New instance of DB2.

Open the DB2 Operator -> DB2 Cluster -> New cluster.

Paste the yaml below, change storageClassName: "lvms-vg1", to your storage class.

<nowiki>
apiVersion: db2u.databases.ibm.com/v1
kind: Db2uCluster
metadata:
name: db2ucmas76-01
namespace: db2u
spec:
license:
accept: true
account:
privileged: true
environment:
database:
settings:
codeset: UTF-8
territory: US
name: MAXDB
ldap:
enabled: false
dbType: db2wh
version: s11.5.9.0-cn2
podConfig:
db2u:
resource:
db2u:
limits:
cpu: '6'
memory: 16Gi
requests:
cpu: 500m
memory: 3Gi
storage:
- name: meta
type: create
spec:
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 10Gi
storageClassName: lvms-vg1
- name: data
type: template
spec:
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 20Gi
storageClassName: lvms-vg1
- name: backup
type: create
spec:
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 10Gi
storageClassName: lvms-vg1
- name: tempts
type: template
spec:
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 10Gi
storageClassName: lvms-vg1
- name: archivelogs
type: create
spec:
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 10Gi
storageClassName: lvms-vg1
size: 1
</nowiki>

= Restore MAXDB76.backup.. to Container =

Define db2 project on openshift

oc project db2u

Check pods

oc get pods

Copy backup file

<small>oc cp MAXDB76.0.ctginst1.DBPART000.20220913055916.001.zip \
c-db2ucmas76-02-db2u 0:/mnt/backup/MAXDB76.0.ctginst1.DBPART000.20220913055916.001.zip</small>

= Ver também =

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

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

IBM Maximo: Migrate MAXDB to RH OpenShift

2026-04-07T20:05:03Z

Ebasso: /* Restore MAXDB76.backup.. to Container */

= Create MAXDB database =

1) Install DB2 Operator

2) Create a New instance of DB2.

Open the DB2 Operator -> DB2 Cluster -> New cluster.

Paste the yaml below, change storageClassName: "lvms-vg1", to your storage class.

<nowiki>
apiVersion: db2u.databases.ibm.com/v1
kind: Db2uCluster
metadata:
name: db2ucmas76-01
namespace: db2u
spec:
license:
accept: true
account:
privileged: true
environment:
database:
settings:
codeset: UTF-8
territory: US
name: MAXDB
ldap:
enabled: false
dbType: db2wh
version: s11.5.9.0-cn2
podConfig:
db2u:
resource:
db2u:
limits:
cpu: '6'
memory: 16Gi
requests:
cpu: 500m
memory: 3Gi
storage:
- name: meta
type: create
spec:
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 10Gi
storageClassName: lvms-vg1
- name: data
type: template
spec:
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 20Gi
storageClassName: lvms-vg1
- name: backup
type: create
spec:
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 10Gi
storageClassName: lvms-vg1
- name: tempts
type: template
spec:
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 10Gi
storageClassName: lvms-vg1
- name: archivelogs
type: create
spec:
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 10Gi
storageClassName: lvms-vg1
size: 1
</nowiki>

= Restore MAXDB76.backup.. to Container =

Define db2 project on openshift

oc project db2u

Check pods

oc get pods

Copy backup file

oc cp MAXDB76.0.ctginst1.DBPART000.20220913055916.001.zip \
c-db2ucmas76-02-db2u 0:/mnt/backup/MAXDB76.0.ctginst1.DBPART000.20220913055916.001.zip

= Ver também =

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

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

IBM Maximo: Migrate MAXDB to RH OpenShift

2026-04-07T20:04:51Z

Ebasso: /* Create MAXDB database */

= Create MAXDB database =

1) Install DB2 Operator

2) Create a New instance of DB2.

Open the DB2 Operator -> DB2 Cluster -> New cluster.

Paste the yaml below, change storageClassName: "lvms-vg1", to your storage class.

<nowiki>
apiVersion: db2u.databases.ibm.com/v1
kind: Db2uCluster
metadata:
name: db2ucmas76-01
namespace: db2u
spec:
license:
accept: true
account:
privileged: true
environment:
database:
settings:
codeset: UTF-8
territory: US
name: MAXDB
ldap:
enabled: false
dbType: db2wh
version: s11.5.9.0-cn2
podConfig:
db2u:
resource:
db2u:
limits:
cpu: '6'
memory: 16Gi
requests:
cpu: 500m
memory: 3Gi
storage:
- name: meta
type: create
spec:
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 10Gi
storageClassName: lvms-vg1
- name: data
type: template
spec:
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 20Gi
storageClassName: lvms-vg1
- name: backup
type: create
spec:
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 10Gi
storageClassName: lvms-vg1
- name: tempts
type: template
spec:
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 10Gi
storageClassName: lvms-vg1
- name: archivelogs
type: create
spec:
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 10Gi
storageClassName: lvms-vg1
size: 1
</nowiki>

= Restore MAXDB76.backup.. to Container =

Define db2 project on openshift

oc project db2u

Check pods

oc get pods

Copy backup file

oc cp MAXDB76.0.ctginst1.DBPART000.20220913055916.001.zip c-db2ucmas76-02-db2u 0:/mnt/backup/MAXDB76.0.ctginst1.DBPART000.20220913055916.001.zip

= Ver também =

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

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

IBM Maximo: Migrate MAXDB to RH OpenShift

2026-04-07T20:01:00Z

Ebasso:

= Create MAXDB database =

1) Install DB2 Operator

2) Create a New instance of DB2.

Open the DB2 Operator -> DB2 Cluster -> New cluster.

Paste the yaml below, change storageClassName: "lvms-vg1", to your storage class.

<nowiki>
apiVersion: db2u.databases.ibm.com/v1
kind: Db2uCluster
metadata:
name: db2ucmas76-01
namespace: db2u
spec:
license:
accept: true
account:
privileged: true
environment:
database:
settings:
codeset: UTF-8
territory: US
name: MAXDB
ldap:
enabled: false
dbType: db2wh
version: s11.5.9.0-cn2
podConfig:
db2u:
resource:
db2u:
limits:
cpu: '6'
memory: 16Gi
requests:
cpu: 500m
memory: 3Gi
storage:
- name: meta
type: create
spec:
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 10Gi
storageClassName: lvms-vg1
- name: data
type: template
spec:
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 20Gi
storageClassName: lvms-vg1
- name: backup
type: create
spec:
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 10Gi
storageClassName: lvms-vg1
- name: tempts
type: template
spec:
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 10Gi
storageClassName: lvms-vg1
- name: archivelogs
type: create
spec:
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 10Gi
storageClassName: lvms-vg1
size: 1
</nowiki>

= Ver também =

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

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

IBM Maximo: Migrate MAXDB to RH OpenShift

2026-04-07T20:00:15Z

Ebasso:

1) Install DB2 Operator

2) Create a New instance of DB2.

Open the DB2 Operator -> DB2 Cluster -> New cluster.

Paste the yaml below, change storageClassName: "lvms-vg1", to your storage class.

<nowiki>
apiVersion: db2u.databases.ibm.com/v1
kind: Db2uCluster
metadata:
name: db2ucmas76-01
namespace: db2u
spec:
license:
accept: true
account:
privileged: true
environment:
database:
settings:
codeset: UTF-8
territory: US
name: MAXDB
ldap:
enabled: false
dbType: db2wh
version: s11.5.9.0-cn2
podConfig:
db2u:
resource:
db2u:
limits:
cpu: '6'
memory: 16Gi
requests:
cpu: 500m
memory: 3Gi
storage:
- name: meta
type: create
spec:
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 10Gi
storageClassName: lvms-vg1
- name: data
type: template
spec:
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 20Gi
storageClassName: lvms-vg1
- name: backup
type: create
spec:
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 10Gi
storageClassName: lvms-vg1
- name: tempts
type: template
spec:
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 10Gi
storageClassName: lvms-vg1
- name: archivelogs
type: create
spec:
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 10Gi
storageClassName: lvms-vg1
size: 1
</nowiki>

= Ver também =

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

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

IBM Maximo: Migrate MAXDB to RH OpenShift

2026-04-07T19:58:36Z

Ebasso: Created page with " 1) Install DB2 Operator 2) Create a New instance of DB2. <nowiki> apiVersion: db2u.databases.ibm.com/v1 kind: Db2uCluster metadata: name: db2ucmas76-01 namespace: db2u spec: license: accept: true account: privileged: true environment: database: settings: codeset: UTF-8 territory: US name: MAXDB ldap: enabled: false dbType: db2wh version: s11.5.9.0-cn2 podConfig: db2u: resource: db2..."

1) Install DB2 Operator

2) Create a New instance of DB2.

<nowiki>
apiVersion: db2u.databases.ibm.com/v1
kind: Db2uCluster
metadata:
name: db2ucmas76-01
namespace: db2u
spec:
license:
accept: true
account:
privileged: true
environment:
database:
settings:
codeset: UTF-8
territory: US
name: MAXDB
ldap:
enabled: false
dbType: db2wh
version: s11.5.9.0-cn2
podConfig:
db2u:
resource:
db2u:
limits:
cpu: '6'
memory: 16Gi
requests:
cpu: 500m
memory: 3Gi
storage:
- name: meta
type: create
spec:
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 10Gi
storageClassName: lvms-vg1
- name: data
type: template
spec:
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 20Gi
storageClassName: lvms-vg1
- name: backup
type: create
spec:
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 10Gi
storageClassName: lvms-vg1
- name: tempts
type: template
spec:
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 10Gi
storageClassName: lvms-vg1
- name: archivelogs
type: create
spec:
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 10Gi
storageClassName: lvms-vg1
size: 1
</nowiki>

= Ver também =

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

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

IBM Maximo

2026-04-07T19:56:54Z

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

Este blog fornece artigos para pessoas que dão suporte ao IBM Maximo Asset Management e ao IBM Control Desk.

O software 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.

'''Principais Benefícios''':

# Reduzir o tempo de inatividade, não planejado, de um ativo (PM -> Manutenção Preventiva)
# Minimizar falhas de um ativo (Código de Falha)
# Maximizar uso de um recurso (Planejamento e Execução)
# Aumentar a confiabilidade de um ativo (PM, KPIs)
# Reduzir os custos do estoque (Gerenciamento de estoque)
# Melhorar os serviços (SS -> Solicitação de Serviço, WO -> Ordem de serviço)
# Gestão de segurança e Risco (Plano de segurança)
# Prolongar a vida útil de ativos (Gestão de ativos)
# Identificar tendências (KPIs e relatórios)

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”.
|-
| Maximo Asset Manage (MAM) ||
O MAM 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 =

* [[Maximo: Matriz de pré-requisitos do Maximo Application Suite]]

{| class="wikitable"
|-
! . !!Gerenciamento de Ativos !! . !!Contratos !! . !! . !! . !! Administração !! . !! .
|-
| . ||Ativos || . ||Contratos de Compra || . || . || . || Conjuntos || . || .
|-
| . ||Modelo de Ativos || . ||Contratos de Leasing/Aluguel || . || . || . || Organizações || . || .
|-
| . ||Medidores || . ||Contrato de Taxa de Mão de Obra|| . || . || . || Calendários || .|| .
|-
| . ||Relacionamentos || . ||Contratos Mestre || . || . || . || Recursos* || . || .
|-
| . ||Grupo de Medidores || . ||Contratos de Garantia || . || . || . || Quadro de Avisos || . || .
|-
| . ||Monitoração de Condições|| . ||Termos e Condições || . || . || . || Modelos de Comunicação || . || .
|-
| . ||Códigos de Falha || . ||Contratos || . || . || . || Administração de Relatórios || . || .
|-
| . ||Monitoração de Condições|| . || . || . || . || . || . || . || .
|}

=== Modulos Administrativos ===
* [[IBM Maximo Manage: Configuração Inicial]]
** Aplicações: Conjuntos, Organizações, Sites, Charts (GL Account) e Currencies (Moeda)

* [[IBM Maximo Manage: Configuração e Desenvolvimento]]
** Aplicações de Configuração: Users, Security Groups, Roles, Person, Person Groups
** Aplicações de Desenvolvimento: Escalations, Workflow Design,
** Aplicações Administrativas: Person, Person Groups, Roles

=== Modulos de Ativos (Assets) ===
* [[IBM Maximo Manage: Gerenciamento de Ativos]]

=== Outros Softwares ===

* [[IBM Maximo Customization Detection Tool]]
* [[IBM Maximo Mobile]]

=== 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]

= Migration to Maximo Application Suite (MAS) =

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

* [[IBM Maximo: Migrate MAXDB to RH OpenShift]]

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

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

* [[IBM Maximo: Provide you customization_binaries.zip on 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]]

= Ambiente / Produtos / Alta Disponibilidade =

* [https://www.ibm.com/support/pages/maximo-product-configuration-matrix-0 Maximo Product Configuration Matrix]
* [http://www.redbooks.ibm.com/redbooks/pdfs/sg248109.pdf Redbook:High Availability and Disaster Recovery Configurations for IBM SmartCloud Control Desk and IBM Maximo Products]

= Instalação e Configuração =

* [[IBM Maximo: Instalação do Maximo Application Suite usando o MAS CLI]]
* [[IBM Maximo: Opções do MAS CLI]]

* [[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 Sterling Connect:Direct: Configuring C:D to use AWS S3 Storage provide an AWS credentials file as a volume

2026-03-12T18:50:43Z

Ebasso: /* Mounting the .aws Directory in Kubernetes */

This article describes how to configure IBM Connect:Direct (CDU) to access S3-compatible object storage.

The setup involves preparing AWS-style configuration files, updating `Initparm.cfg`, and mounting the necessary credential files into the Connect:Direct pod using Kubernetes `extraVolume` and `extraVolumeMount` parameters.

== AWS Configuration Files ==

The file credentials must be created under the user's `.aws` directory:

=== Example: credentials File ===
<syntaxhighlight lang="ini">[default]
aws_access_key_id = <profile id>
aws_secret_access_key = <access key>

[aws-profile02]
aws_access_key_id = <profile id>
aws_secret_access_key = <access key>
</syntaxhighlight>

These files can be automatically generated using the AWS CLI:

<syntaxhighlight lang="bash">aws configure --profile aws-profile02</syntaxhighlight>

== Updating Initparm.cfg ==
The following S3 I/O Exit configuration must be added to `Initparm.cfg`:

<syntaxhighlight lang="ini"># S3 IO Exit parameters
file.ioexit:\
:name=s3:\
:library=/opt/cdunix/ndm/lib/libcdjnibridge.so:\
:home.dir=/opt/cdunix/ndm/ioexit-plugins/s3:\
:options=-Xmx640m \
-Djava.class.path=/opt/cdunix/ndm/ioexit-plugins/s3/cd-s3-ioexit.jar \
-Ds3.profilePath='/home/cduser/.aws/credentials' \
-Ds3.profileName=default \
com.aricent.ibm.mft.connectdirect.s3ioexit.S3IOExitFactory:

file.ioexit:\
:name=s3qa:\
:library=/opt/cdunix/ndm/lib/libcdjnibridge.so:\
:home.dir=/opt/cdunix/ndm/ioexit-plugins/s3:\
:options=-Xmx640m \
-Djava.class.path=/opt/cdunix/ndm/ioexit-plugins/s3/cd-s3-ioexit.jar \
-Ds3.profilePath='/home/cduser/.aws/credentials' \
-Ds3.profileName=aws-profile-02 \
com.aricent.ibm.mft.connectdirect.s3ioexit.S3IOExitFactory:
</syntaxhighlight>

== Mounting the .aws Directory in Kubernetes ==
The `.aws` directory containing the **credentials** file must be mounted on the Connect:Direct container at:

<syntaxhighlight lang="bash">/home/cduser/.aws</syntaxhighlight>

This can be achieved via Helm chart configuration using `extraVolume` and `extraVolumeMount`.

=== Example Helm Values Configuration ===
<syntaxhighlight lang="yaml"># Mount the .aws directory in the container
extraVolumeMounts:
- name: awsvol
mountPath: /home/cduser/.aws

# Define the NFS volume in the pod spec
extraVolume:
- name: awsvol
nfs:
server: <NFS server IP>
path: /srv/nfs/.aws/
</syntaxhighlight>

Ensure that the '''.aws/credentials''' file are already placed on the NFS path '''before''' deploying the chart.

= Ver também =

* [[IBM Sterling| Artigos sobre IBM Sterling]]

* [[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: Configuring C:D to use AWS S3 Storage provide an AWS credentials file as a volume

2026-03-12T18:43:18Z

Ebasso: /* Mounting the .aws Directory in Kubernetes */

This article describes how to configure IBM Connect:Direct (CDU) to access S3-compatible object storage.

The setup involves preparing AWS-style configuration files, updating `Initparm.cfg`, and mounting the necessary credential files into the Connect:Direct pod using Kubernetes `extraVolume` and `extraVolumeMount` parameters.

== AWS Configuration Files ==

The file credentials must be created under the user's `.aws` directory:

=== Example: credentials File ===
<syntaxhighlight lang="ini">[default]
aws_access_key_id = <profile id>
aws_secret_access_key = <access key>

[aws-profile02]
aws_access_key_id = <profile id>
aws_secret_access_key = <access key>
</syntaxhighlight>

These files can be automatically generated using the AWS CLI:

<syntaxhighlight lang="bash">aws configure --profile aws-profile02</syntaxhighlight>

== Updating Initparm.cfg ==
The following S3 I/O Exit configuration must be added to `Initparm.cfg`:

<syntaxhighlight lang="ini"># S3 IO Exit parameters
file.ioexit:\
:name=s3:\
:library=/opt/cdunix/ndm/lib/libcdjnibridge.so:\
:home.dir=/opt/cdunix/ndm/ioexit-plugins/s3:\
:options=-Xmx640m \
-Djava.class.path=/opt/cdunix/ndm/ioexit-plugins/s3/cd-s3-ioexit.jar \
-Ds3.profilePath='/home/cduser/.aws/credentials' \
-Ds3.profileName=default \
com.aricent.ibm.mft.connectdirect.s3ioexit.S3IOExitFactory:

file.ioexit:\
:name=s3qa:\
:library=/opt/cdunix/ndm/lib/libcdjnibridge.so:\
:home.dir=/opt/cdunix/ndm/ioexit-plugins/s3:\
:options=-Xmx640m \
-Djava.class.path=/opt/cdunix/ndm/ioexit-plugins/s3/cd-s3-ioexit.jar \
-Ds3.profilePath='/home/cduser/.aws/credentials' \
-Ds3.profileName=aws-profile-02 \
com.aricent.ibm.mft.connectdirect.s3ioexit.S3IOExitFactory:
</syntaxhighlight>

== Mounting the .aws Directory in Kubernetes ==
The `.aws` directory containing the **credentials** file must be mounted on the Connect:Direct container at:

<syntaxhighlight lang="bash">/home/cduser/.aws</syntaxhighlight>

This can be achieved via Helm chart configuration using `extraVolume` and `extraVolumeMount`.

=== Example Helm Values Configuration ===
<syntaxhighlight lang="yaml"># Mount the .aws directory in the container
extraVolumeMounts:
- name: extravol
mountPath: /home/cduser/.aws

# Define the NFS volume in the pod spec
extraVolume:
- name: extravol
nfs:
server: <NFS server IP>
path: /srv/nfs/.aws/
</syntaxhighlight>

Ensure that the '''.aws/credentials''' file are already placed on the NFS path '''before''' deploying the chart.

= Ver também =

* [[IBM Sterling| Artigos sobre IBM Sterling]]

* [[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: Configuring C:D to use AWS S3 Storage provide an AWS credentials file as a volume

2026-03-12T18:40:21Z

Ebasso: /* Example Helm Values Configuration */

This article describes how to configure IBM Connect:Direct (CDU) to access S3-compatible object storage.

The setup involves preparing AWS-style configuration files, updating `Initparm.cfg`, and mounting the necessary credential files into the Connect:Direct pod using Kubernetes `extraVolume` and `extraVolumeMount` parameters.

== AWS Configuration Files ==

The file credentials must be created under the user's `.aws` directory:

=== Example: credentials File ===
<syntaxhighlight lang="ini">[default]
aws_access_key_id = <profile id>
aws_secret_access_key = <access key>

[aws-profile02]
aws_access_key_id = <profile id>
aws_secret_access_key = <access key>
</syntaxhighlight>

These files can be automatically generated using the AWS CLI:

<syntaxhighlight lang="bash">aws configure --profile aws-profile02</syntaxhighlight>

== Updating Initparm.cfg ==
The following S3 I/O Exit configuration must be added to `Initparm.cfg`:

<syntaxhighlight lang="ini"># S3 IO Exit parameters
file.ioexit:\
:name=s3:\
:library=/opt/cdunix/ndm/lib/libcdjnibridge.so:\
:home.dir=/opt/cdunix/ndm/ioexit-plugins/s3:\
:options=-Xmx640m \
-Djava.class.path=/opt/cdunix/ndm/ioexit-plugins/s3/cd-s3-ioexit.jar \
-Ds3.profilePath='/home/cduser/.aws/credentials' \
-Ds3.profileName=default \
com.aricent.ibm.mft.connectdirect.s3ioexit.S3IOExitFactory:

file.ioexit:\
:name=s3qa:\
:library=/opt/cdunix/ndm/lib/libcdjnibridge.so:\
:home.dir=/opt/cdunix/ndm/ioexit-plugins/s3:\
:options=-Xmx640m \
-Djava.class.path=/opt/cdunix/ndm/ioexit-plugins/s3/cd-s3-ioexit.jar \
-Ds3.profilePath='/home/cduser/.aws/credentials' \
-Ds3.profileName=aws-profile-02 \
com.aricent.ibm.mft.connectdirect.s3ioexit.S3IOExitFactory:
</syntaxhighlight>

== Mounting the .aws Directory in Kubernetes ==
The `.aws` directory containing the **config** and **credentials** files must be mounted on the Connect:Direct container at:

<syntaxhighlight lang="bash">/home/cduser/.aws</syntaxhighlight>

This can be achieved via Helm chart configuration using `extraVolume` and `extraVolumeMount`.

=== Example Helm Values Configuration ===
<syntaxhighlight lang="yaml"># Mount the .aws directory in the container
extraVolumeMounts:
- name: extravol
mountPath: /home/cduser/.aws

# Define the NFS volume in the pod spec
extraVolume:
- name: extravol
nfs:
server: <NFS server IP>
path: /srv/nfs/.aws/
</syntaxhighlight>

Ensure that the '''.aws/credentials''' file are already placed on the NFS path '''before''' deploying the chart.

= Ver também =

* [[IBM Sterling| Artigos sobre IBM Sterling]]

* [[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: Configuring C:D to use AWS S3 Storage provide an AWS credentials file as a volume

2026-03-12T18:40:05Z

Ebasso: /* Example Helm Values Configuration */

This article describes how to configure IBM Connect:Direct (CDU) to access S3-compatible object storage.

The setup involves preparing AWS-style configuration files, updating `Initparm.cfg`, and mounting the necessary credential files into the Connect:Direct pod using Kubernetes `extraVolume` and `extraVolumeMount` parameters.

== AWS Configuration Files ==

The file credentials must be created under the user's `.aws` directory:

=== Example: credentials File ===
<syntaxhighlight lang="ini">[default]
aws_access_key_id = <profile id>
aws_secret_access_key = <access key>

[aws-profile02]
aws_access_key_id = <profile id>
aws_secret_access_key = <access key>
</syntaxhighlight>

These files can be automatically generated using the AWS CLI:

<syntaxhighlight lang="bash">aws configure --profile aws-profile02</syntaxhighlight>

== Updating Initparm.cfg ==
The following S3 I/O Exit configuration must be added to `Initparm.cfg`:

<syntaxhighlight lang="ini"># S3 IO Exit parameters
file.ioexit:\
:name=s3:\
:library=/opt/cdunix/ndm/lib/libcdjnibridge.so:\
:home.dir=/opt/cdunix/ndm/ioexit-plugins/s3:\
:options=-Xmx640m \
-Djava.class.path=/opt/cdunix/ndm/ioexit-plugins/s3/cd-s3-ioexit.jar \
-Ds3.profilePath='/home/cduser/.aws/credentials' \
-Ds3.profileName=default \
com.aricent.ibm.mft.connectdirect.s3ioexit.S3IOExitFactory:

file.ioexit:\
:name=s3qa:\
:library=/opt/cdunix/ndm/lib/libcdjnibridge.so:\
:home.dir=/opt/cdunix/ndm/ioexit-plugins/s3:\
:options=-Xmx640m \
-Djava.class.path=/opt/cdunix/ndm/ioexit-plugins/s3/cd-s3-ioexit.jar \
-Ds3.profilePath='/home/cduser/.aws/credentials' \
-Ds3.profileName=aws-profile-02 \
com.aricent.ibm.mft.connectdirect.s3ioexit.S3IOExitFactory:
</syntaxhighlight>

== Mounting the .aws Directory in Kubernetes ==
The `.aws` directory containing the **config** and **credentials** files must be mounted on the Connect:Direct container at:

<syntaxhighlight lang="bash">/home/cduser/.aws</syntaxhighlight>

This can be achieved via Helm chart configuration using `extraVolume` and `extraVolumeMount`.

=== Example Helm Values Configuration ===
<syntaxhighlight lang="yaml"># Mount the .aws directory in the container
extraVolumeMounts:
- name: extravol
mountPath: /home/cduser/.aws

# Define the NFS volume in the pod spec
extraVolume:
- name: extravol
nfs:
server: <NFS server IP>
path: /srv/nfs/.aws/
</syntaxhighlight>

Ensure that the `.aws/credentials` file are already placed on the NFS path '''before''' deploying the chart.

= Ver também =

* [[IBM Sterling| Artigos sobre IBM Sterling]]

* [[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: Configuring C:D to use AWS S3 Storage provide an AWS credentials file as a volume

2026-03-12T18:39:18Z

Ebasso: /* Summary */

This article describes how to configure IBM Connect:Direct (CDU) to access S3-compatible object storage.

The setup involves preparing AWS-style configuration files, updating `Initparm.cfg`, and mounting the necessary credential files into the Connect:Direct pod using Kubernetes `extraVolume` and `extraVolumeMount` parameters.

== AWS Configuration Files ==

The file credentials must be created under the user's `.aws` directory:

=== Example: credentials File ===
<syntaxhighlight lang="ini">[default]
aws_access_key_id = <profile id>
aws_secret_access_key = <access key>

[aws-profile02]
aws_access_key_id = <profile id>
aws_secret_access_key = <access key>
</syntaxhighlight>

These files can be automatically generated using the AWS CLI:

<syntaxhighlight lang="bash">aws configure --profile aws-profile02</syntaxhighlight>

== Updating Initparm.cfg ==
The following S3 I/O Exit configuration must be added to `Initparm.cfg`:

<syntaxhighlight lang="ini"># S3 IO Exit parameters
file.ioexit:\
:name=s3:\
:library=/opt/cdunix/ndm/lib/libcdjnibridge.so:\
:home.dir=/opt/cdunix/ndm/ioexit-plugins/s3:\
:options=-Xmx640m \
-Djava.class.path=/opt/cdunix/ndm/ioexit-plugins/s3/cd-s3-ioexit.jar \
-Ds3.profilePath='/home/cduser/.aws/credentials' \
-Ds3.profileName=default \
com.aricent.ibm.mft.connectdirect.s3ioexit.S3IOExitFactory:

file.ioexit:\
:name=s3qa:\
:library=/opt/cdunix/ndm/lib/libcdjnibridge.so:\
:home.dir=/opt/cdunix/ndm/ioexit-plugins/s3:\
:options=-Xmx640m \
-Djava.class.path=/opt/cdunix/ndm/ioexit-plugins/s3/cd-s3-ioexit.jar \
-Ds3.profilePath='/home/cduser/.aws/credentials' \
-Ds3.profileName=aws-profile-02 \
com.aricent.ibm.mft.connectdirect.s3ioexit.S3IOExitFactory:
</syntaxhighlight>

== Mounting the .aws Directory in Kubernetes ==
The `.aws` directory containing the **config** and **credentials** files must be mounted on the Connect:Direct container at:

<syntaxhighlight lang="bash">/home/cduser/.aws</syntaxhighlight>

This can be achieved via Helm chart configuration using `extraVolume` and `extraVolumeMount`.

=== Example Helm Values Configuration ===
<syntaxhighlight lang="yaml"># Mount the .aws directory in the container
extraVolumeMounts:
- name: extravol
mountPath: /home/cduser/.aws

# Define the NFS volume in the pod spec
extraVolume:
- name: extravol
nfs:
server: <NFS server IP>
path: /srv/nfs/.aws/
</syntaxhighlight>

Ensure that the `.aws/config` and `.aws/credentials` files are already placed on the NFS path **before** deploying the chart.

= Ver também =

* [[IBM Sterling| Artigos sobre IBM Sterling]]

* [[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: Configuring C:D to use AWS S3 Storage provide an AWS credentials file as a volume

2026-03-12T18:38:41Z

Ebasso: /* Using S3 in Process Files */

This article describes how to configure IBM Connect:Direct (CDU) to access S3-compatible object storage.

The setup involves preparing AWS-style configuration files, updating `Initparm.cfg`, and mounting the necessary credential files into the Connect:Direct pod using Kubernetes `extraVolume` and `extraVolumeMount` parameters.

== AWS Configuration Files ==

The file credentials must be created under the user's `.aws` directory:

=== Example: credentials File ===
<syntaxhighlight lang="ini">[default]
aws_access_key_id = <profile id>
aws_secret_access_key = <access key>

[aws-profile02]
aws_access_key_id = <profile id>
aws_secret_access_key = <access key>
</syntaxhighlight>

These files can be automatically generated using the AWS CLI:

<syntaxhighlight lang="bash">aws configure --profile aws-profile02</syntaxhighlight>

== Updating Initparm.cfg ==
The following S3 I/O Exit configuration must be added to `Initparm.cfg`:

<syntaxhighlight lang="ini"># S3 IO Exit parameters
file.ioexit:\
:name=s3:\
:library=/opt/cdunix/ndm/lib/libcdjnibridge.so:\
:home.dir=/opt/cdunix/ndm/ioexit-plugins/s3:\
:options=-Xmx640m \
-Djava.class.path=/opt/cdunix/ndm/ioexit-plugins/s3/cd-s3-ioexit.jar \
-Ds3.profilePath='/home/cduser/.aws/credentials' \
-Ds3.profileName=default \
com.aricent.ibm.mft.connectdirect.s3ioexit.S3IOExitFactory:

file.ioexit:\
:name=s3qa:\
:library=/opt/cdunix/ndm/lib/libcdjnibridge.so:\
:home.dir=/opt/cdunix/ndm/ioexit-plugins/s3:\
:options=-Xmx640m \
-Djava.class.path=/opt/cdunix/ndm/ioexit-plugins/s3/cd-s3-ioexit.jar \
-Ds3.profilePath='/home/cduser/.aws/credentials' \
-Ds3.profileName=aws-profile-02 \
com.aricent.ibm.mft.connectdirect.s3ioexit.S3IOExitFactory:
</syntaxhighlight>

== Mounting the .aws Directory in Kubernetes ==
The `.aws` directory containing the **config** and **credentials** files must be mounted on the Connect:Direct container at:

<syntaxhighlight lang="bash">/home/cduser/.aws</syntaxhighlight>

This can be achieved via Helm chart configuration using `extraVolume` and `extraVolumeMount`.

=== Example Helm Values Configuration ===
<syntaxhighlight lang="yaml"># Mount the .aws directory in the container
extraVolumeMounts:
- name: extravol
mountPath: /home/cduser/.aws

# Define the NFS volume in the pod spec
extraVolume:
- name: extravol
nfs:
server: <NFS server IP>
path: /srv/nfs/.aws/
</syntaxhighlight>

Ensure that the `.aws/config` and `.aws/credentials` files are already placed on the NFS path **before** deploying the chart.

== Summary ==
By preparing AWS configuration files, configuring the S3 I/O Exit in `Initparm.cfg`, and mounting the `.aws` directory via Kubernetes volumes, IBM Connect:Direct can seamlessly interact with S3-compatible object storage systems such as Dell EMC. This setup allows secure and flexible object-based file transfers within Connect:Direct processes.

= Ver também =

* [[IBM Sterling| Artigos sobre IBM Sterling]]

* [[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: Configuring C:D to use AWS S3 Storage provide an AWS credentials file as a volume

2026-03-12T18:38:25Z

Ebasso: /* Updating Initparm.cfg */

This article describes how to configure IBM Connect:Direct (CDU) to access S3-compatible object storage.

The setup involves preparing AWS-style configuration files, updating `Initparm.cfg`, and mounting the necessary credential files into the Connect:Direct pod using Kubernetes `extraVolume` and `extraVolumeMount` parameters.

== AWS Configuration Files ==

The file credentials must be created under the user's `.aws` directory:

=== Example: credentials File ===
<syntaxhighlight lang="ini">[default]
aws_access_key_id = <profile id>
aws_secret_access_key = <access key>

[aws-profile02]
aws_access_key_id = <profile id>
aws_secret_access_key = <access key>
</syntaxhighlight>

These files can be automatically generated using the AWS CLI:

<syntaxhighlight lang="bash">aws configure --profile aws-profile02</syntaxhighlight>

== Updating Initparm.cfg ==
The following S3 I/O Exit configuration must be added to `Initparm.cfg`:

<syntaxhighlight lang="ini"># S3 IO Exit parameters
file.ioexit:\
:name=s3:\
:library=/opt/cdunix/ndm/lib/libcdjnibridge.so:\
:home.dir=/opt/cdunix/ndm/ioexit-plugins/s3:\
:options=-Xmx640m \
-Djava.class.path=/opt/cdunix/ndm/ioexit-plugins/s3/cd-s3-ioexit.jar \
-Ds3.profilePath='/home/cduser/.aws/credentials' \
-Ds3.profileName=default \
com.aricent.ibm.mft.connectdirect.s3ioexit.S3IOExitFactory:

file.ioexit:\
:name=s3qa:\
:library=/opt/cdunix/ndm/lib/libcdjnibridge.so:\
:home.dir=/opt/cdunix/ndm/ioexit-plugins/s3:\
:options=-Xmx640m \
-Djava.class.path=/opt/cdunix/ndm/ioexit-plugins/s3/cd-s3-ioexit.jar \
-Ds3.profilePath='/home/cduser/.aws/credentials' \
-Ds3.profileName=aws-profile-02 \
com.aricent.ibm.mft.connectdirect.s3ioexit.S3IOExitFactory:
</syntaxhighlight>

== Using S3 in Process Files ==
When referencing S3 paths in Connect:Direct processes, use the **s://** prefix to indicate that S3 object storage is being accessed.

== Mounting the .aws Directory in Kubernetes ==
The `.aws` directory containing the **config** and **credentials** files must be mounted on the Connect:Direct container at:

<syntaxhighlight lang="bash">/home/cduser/.aws</syntaxhighlight>

This can be achieved via Helm chart configuration using `extraVolume` and `extraVolumeMount`.

=== Example Helm Values Configuration ===
<syntaxhighlight lang="yaml"># Mount the .aws directory in the container
extraVolumeMounts:
- name: extravol
mountPath: /home/cduser/.aws

# Define the NFS volume in the pod spec
extraVolume:
- name: extravol
nfs:
server: <NFS server IP>
path: /srv/nfs/.aws/
</syntaxhighlight>

Ensure that the `.aws/config` and `.aws/credentials` files are already placed on the NFS path **before** deploying the chart.

== Summary ==
By preparing AWS configuration files, configuring the S3 I/O Exit in `Initparm.cfg`, and mounting the `.aws` directory via Kubernetes volumes, IBM Connect:Direct can seamlessly interact with S3-compatible object storage systems such as Dell EMC. This setup allows secure and flexible object-based file transfers within Connect:Direct processes.

= Ver também =

* [[IBM Sterling| Artigos sobre IBM Sterling]]

* [[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: Configuring C:D to use AWS S3 Storage provide an AWS credentials file as a volume

2026-03-12T18:37:06Z

Ebasso: /* AWS Configuration Files */

This article describes how to configure IBM Connect:Direct (CDU) to access S3-compatible object storage.

The setup involves preparing AWS-style configuration files, updating `Initparm.cfg`, and mounting the necessary credential files into the Connect:Direct pod using Kubernetes `extraVolume` and `extraVolumeMount` parameters.

== AWS Configuration Files ==

The file credentials must be created under the user's `.aws` directory:

=== Example: credentials File ===
<syntaxhighlight lang="ini">[default]
aws_access_key_id = <profile id>
aws_secret_access_key = <access key>

[aws-profile02]
aws_access_key_id = <profile id>
aws_secret_access_key = <access key>
</syntaxhighlight>

These files can be automatically generated using the AWS CLI:

<syntaxhighlight lang="bash">aws configure --profile aws-profile02</syntaxhighlight>

== Updating Initparm.cfg ==
The following S3 I/O Exit configuration must be added to `Initparm.cfg`:

<syntaxhighlight lang="ini"># S3 IO Exit parameters
file.ioexit:\
:name=s3:\
:library=/opt/cdunix/ndm/lib/libcdjnibridge.so:\
:home.dir=/opt/cdunix/ndm/ioexit-plugins/s3:\
:options=-Xmx640m \
-Djava.class.path=/opt/cdunix/ndm/ioexit-plugins/s3/cd-s3-ioexit.jar \
-Ds3.endPointUrl=<S3 source IP> \
-Ds3.endPointPort=<port number> \
-Ds3.endPointSecure=NO \
-Ds3.profilePath='/home/cduser/.aws/credentials' \
-Ds3.profileName=<profile name> \
com.aricent.ibm.mft.connectdirect.s3ioexit.S3IOExitFactory:

</syntaxhighlight>

== Using S3 in Process Files ==
When referencing S3 paths in Connect:Direct processes, use the **s://** prefix to indicate that S3 object storage is being accessed.

== Mounting the .aws Directory in Kubernetes ==
The `.aws` directory containing the **config** and **credentials** files must be mounted on the Connect:Direct container at:

<syntaxhighlight lang="bash">/home/cduser/.aws</syntaxhighlight>

This can be achieved via Helm chart configuration using `extraVolume` and `extraVolumeMount`.

=== Example Helm Values Configuration ===
<syntaxhighlight lang="yaml"># Mount the .aws directory in the container
extraVolumeMounts:
- name: extravol
mountPath: /home/cduser/.aws

# Define the NFS volume in the pod spec
extraVolume:
- name: extravol
nfs:
server: <NFS server IP>
path: /srv/nfs/.aws/
</syntaxhighlight>

Ensure that the `.aws/config` and `.aws/credentials` files are already placed on the NFS path **before** deploying the chart.

== Summary ==
By preparing AWS configuration files, configuring the S3 I/O Exit in `Initparm.cfg`, and mounting the `.aws` directory via Kubernetes volumes, IBM Connect:Direct can seamlessly interact with S3-compatible object storage systems such as Dell EMC. This setup allows secure and flexible object-based file transfers within Connect:Direct processes.

= Ver também =

* [[IBM Sterling| Artigos sobre IBM Sterling]]

* [[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: Configuring C:D to use AWS S3 Storage provide an AWS credentials file as a volume

2026-03-12T18:35:54Z

Ebasso: /* AWS Configuration Files */

This article describes how to configure IBM Connect:Direct (CDU) to access S3-compatible object storage.

The setup involves preparing AWS-style configuration files, updating `Initparm.cfg`, and mounting the necessary credential files into the Connect:Direct pod using Kubernetes `extraVolume` and `extraVolumeMount` parameters.

== AWS Configuration Files ==

Two files must be created under the user's `.aws` directory: the **config** file and the **credentials** file.

=== Example: credentials File ===
<syntaxhighlight lang="ini">[default]
aws_access_key_id = <profile id>
aws_secret_access_key = <access key>

[aws-profile02]
aws_access_key_id = <profile id>
aws_secret_access_key = <access key>
</syntaxhighlight>

These files can be automatically generated using the AWS CLI:

<syntaxhighlight lang="bash">aws configure --profile aws-profile02</syntaxhighlight>

== Updating Initparm.cfg ==
The following S3 I/O Exit configuration must be added to `Initparm.cfg`:

<syntaxhighlight lang="ini"># S3 IO Exit parameters
file.ioexit:\
:name=s3:\
:library=/opt/cdunix/ndm/lib/libcdjnibridge.so:\
:home.dir=/opt/cdunix/ndm/ioexit-plugins/s3:\
:options=-Xmx640m \
-Djava.class.path=/opt/cdunix/ndm/ioexit-plugins/s3/cd-s3-ioexit.jar \
-Ds3.endPointUrl=<S3 source IP> \
-Ds3.endPointPort=<port number> \
-Ds3.endPointSecure=NO \
-Ds3.profilePath='/home/cduser/.aws/credentials' \
-Ds3.profileName=<profile name> \
com.aricent.ibm.mft.connectdirect.s3ioexit.S3IOExitFactory:

</syntaxhighlight>

== Using S3 in Process Files ==
When referencing S3 paths in Connect:Direct processes, use the **s://** prefix to indicate that S3 object storage is being accessed.

== Mounting the .aws Directory in Kubernetes ==
The `.aws` directory containing the **config** and **credentials** files must be mounted on the Connect:Direct container at:

<syntaxhighlight lang="bash">/home/cduser/.aws</syntaxhighlight>

This can be achieved via Helm chart configuration using `extraVolume` and `extraVolumeMount`.

=== Example Helm Values Configuration ===
<syntaxhighlight lang="yaml"># Mount the .aws directory in the container
extraVolumeMounts:
- name: extravol
mountPath: /home/cduser/.aws

# Define the NFS volume in the pod spec
extraVolume:
- name: extravol
nfs:
server: <NFS server IP>
path: /srv/nfs/.aws/
</syntaxhighlight>

Ensure that the `.aws/config` and `.aws/credentials` files are already placed on the NFS path **before** deploying the chart.

== Summary ==
By preparing AWS configuration files, configuring the S3 I/O Exit in `Initparm.cfg`, and mounting the `.aws` directory via Kubernetes volumes, IBM Connect:Direct can seamlessly interact with S3-compatible object storage systems such as Dell EMC. This setup allows secure and flexible object-based file transfers within Connect:Direct processes.

= Ver também =

* [[IBM Sterling| Artigos sobre IBM Sterling]]

* [[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: Configuring C:D to use AWS S3 Storage provide an AWS credentials file as a volume

2026-03-12T18:32:16Z

Ebasso: /* Updating Initparm.cfg */

This article describes how to configure IBM Connect:Direct (CDU) to access S3-compatible object storage.

The setup involves preparing AWS-style configuration files, updating `Initparm.cfg`, and mounting the necessary credential files into the Connect:Direct pod using Kubernetes `extraVolume` and `extraVolumeMount` parameters.

== AWS Configuration Files ==

Two files must be created under the user's `.aws` directory: the **config** file and the **credentials** file.

=== Example: config File ===
<syntaxhighlight lang="ini">[default]
output = json
region = us-east-1

[profile emc]
</syntaxhighlight>

=== Example: credentials File ===
<syntaxhighlight lang="ini">[emc]
aws_access_key_id = <profile id>
aws_secret_access_key = <access key>
</syntaxhighlight>

These files can be automatically generated using the AWS CLI:

<syntaxhighlight lang="bash">aws configure --profile emc</syntaxhighlight>

You will be prompted to enter region, access key, and secret key. After creation, the `.aws` directory must later be mounted inside the pod.

== Updating Initparm.cfg ==
The following S3 I/O Exit configuration must be added to `Initparm.cfg`:

<syntaxhighlight lang="ini"># S3 IO Exit parameters
file.ioexit:\
:name=s3:\
:library=/opt/cdunix/ndm/lib/libcdjnibridge.so:\
:home.dir=/opt/cdunix/ndm/ioexit-plugins/s3:\
:options=-Xmx640m \
-Djava.class.path=/opt/cdunix/ndm/ioexit-plugins/s3/cd-s3-ioexit.jar \
-Ds3.endPointUrl=<S3 source IP> \
-Ds3.endPointPort=<port number> \
-Ds3.endPointSecure=NO \
-Ds3.profilePath='/home/cduser/.aws/credentials' \
-Ds3.profileName=<profile name> \
com.aricent.ibm.mft.connectdirect.s3ioexit.S3IOExitFactory:

</syntaxhighlight>

== Using S3 in Process Files ==
When referencing S3 paths in Connect:Direct processes, use the **s://** prefix to indicate that S3 object storage is being accessed.

== Mounting the .aws Directory in Kubernetes ==
The `.aws` directory containing the **config** and **credentials** files must be mounted on the Connect:Direct container at:

<syntaxhighlight lang="bash">/home/cduser/.aws</syntaxhighlight>

This can be achieved via Helm chart configuration using `extraVolume` and `extraVolumeMount`.

=== Example Helm Values Configuration ===
<syntaxhighlight lang="yaml"># Mount the .aws directory in the container
extraVolumeMounts:
- name: extravol
mountPath: /home/cduser/.aws

# Define the NFS volume in the pod spec
extraVolume:
- name: extravol
nfs:
server: <NFS server IP>
path: /srv/nfs/.aws/
</syntaxhighlight>

Ensure that the `.aws/config` and `.aws/credentials` files are already placed on the NFS path **before** deploying the chart.

== Summary ==
By preparing AWS configuration files, configuring the S3 I/O Exit in `Initparm.cfg`, and mounting the `.aws` directory via Kubernetes volumes, IBM Connect:Direct can seamlessly interact with S3-compatible object storage systems such as Dell EMC. This setup allows secure and flexible object-based file transfers within Connect:Direct processes.

= Ver também =

* [[IBM Sterling| Artigos sobre IBM Sterling]]

* [[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: Configuring C:D to use AWS S3 Storage provide an AWS credentials file as a volume

2026-03-12T18:31:25Z

Ebasso: Created page with "This article describes how to configure IBM Connect:Direct (CDU) to access S3-compatible object storage. The setup involves preparing AWS-style configuration files, updating `Initparm.cfg`, and mounting the necessary credential files into the Connect:Direct pod using Kubernetes `extraVolume` and `extraVolumeMount` parameters. == AWS Configuration Files == Two files must be created under the user's `.aws` directory: the **config** file and the **credentials** file. =..."

This article describes how to configure IBM Connect:Direct (CDU) to access S3-compatible object storage.

The setup involves preparing AWS-style configuration files, updating `Initparm.cfg`, and mounting the necessary credential files into the Connect:Direct pod using Kubernetes `extraVolume` and `extraVolumeMount` parameters.

== AWS Configuration Files ==

Two files must be created under the user's `.aws` directory: the **config** file and the **credentials** file.

=== Example: config File ===
<syntaxhighlight lang="ini">[default]
output = json
region = us-east-1

[profile emc]
</syntaxhighlight>

=== Example: credentials File ===
<syntaxhighlight lang="ini">[emc]
aws_access_key_id = <profile id>
aws_secret_access_key = <access key>
</syntaxhighlight>

These files can be automatically generated using the AWS CLI:

<syntaxhighlight lang="bash">aws configure --profile emc</syntaxhighlight>

You will be prompted to enter region, access key, and secret key. After creation, the `.aws` directory must later be mounted inside the pod.

== Updating Initparm.cfg ==
The following S3 I/O Exit configuration must be added to `Initparm.cfg`:

<syntaxhighlight lang="ini"># S3 IO Exit parameters
file.ioexit::name=s3::library=/opt/cdunix/ndm/lib/libcdjnibridge.so::home.dir=/opt/cdunix/ndm/ioexit-plugins/s3::options=-Xmx640m -Djava.class.path=/opt/cdunix/ndm/ioexit-plugins/s3/cd-s3-ioexit.jar -Ds3.endPointUrl=<Dell EMC IP> -Ds3.endPointPort=<port number> -Ds3.endPointSecure=NO -Ds3.profilePath='/home/cduser/.aws/credentials' -Ds3.profileName=<profile name> com.aricent.ibm.mft.connectdirect.s3ioexit.S3IOExitFactory:
</syntaxhighlight>

== Using S3 in Process Files ==
When referencing S3 paths in Connect:Direct processes, use the **s://** prefix to indicate that S3 object storage is being accessed.

== Mounting the .aws Directory in Kubernetes ==
The `.aws` directory containing the **config** and **credentials** files must be mounted on the Connect:Direct container at:

<syntaxhighlight lang="bash">/home/cduser/.aws</syntaxhighlight>

This can be achieved via Helm chart configuration using `extraVolume` and `extraVolumeMount`.

=== Example Helm Values Configuration ===
<syntaxhighlight lang="yaml"># Mount the .aws directory in the container
extraVolumeMounts:
- name: extravol
mountPath: /home/cduser/.aws

# Define the NFS volume in the pod spec
extraVolume:
- name: extravol
nfs:
server: <NFS server IP>
path: /srv/nfs/.aws/
</syntaxhighlight>

Ensure that the `.aws/config` and `.aws/credentials` files are already placed on the NFS path **before** deploying the chart.

== Summary ==
By preparing AWS configuration files, configuring the S3 I/O Exit in `Initparm.cfg`, and mounting the `.aws` directory via Kubernetes volumes, IBM Connect:Direct can seamlessly interact with S3-compatible object storage systems such as Dell EMC. This setup allows secure and flexible object-based file transfers within Connect:Direct processes.

= Ver também =

* [[IBM Sterling| Artigos sobre IBM Sterling]]

* [[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-03-12T18:30:29Z

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 : 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]]

== 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: Using extraVolume and extraVolumeMounts in IBM Connect:Direct Deployments

2026-03-12T18:26:24Z

Ebasso: /* Sample Configuration */

IBM Sterling Connect:Direct: Using extraVolume and extraVolumeMounts in IBM Connect:Direct Deployments

2026-03-12T18:26:02Z

Ebasso: /* Default Volume Mount Example */

When deploying '''IBM Connect:Direct''' in Kubernetes environments, administrators may need to augment the container with additional storage locations for configuration files, scripts, logs, key stores, partner‑exchange directories, or other operational assets.

To support this requirement, the Connect:Direct deployment architecture includes two extensible configuration fields:

* '''extraVolume'''
* '''extraVolumeMounts'''

These fields allow users to define and mount additional hostPath or persistent volumes into the Connect:Direct container '''without modifying the base container image''', maintaining flexibility and portability.

= Sample Configuration =
Below is a complete example showing how to define and mount two custom volumes: one backed by a local host path and another backed by NFS.

== extraVolume Definition ==
<syntaxhighlight lang="yaml">
extraVolume:
- name: svshare-volume
hostPath:
path: /svshare
type: Directory

- name: backup-volume
nfs:
path: <nfs data path>
server: <server ip>
</syntaxhighlight>

== extraVolumeMounts Definition ==
<syntaxhighlight lang="yaml">
extraVolumeMounts:
- name: svshare-volume
mountPath: /svshare

# Replace BACKUP (/opt/backup)
- name: backup-volume
mountPath: /opt/backup
</syntaxhighlight>

= Ver também =

* [[IBM Sterling| Artigos sobre IBM Sterling]]

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

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

IBM Sterling Connect:Direct: Using extraVolume and extraVolumeMounts in IBM Connect:Direct Deployments

2026-03-12T18:25:49Z

Ebasso: /* Purpose of `extraVolume` and `extraVolumeMounts` */

When deploying '''IBM Connect:Direct''' in Kubernetes environments, administrators may need to augment the container with additional storage locations for configuration files, scripts, logs, key stores, partner‑exchange directories, or other operational assets.

To support this requirement, the Connect:Direct deployment architecture includes two extensible configuration fields:

* '''extraVolume'''
* '''extraVolumeMounts'''

These fields allow users to define and mount additional hostPath or persistent volumes into the Connect:Direct container '''without modifying the base container image''', maintaining flexibility and portability.

= Default Volume Mount Example =
The deployment may include a default mount (as illustrated in the documentation), but additional volumes can be layered using these fields.

= Sample Configuration =
Below is a complete example showing how to define and mount two custom volumes: one backed by a local host path and another backed by NFS.

== extraVolume Definition ==
<syntaxhighlight lang="yaml">
extraVolume:
- name: svshare-volume
hostPath:
path: /svshare
type: Directory

- name: backup-volume
nfs:
path: <nfs data path>
server: <server ip>
</syntaxhighlight>

== extraVolumeMounts Definition ==
<syntaxhighlight lang="yaml">
extraVolumeMounts:
- name: svshare-volume
mountPath: /svshare

# Replace BACKUP (/opt/backup)
- name: backup-volume
mountPath: /opt/backup
</syntaxhighlight>

= Ver também =

* [[IBM Sterling| Artigos sobre IBM Sterling]]

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

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

IBM Sterling Connect:Direct: Using extraVolume and extraVolumeMounts in IBM Connect:Direct Deployments

2026-03-12T18:25:12Z

Ebasso:

When deploying '''IBM Connect:Direct''' in Kubernetes environments, administrators may need to augment the container with additional storage locations for configuration files, scripts, logs, key stores, partner‑exchange directories, or other operational assets.

To support this requirement, the Connect:Direct deployment architecture includes two extensible configuration fields:

* '''extraVolume'''
* '''extraVolumeMounts'''

These fields allow users to define and mount additional hostPath or persistent volumes into the Connect:Direct container '''without modifying the base container image''', maintaining flexibility and portability.

= Purpose of `extraVolume` and `extraVolumeMounts` =
The two fields work together as follows:

* '''extraVolume''' – Defines additional Kubernetes volumes—such as hostPath, NFS, emptyDir, or PVC references—that should be attached to the pod.
* '''extraVolumeMounts''' – Specifies where inside the Connect:Direct container each extra volume should be mounted.

This modular approach enables administrators to expand storage mappings in a controlled and repeatable way.

= Default Volume Mount Example =
The deployment may include a default mount (as illustrated in the documentation), but additional volumes can be layered using these fields.

= Sample Configuration =
Below is a complete example showing how to define and mount two custom volumes: one backed by a local host path and another backed by NFS.

== extraVolume Definition ==
<syntaxhighlight lang="yaml">
extraVolume:
- name: svshare-volume
hostPath:
path: /svshare
type: Directory

- name: backup-volume
nfs:
path: <nfs data path>
server: <server ip>
</syntaxhighlight>

== extraVolumeMounts Definition ==
<syntaxhighlight lang="yaml">
extraVolumeMounts:
- name: svshare-volume
mountPath: /svshare

# Replace BACKUP (/opt/backup)
- name: backup-volume
mountPath: /opt/backup
</syntaxhighlight>

= Ver também =

* [[IBM Sterling| Artigos sobre IBM Sterling]]

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

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

IBM Sterling Connect:Direct: Using extraVolume and extraVolumeMounts in IBM Connect:Direct Deployments

2026-03-12T18:24:40Z

Ebasso: /* Summary */

= Using `extraVolume` and `extraVolumeMounts` in IBM Connect:Direct Deployments =

When deploying '''IBM Connect:Direct''' in Kubernetes environments, administrators may need to augment the container with additional storage locations for configuration files, scripts, logs, key stores, partner‑exchange directories, or other operational assets.

To support this requirement, the Connect:Direct deployment architecture includes two extensible configuration fields:

* '''extraVolume'''
* '''extraVolumeMounts'''

These fields allow users to define and mount additional hostPath or persistent volumes into the Connect:Direct container '''without modifying the base container image''', maintaining flexibility and portability.

== Purpose of `extraVolume` and `extraVolumeMounts` ==
The two fields work together as follows:

* '''extraVolume''' – Defines additional Kubernetes volumes—such as hostPath, NFS, emptyDir, or PVC references—that should be attached to the pod.
* '''extraVolumeMounts''' – Specifies where inside the Connect:Direct container each extra volume should be mounted.

This modular approach enables administrators to expand storage mappings in a controlled and repeatable way.

== Default Volume Mount Example ==
The deployment may include a default mount (as illustrated in the documentation), but additional volumes can be layered using these fields.

== Sample Configuration ==
Below is a complete example showing how to define and mount two custom volumes: one backed by a local host path and another backed by NFS.

=== extraVolume Definition ===
<syntaxhighlight lang="yaml">
extraVolume:
- name: svshare-volume
hostPath:
path: /svshare
type: Directory

- name: backup-volume
nfs:
path: <nfs data path>
server: <server ip>
</syntaxhighlight>

=== extraVolumeMounts Definition ===
<syntaxhighlight lang="yaml">
extraVolumeMounts:
- name: svshare-volume
mountPath: /svshare

# Replace BACKUP (/opt/backup)
- name: backup-volume
mountPath: /opt/backup
</syntaxhighlight>

= Ver também =

* [[IBM Sterling| Artigos sobre IBM Sterling]]

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

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

IBM Sterling Connect:Direct: Using extraVolume and extraVolumeMounts in IBM Connect:Direct Deployments

2026-03-12T18:24:30Z

Ebasso: Created page with " = Using `extraVolume` and `extraVolumeMounts` in IBM Connect:Direct Deployments = When deploying '''IBM Connect:Direct''' in Kubernetes environments, administrators may need to augment the container with additional storage locations for configuration files, scripts, logs, key stores, partner‑exchange directories, or other operational assets. To support this requirement, the Connect:Direct deployment architecture includes two extensible configuration fields: * '''e..."

= Using `extraVolume` and `extraVolumeMounts` in IBM Connect:Direct Deployments =

When deploying '''IBM Connect:Direct''' in Kubernetes environments, administrators may need to augment the container with additional storage locations for configuration files, scripts, logs, key stores, partner‑exchange directories, or other operational assets.

To support this requirement, the Connect:Direct deployment architecture includes two extensible configuration fields:

* '''extraVolume'''
* '''extraVolumeMounts'''

These fields allow users to define and mount additional hostPath or persistent volumes into the Connect:Direct container '''without modifying the base container image''', maintaining flexibility and portability.

== Purpose of `extraVolume` and `extraVolumeMounts` ==
The two fields work together as follows:

* '''extraVolume''' – Defines additional Kubernetes volumes—such as hostPath, NFS, emptyDir, or PVC references—that should be attached to the pod.
* '''extraVolumeMounts''' – Specifies where inside the Connect:Direct container each extra volume should be mounted.

This modular approach enables administrators to expand storage mappings in a controlled and repeatable way.

== Default Volume Mount Example ==
The deployment may include a default mount (as illustrated in the documentation), but additional volumes can be layered using these fields.

== Sample Configuration ==
Below is a complete example showing how to define and mount two custom volumes: one backed by a local host path and another backed by NFS.

=== extraVolume Definition ===
<syntaxhighlight lang="yaml">
extraVolume:
- name: svshare-volume
hostPath:
path: /svshare
type: Directory

- name: backup-volume
nfs:
path: <nfs data path>
server: <server ip>
</syntaxhighlight>

=== extraVolumeMounts Definition ===
<syntaxhighlight lang="yaml">
extraVolumeMounts:
- name: svshare-volume
mountPath: /svshare

# Replace BACKUP (/opt/backup)
- name: backup-volume
mountPath: /opt/backup
</syntaxhighlight>

== Summary ==
By leveraging `extraVolume` and `extraVolumeMounts`, IBM Connect:Direct Kubernetes deployments can be extended with custom storage mappings tailored to operational needs. This approach ensures:

* Consistent configuration across environments
* No changes required to the container image
* Seamless integration with host‑based or network‑based storage
* Flexibility for automation and DevOps pipelines

= Ver também =

* [[IBM Sterling| Artigos sobre IBM Sterling]]

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

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

IBM Sterling Connect:Direct

2026-03-12T18:22:49Z

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 : 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: 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]]

== 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 Maximo: Resizing JPEG Files in doclinks

2026-03-04T16:07:44Z

Ebasso: /* Ver também */

If many photos are attached go IBM Maximo, the '''DOCLINKS''' folder can quickly consume large amounts of disk space.

You can resize JPEG files using ImageMagick on Linux.

== Procedure ==

1) Install ImageMagick

<nowiki>dnf install -y ImageMagick</nowiki>

2) Run image magic

<pre>
cd /opt/IBM/SMP/maximo/doclinks

find . -type f \( -iname "*.jpg" \) -exec mogrify -resize 1920x1920\> {} \;
</pre>

* '''Important''':

* Resizes images larger than 1920x1920.
* Keeps original file names.
* No database updates required in IBM Maximo.

= Ver também =

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

[[Category:IBM Maximo]]
[[Category:ibm-maximo-performance]]

IBM Maximo: Resizing JPEG Files in doclinks

2026-03-04T16:07:24Z

Ebasso: /* Procedure */

IBM Maximo: Resizing JPEG Files in doclinks

2026-03-04T16:07:11Z

Ebasso: /* Procedure */

If many photos are attached go IBM Maximo, the '''DOCLINKS''' folder can quickly consume large amounts of disk space.

You can resize JPEG files using ImageMagick on Linux.

== Procedure ==

1) Install ImageMagick

<nowiki>dnf install -y ImageMagick</nowiki>

2) Run image magic

<pre>
cd /opt/IBM/SMP/maximo/doclinks

find . -type f \( -iname "*.jpg" \) -exec mogrify -resize 1920x1920\> {} \;
</pre>

* **Important**:

* Resizes images larger than 1920x1920.
* Keeps original file names.
* No database updates required in IBM Maximo.

= Ver também =

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

[[Category:IBM Maximo]]
[[Category:ibm-maximo-performance]]
[[Category:ibm-maximo-messages]]

IBM Maximo: Resizing JPEG Files in doclinks

2026-03-04T16:06:58Z

Ebasso: /* Procedure */

If many photos are attached go IBM Maximo, the '''DOCLINKS''' folder can quickly consume large amounts of disk space.

You can resize JPEG files using ImageMagick on Linux.

== Procedure ==

1) Install ImageMagick

<nowiki>dnf install -y ImageMagick</nowiki>

2) Run image magic

<pre>
cd /opt/IBM/SMP/maximo/doclinks

find . -type f \( -iname "*.jpg" \) -exec mogrify -resize 1920x1920\> {} \;
</pre>

**Important**:

* Resizes images larger than 1920x1920.
* Keeps original file names.
* No database updates required in IBM Maximo.

= Ver também =

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

[[Category:IBM Maximo]]
[[Category:ibm-maximo-performance]]
[[Category:ibm-maximo-messages]]