New pages

New pages
Hide registered users | Show bots | Show redirects
  • 01:53, 20 May 2026IBM Sterling Connect:Direct : Secure+ Sample file (hist | edit) ‎[2,031 bytes]Ebasso (talk | contribs) (Created page with " Sample spconfig.txt <nowiki> sync netmap path=/home/ajc_test/cdunix/ndm/cfg/cdu_silent/netmap.cfg name=* ; Import KeyCert File="/home/ajc_test/cd_install/cdu/silent/cdu_silent_06252025_keycert.pem" Passphrase=password Label=cdu_silent_06252025_keycert ImportMode=Add ; Import TrustedCert File="/home/ajc_test/cd_install/cdu/silent/capgemini_ajc_ecdsa_intermediate_ca.pem" Label=capgemini_ajc_ecdsa_intermediate_ca ImportMode=Add ; Upda...")
  • 01:41, 20 May 2026IBM Sterling Connect:Direct : Silent Install without provide certificates (hist | edit) ‎[1,095 bytes]Ebasso (talk | contribs) (Created page with "= Extract installer = mkdir /Binaries/CD tar -xvf 6.4.0.5-IBMSterlingConnectDirectforUNIX-Linux-x86-iFix007.tar will extract files cdinstall, cdinstall_a, cdunix. = Install = 1) Setup OS useradd -m cdadmin mkdir -p /opt/cdunix chown cdadmin:cdadmin /opt/cdunix 3) Setup silent install Create no_spconfig.txt echo "quit;"> no_spconfig.txt Create file silent_install.ini <nowiki>cdai_installCmd=install cdai_cpioFile=/Binaries/CD/cdunix cdai_installDi...")
  • 20:17, 14 May 2026IBM Sterling B2B: Configuring SSL in IBM Sterling B2B Integrator (hist | edit) ‎[1,103 bytes]Ebasso (talk | contribs) (Created page with "= Configuring IBM Sterling B2B Integrator for SSL = 1) Go to the properties directory cd /home/siuser/SI/properties 1) Edit the file '''customer_overrides.properties''' and add: noapp.HTTPS_REDIRECT_WARS=ALL noapp.SKIP_BASEPORT_DEPLOYMENT_WARS=ALL noapp.HTTPS_LIST_PORT=5001 If you also want to change the certificate: noapp.sslCert=<INTERNAL_CREATED_CERTIFICATE> Save the file. 2) Edit the file '''sandbox.cfg''' and modify: WEBAPP_LIST_PORT=5001 WEBA...")
  • 14:22, 8 May 2026IBM Maximo: Provide you customization binaries.zip on OpenShift (Apache HTTP) (hist | edit) ‎[6,060 bytes]Ebasso (talk | contribs) (Created page with "Uploading customization_binaries.zip directly to OpenShift simplifies deployment by avoiding external image builds and registries. It enables faster updates and avoid problem with security teams. = Provide customization_binaries.zip in a custom container = Start by creating a new project: oc new-project httpd-customization-binaries Create a file httpd-customization-binaries.yaml, with this content: <nowiki> --- apiVersion: v1 kind: ConfigMap metadata: name: htt...")
  • 11:52, 5 May 2026IBM Maximo: Deploying Kafka after Maximo Manage (hist | edit) ‎[2,005 bytes]Ebasso (talk | contribs) (Created page with "Kafka is an essential component of the IBM Maximo Application Suite (MAS), providing distributed messaging for applications such as IoT, Monitor, and Predict. The MAS CLI supports multiple Kafka providers, allowing flexibility in infrastructure selection. The MAS CLI supports the following providers via the --kafka-provider parameter: {| class="wikitable" |- ! Provider !! Value !! Description |- | Strimzi || strimzi || Open-source Kafka operator for Kubernetes |- | Re...")
  • 16:16, 3 May 2026Rust: Struct, (hist | edit) ‎[100 bytes]Ebasso (talk | contribs) (Created page with " struct User { username: String, email: String, sign_in_count: u64, active: bool, }")
  • 14:20, 3 May 2026IBM Maximo: Installing MAS Core + Manage + Oracle DB Container (hist | edit) ‎[2,588 bytes]Ebasso (talk | contribs) (Created page with " Run the MAS installation: <nowiki>export IBM_ENTITLEMENT_KEY=x export STORAGE_CLASS_RWO=ocs-storagecluster-cephfs export STORAGE_CLASS_RWM=ocs-storagecluster-cephfs mas install --mas-catalog-version v9-260430-amd64 --ibm-entitlement-key $IBM_ENTITLEMENT_KEY \ --mas-channel 9.1.x --mas-instance-id lab01 --mas-workspace-id ws01 --mas-workspace-name "Lab Workspace" \ --additional-configs "/mnt/home/masconfigs" \ --non-prod \ --storage-class-rwo $STORAGE_CLASS...")
  • 14:12, 3 May 2026IBM Maximo: Install MAS - Grafana task not ready (hist | edit) ‎[1,581 bytes]Ebasso (talk | contribs) (Created page with "= Problem Description = Grafana task not became in READY state Message NOTREADY on grafana task. = Root Cause = You cannot download grafana images from '''hub.docker.com.''' = Solution = === Before error happens === When grafana5 namespace was created try to run DOCKER_USERNAME='your user' DOCKER_PASSWORD='your password' DOCKER_EMAIL='your email address' oc create secret docker-registry dockerhub-pull --docker-server=https://index.docker.io/v1/ \ --docker...")
  • 19:10, 2 May 2026IBM Maximo: Creating Maximo Database on Oracle Database Free Edition (Container) (hist | edit) ‎[8,496 bytes]Ebasso (talk | contribs) (Created page with "This guide provides step-by-step instructions for deploying Oracle Database 23c Free Edition on OpenShift and creating a Maximo database with the required schema. == Overview == Oracle Database 23c Free Edition is a fully-featured Oracle Database that can be used for development, testing, and small production deployments. This guide covers: Follow the instructions, to create Oracle Database * Oracle: Run Oracle DB on Redhat OpenShift == Step 4: Create Maximo D...")
  • 16:49, 2 May 2026Oracle: Run Oracle DB on Redhat OpenShift (hist | edit) ‎[3,349 bytes]Ebasso (talk | contribs) (Created page with " = Procedure = 1) Create a new project (namespace): oc new-project oracle-db 2) Create a Service Account which you will use to run the database: oc create sa oracle-sa 3) Configure Security Context Constraint (SCC) oc adm policy add-scc-to-user anyuid -z oracle-sa Check with oc adm policy who-can use scc anyuid 4) Create a secret to store the default password for Oracle : oc create secret generic oracle-db-pass --from-literal=password=<your_password_here>...")
  • 18:03, 24 April 2026IBM Sterling Connect:Direct : C:D WebService - Annotations to Create a Network Load Balancer (NLB) service (hist | edit) ‎[1,889 bytes]Ebasso (talk | contribs) (Created page with "These annotations help tocreated on **AWS using a Network Load Balancer (NLB)**. == AWS Load Balancer Annotations == The following annotations define the Network Load Balancer behavior and configuration on AWS and must be setup the values.yaml of the Helm: <syntaxhighlight lang="yaml"> annotations: service.beta.kubernetes.io/aws-load-balancer-type: "nlb" service.beta.kubernetes.io/aws-load-balancer-nlb-target-type: "ip" service.beta.kubernetes.io/aws-load-balanc...")
  • 17:39, 23 April 2026IBM Maximo: Steps to Upgrade a Maximo 7.6 Database to MAS 9 after MAS Installation (hist | edit) ‎[4,020 bytes]Ebasso (talk | contribs) (Created page with "Update the database connection in MAS by providing the JDBC connection details for the Maximo 7.6.1.3 database, including the database credentials and certificates (if applicable). Once the information is updated, save the changes and proceed with the activation. = Procedure = 1) Stop Manage * Run managestop.sh from the maxinst pod, or * Use the Tools API as described in: : How to use the Tools API in Maximo Manage : https://www.ibm.com/support/pages/how-use-tools-ap...")
  • 17:22, 23 April 2026IBM Maximo: MAS Manage (hist | edit) ‎[2,492 bytes]Ebasso (talk | contribs) (Created page with "'''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...")
  • 19:53, 22 April 2026IBM Maximo: Disconnecting MAS Manage from the database for DB Maintenance (hist | edit) ‎[2,021 bytes]Ebasso (talk | contribs) (Created page with "In the IBM Maximo 7.6 (on‑premises) architecture, this process was straightforward: all Maximo JVMs could be stopped, providing full control over database connectivity during maintenance windows. With the introduction of MAS running on OpenShift, this approach is no longer applicable. The platform automatically manages workload pods and deployments, causing application components to restart automatically. = Procedure = == 1. Stop Maximo Manage Application == First...")
  • 20:21, 20 April 2026IBM Maximo: Changing the Database in IBM Maximo Application Suite (MAS) (hist | edit) ‎[4,505 bytes]Ebasso (talk | contribs) (Created page with "This guide explains how to change or reconfigure the database connection for IBM Maximo Application Suite (MAS) Manage application. When you need to change the database configuration for MAS Manage, you must stop all MAS Manage deployments, verify database connections are closed, and then reconfigure the JDBC connection settings. = Procedure = == 1. Stop Maximo Manage Application == First, access the Manage maxinst pod and stop the Maximo application: <syntaxhighlig...")
  • 17:50, 11 April 2026IBM Maximo: Troubleshooting - Unable to Delete a Project (Namespace) (hist | edit) ‎[1,268 bytes]Ebasso (talk | contribs) (Created page with "It is not possible to delete a project, even when using force deletion. == Check == Check what resources still exist inside the namespace. Run the following command to export the namespace definition to JSON: oc get namespace $PROJECT_NAME -o json > tmp.json && cat tmp.json Inspect the end of the generated file, especially the '''spec''' section. == Root Cause == In some cases, the deletion is blocked by a controller or operator due to a '''finalizer'''. Example...")
  • 10:38, 11 April 2026IBM Maximo: Install MAS - Image Stream Cannot Be Used as Build Output (hist | edit) ‎[4,726 bytes]Ebasso (talk | contribs) (Created page with "== Problem Description == When attempting to start a build in OpenShift, you may encounter the following error: <pre> Error starting build: an image stream cannot be used as build output because the integrated container image registry is not configured </pre> This error occurs when a BuildConfig is configured to output to an ImageStream, but OpenShift's integrated container image registry is not available. == Root Cause == The error indicates that: * The BuildConfig...")
  • 10:33, 11 April 2026IBM Maximo: Troubleshooting Maximo Manage Workspace activation (hist | edit) ‎[2,472 bytes]Ebasso (talk | contribs) (Created page with " Check manageworkspace oc describe manageworkspace -n mas-dev01-manage Result: <nowiki>Name: dev01-demo01 Namespace: mas-dev01-manage Labels: mas.ibm.com/applicationId=manage mas.ibm.com/instanceId=dev01 ...</nowiki> If From the oc describe output, the critical error is in the Status.Conditions section: Type: BuildReady Status: '''False''' Reason: '''Failed''' Message: Build Failed. Type: DeploymentCR Status: True Reason: '...")
  • 20:45, 10 April 2026IBM Maximo: Install MAS - Known installation issues (hist | edit) ‎[1,251 bytes]Ebasso (talk | contribs) (Created page with " = DRO Failure = The DRO (Data Reporter Operator) When the following happens: Wait for the rhm-data-service to be ready. Checking pods <nowiki>oc get pods -n redhat-marketplace NAME READY STATUS RESTARTS AGE ibm-data-reporter-operator-controller-manager-7dbf5f4b75-mxzpj 1/1 Running 0 159m ibm-metrics-operator-controller-manager-588c464b77-7z7bv 1/1 Running 3 (...")
  • 17:56, 10 April 2026IBM Maximo: Installing MAS Core + Manage + DB2 Container (hist | edit) ‎[1,577 bytes]Ebasso (talk | contribs) (Created page with " Run the MAS installation: mas install \ --non-prod \ --mas-instance-id dev01 \ --mas-workspace-id demo01 \ --mas-workspace-name 'eam-migration-demo01' \ --mas-catalog-version v9-260326-amd64 \ --mas-channel 9.1.x \ --manage-channel 9.1.x \ --manage-jdbc workspace-application \ --db2-manage \ --manage-components base=latest \ --license-file /mnt/home/license.dat \ --contact-email [email protected] \ --contact-firstname Enio \ --contact-lastn...")
  • 13:05, 10 April 2026IBM Maximo: Install Maximo Application Suite using MAS CLI (hist | edit) ‎[7,031 bytes]Ebasso (talk | contribs) (Created page with " = Prerequisites = == IBM Entitlement Key == Access the [https://myibm.ibm.com/products-services/containerlibrary Container Software Library] using your IBMId to obtain your entitlement key. == MAS License File == Access the [https://licensing.flexnetoperations.com/ IBM License Key Center]. From the '''Get Keys''' menu, select '''IBM AppPoint Suites''', then select '''IBM MAXIMO APPLICATION SUITE AppPOINT LIC''' and complete the form with the following information: {...")
  • 00:10, 8 April 2026IBM Maximo: Migrate MAXDB to RH OpenShift (restoresql.sql) (hist | edit) ‎[9,642 bytes]Ebasso (talk | contribs) (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...")
  • 00:02, 8 April 2026IBM Maximo: Migrate MAXDB to RH OpenShift (db2ckbkp.out) (hist | edit) ‎[1,981 bytes]Ebasso (talk | contribs) (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...")
  • 20:14, 7 April 2026IBM Maximo: Migrate MAXDB to RH OpenShift (db2ucmas76-01.yaml) (hist | edit) ‎[5,723 bytes]Ebasso (talk | contribs) (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:...")
  • 19:58, 7 April 2026IBM Maximo: Migrate MAXDB to RH OpenShift (DB2 Version) (hist | edit) ‎[3,397 bytes]Ebasso (talk | contribs) (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...") originally created as "IBM Maximo: Migrate MAXDB to RH OpenShift"
  • 18:31, 12 March 2026IBM Sterling Connect:Direct: Configuring C:D to use AWS S3 Storage provide an AWS credentials file as a volume (hist | edit) ‎[2,756 bytes]Ebasso (talk | contribs) (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:24, 12 March 2026IBM Sterling Connect:Direct: Using extraVolume and extraVolumeMounts in IBM Connect:Direct Deployments (hist | edit) ‎[1,428 bytes]Ebasso (talk | contribs) (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...")
  • 16:06, 4 March 2026IBM Maximo: Resizing JPEG Files in doclinks (hist | edit) ‎[731 bytes]Ebasso (talk | contribs) (Created page with "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 dnf install -y ImageMagick </pre> 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...")
  • 21:58, 19 February 2026IBM MQ: Usando Aplicações Cliente (hist | edit) ‎[1,580 bytes]Ebasso (talk | contribs) (Created page with "== Testando a Conexão == Connect to container <syntaxhighlight lang="bash"> podman exec -it ibm-mq bash </syntaxhighlight> === Verificar Status do Queue Manager === <syntaxhighlight lang="bash"> dspmq </syntaxhighlight> === Usando Programas de Exemplo do MQ === '''Enviar uma mensagem:''' <syntaxhighlight lang="bash"> /opt/mqm/samp/bin/amqsput DEV.QUEUE.1 QM1 </syntaxhighlight> Digite a mensagem e pressione Enter duas vezes. '''Receber uma mensagem:''' <syn...")
  • 19:23, 19 February 2026IBM MQ: Principais Conceitos do IBM MQ (hist | edit) ‎[10,315 bytes]Ebasso (talk | contribs) (Created page with "= Principais Conceitos do IBM MQ = == Messages (Mensagens) == '''Messages''' são unidades de dados que são transmitidas entre aplicações através do IBM MQ. Uma mensagem consiste em: * '''Message Descriptor (Descritor de Mensagem)''': Contém informações de controle e metadados sobre a mensagem, como: ** Message ID (identificador único) ** Correlation ID (para correlacionar respostas) ** Priority (prioridade) ** Persistence (se a mensagem deve ser persistida em...")
  • 19:07, 19 February 2026IBM CloudPak for Integration (hist | edit) ‎[90 bytes]Ebasso (talk | contribs) (Created page with "= Veja também= Category:IBM CP4I Category:IBM Automation Category:Middleware")
  • 19:07, 19 February 2026IBM App Connect (hist | edit) ‎[97 bytes]Ebasso (talk | contribs) (Created page with "= Veja também= Category:IBM App Connect Category:IBM Automation Category:Middleware")
  • 19:06, 19 February 2026IBM API Connect (hist | edit) ‎[97 bytes]Ebasso (talk | contribs) (Created page with "= Veja também= Category:IBM API Connect Category:IBM Automation Category:Middleware")
  • 19:03, 19 February 2026IBM MQ (hist | edit) ‎[440 bytes]Ebasso (talk | contribs) (Created page with " * IBM MQ: Deploy do IBM MQ como container == Comandos MQ Úteis == IBM MQ: Comandos MQ Úteis == Considerações de Segurança == IBM MQ: Consideracoes de Seguranca = Veja também= Category:IBM MQ Category:Podman Category:Containers Category:Middleware")
  • 18:58, 19 February 2026IBM MQ: Comandos MQ Úteis (hist | edit) ‎[798 bytes]Ebasso (talk | contribs) (Created page with "== Comandos MQ Úteis == IBM MQ: Comandos MQ Úteis === Listar Filas === <syntaxhighlight lang="bash"> podman exec ibm-mq runmqsc QM1 <<EOF DISPLAY QUEUE(*) EOF </syntaxhighlight> === Criar uma Fila === <syntaxhighlight lang="bash"> podman exec ibm-mq runmqsc QM1 <<EOF DEFINE QLOCAL(MINHA.FILA) EOF </syntaxhighlight> === Verificar Profundidade da Fila === <syntaxhighlight lang="bash"> podman exec ibm-mq runmqsc QM1 <<EOF DISPLAY QLOCAL(DEV.QUEUE.1) CURDEPTH EO...")
  • 18:56, 19 February 2026IBM MQ: Consideracoes de Seguranca (hist | edit) ‎[1,010 bytes]Ebasso (talk | contribs) (Created page with " As senhas padrão (<code>passw0rd</code>) devem ser alteradas imediatamente em ambientes de produção. === Alterando Senhas === <syntaxhighlight lang="bash"> # Acessar o container podman exec -it ibm-mq bash # Alterar senha do usuário admin mqsichangepassword admin # Alterar senha do usuário app mqsichangepassword app </syntaxhighlight> === Usando Secrets do Podman === <syntaxhighlight lang="bash"> # Criar secrets echo "senha-segura-admin" | podman secret crea...")
  • 17:52, 19 February 2026IBM MQ: Deploy do IBM MQ como container (hist | edit) ‎[3,447 bytes]Ebasso (talk | contribs) (Created page with " = IBM MQ Deployment com Podman = Este guia fornece instruções completas para implantar IBM MQ usando Podman. == Pré-requisitos == * Podman instalado no sistema * Espaço em disco suficiente (mínimo 2GB) * Portas 1414 e 9443 disponíveis == Instalação Rápida == === Passo 1: Criar Diretórios === <syntaxhighlight lang="bash"> mkdir -p ./mq-data mkdir -p ./mq-config mkdir -p ./mq-logs </syntaxhighlight> === Passo 2: Baixar a Imagem IBM MQ === <syntaxhighlig...")