User contributions for Ebasso
8 April 2026
- 00:1700:17, 8 April 2026 diff hist +1 IBM Maximo: Migrate MAXDB to RH OpenShift →Checking restored database current
- 00:1300:13, 8 April 2026 diff hist +584 IBM Maximo: Migrate MAXDB to RH OpenShift →Restore MAXDB76 backup file into Container
- 00:1100:11, 8 April 2026 diff hist +48 IBM Maximo: Migrate MAXDB to RH OpenShift →Restore MAXDB76 backup file into Container
- 00:1000:10, 8 April 2026 diff hist +9,642 N IBM Maximo: Migrate MAXDB to RH OpenShift (restoresql.sql) 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..." current
- 00:0900:09, 8 April 2026 diff hist +108 IBM Maximo: Migrate MAXDB to RH OpenShift →Restore MAXDB76 backup file into Container
- 00:0900:09, 8 April 2026 diff hist +672 IBM Maximo: Migrate MAXDB to RH OpenShift →Restore MAXDB76 backup file into Container
- 00:0500:05, 8 April 2026 diff hist −8 IBM Maximo: Migrate MAXDB to RH OpenShift →Copy MAXDB76 backup file into Container
- 00:0500:05, 8 April 2026 diff hist +114 IBM Maximo: Migrate MAXDB to RH OpenShift No edit summary
- 00:0200:02, 8 April 2026 diff hist +1,981 N IBM Maximo: Migrate MAXDB to RH OpenShift (db2ckbkp.out) 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..." current
- 00:0200:02, 8 April 2026 diff hist +108 IBM Maximo: Migrate MAXDB to RH OpenShift No edit summary
7 April 2026
- 23:5923:59, 7 April 2026 diff hist +117 IBM Maximo: Migrate MAXDB to RH OpenShift →Restore MAXDB76 backup file into Container
- 21:1721:17, 7 April 2026 diff hist +273 IBM Maximo: Migrate MAXDB to RH OpenShift →Restore MAXDB76 backup file into Container
- 20:1520:15, 7 April 2026 diff hist +44 IBM Maximo: Migrate MAXDB to RH OpenShift →Create MAXDB database
- 20:1420:14, 7 April 2026 diff hist +1,817 N IBM Maximo: Migrate MAXDB to RH OpenShift (db2ucmas76-01.yaml) 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:..." current
- 20:1420:14, 7 April 2026 diff hist +2 IBM Maximo: Migrate MAXDB to RH OpenShift →Create MAXDB database
- 20:1320:13, 7 April 2026 diff hist −1,556 IBM Maximo: Migrate MAXDB to RH OpenShift →Create MAXDB database
- 20:1220:12, 7 April 2026 diff hist +5 IBM Maximo: Migrate MAXDB to RH OpenShift →Restore MAXDB76.backup.. to Container
- 20:1020:10, 7 April 2026 diff hist +112 IBM Maximo: Migrate MAXDB to RH OpenShift →Restore MAXDB76.backup.. to Container
- 20:0920:09, 7 April 2026 diff hist −46 IBM Maximo: Migrate MAXDB to RH OpenShift →Restore MAXDB76.backup.. to Container
- 20:0920:09, 7 April 2026 diff hist −32 IBM Maximo: Migrate MAXDB to RH OpenShift →Restore MAXDB76.backup.. to Container
- 20:0820:08, 7 April 2026 diff hist +15 IBM Maximo: Migrate MAXDB to RH OpenShift →Restore MAXDB76.backup.. to Container
- 20:0520:05, 7 April 2026 diff hist +3 IBM Maximo: Migrate MAXDB to RH OpenShift →Restore MAXDB76.backup.. to Container
- 20:0420:04, 7 April 2026 diff hist +285 IBM Maximo: Migrate MAXDB to RH OpenShift →Create MAXDB database
- 20:0120:01, 7 April 2026 diff hist +27 IBM Maximo: Migrate MAXDB to RH OpenShift No edit summary
- 20:0020:00, 7 April 2026 diff hist +137 IBM Maximo: Migrate MAXDB to RH OpenShift No edit summary
- 19:5819:58, 7 April 2026 diff hist +1,793 N IBM Maximo: Migrate MAXDB to RH OpenShift 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..."
- 19:5619:56, 7 April 2026 diff hist +49 IBM Maximo →Migration to Maximo Application Suite (MAS) current
12 March 2026
- 18:5018:50, 12 March 2026 diff hist −4 IBM Sterling Connect:Direct: Configuring C:D to use AWS S3 Storage provide an AWS credentials file as a volume →Mounting the .aws Directory in Kubernetes current
- 18:4318:43, 12 March 2026 diff hist −16 IBM Sterling Connect:Direct: Configuring C:D to use AWS S3 Storage provide an AWS credentials file as a volume →Mounting the .aws Directory in Kubernetes
- 18:4018:40, 12 March 2026 diff hist +4 IBM Sterling Connect:Direct: Configuring C:D to use AWS S3 Storage provide an AWS credentials file as a volume →Example Helm Values Configuration
- 18:4018:40, 12 March 2026 diff hist −17 IBM Sterling Connect:Direct: Configuring C:D to use AWS S3 Storage provide an AWS credentials file as a volume →Example Helm Values Configuration
- 18:3918:39, 12 March 2026 diff hist −361 IBM Sterling Connect:Direct: Configuring C:D to use AWS S3 Storage provide an AWS credentials file as a volume →Summary
- 18:3818:38, 12 March 2026 diff hist −166 IBM Sterling Connect:Direct: Configuring C:D to use AWS S3 Storage provide an AWS credentials file as a volume →Using S3 in Process Files
- 18:3818:38, 12 March 2026 diff hist +258 IBM Sterling Connect:Direct: Configuring C:D to use AWS S3 Storage provide an AWS credentials file as a volume →Updating Initparm.cfg
- 18:3718:37, 12 March 2026 diff hist −38 IBM Sterling Connect:Direct: Configuring C:D to use AWS S3 Storage provide an AWS credentials file as a volume →AWS Configuration Files
- 18:3518:35, 12 March 2026 diff hist −175 IBM Sterling Connect:Direct: Configuring C:D to use AWS S3 Storage provide an AWS credentials file as a volume →AWS Configuration Files
- 18:3218:32, 12 March 2026 diff hist +24 IBM Sterling Connect:Direct: Configuring C:D to use AWS S3 Storage provide an AWS credentials file as a volume →Updating Initparm.cfg
- 18:3118:31, 12 March 2026 diff hist +3,247 N IBM Sterling Connect:Direct: Configuring C:D to use AWS S3 Storage provide an AWS credentials file as a volume 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. =..."
- 18:3018:30, 12 March 2026 diff hist +118 IBM Sterling Connect:Direct →Install, Commands and Configurations current
- 18:2618:26, 12 March 2026 diff hist −165 IBM Sterling Connect:Direct: Using extraVolume and extraVolumeMounts in IBM Connect:Direct Deployments →Sample Configuration current
- 18:2618:26, 12 March 2026 diff hist −174 IBM Sterling Connect:Direct: Using extraVolume and extraVolumeMounts in IBM Connect:Direct Deployments →Default Volume Mount Example
- 18:2518:25, 12 March 2026 diff hist −477 IBM Sterling Connect:Direct: Using extraVolume and extraVolumeMounts in IBM Connect:Direct Deployments →Purpose of `extraVolume` and `extraVolumeMounts`
- 18:2518:25, 12 March 2026 diff hist −95 IBM Sterling Connect:Direct: Using extraVolume and extraVolumeMounts in IBM Connect:Direct Deployments No edit summary
- 18:2418:24, 12 March 2026 diff hist −421 IBM Sterling Connect:Direct: Using extraVolume and extraVolumeMounts in IBM Connect:Direct Deployments →Summary
- 18:2418:24, 12 March 2026 diff hist +2,760 N IBM Sterling Connect:Direct: Using extraVolume and extraVolumeMounts in IBM Connect:Direct Deployments 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..."
- 18:2218:22, 12 March 2026 diff hist +110 IBM Sterling Connect:Direct →Install, Commands and Configurations
4 March 2026
- 16:0716:07, 4 March 2026 diff hist −33 IBM Maximo: Resizing JPEG Files in doclinks →Ver também current
- 16:0716:07, 4 March 2026 diff hist +2 IBM Maximo: Resizing JPEG Files in doclinks →Procedure
- 16:0716:07, 4 March 2026 diff hist +2 IBM Maximo: Resizing JPEG Files in doclinks →Procedure
- 16:0616:06, 4 March 2026 diff hist +10 IBM Maximo: Resizing JPEG Files in doclinks →Procedure