IBM Sterling: Configurando o MQ como Container no OpenShift: Difference between revisions

From Wiki
 
(10 intermediate revisions by the same user not shown)
Line 14: Line 14:
kind: Secret
kind: Secret
metadata:   
metadata:   
     name: mq-secret
     name: sterling-b2bi-mq-secret
type: Opaque
type: Opaque
stringData:   
stringData:   
Line 35: Line 35:
  cd charts/stable/ibm-mqadvanced-server-dev
  cd charts/stable/ibm-mqadvanced-server-dev


Crie o arquivo override (override.yaml) referindo-se ao arquivo "values.yaml".
Crie o arquivo '''override.yaml'''. Este arquivo sobrepõe os valores do arquivo "values.yaml".


  <nowiki>
  <nowiki>
Line 43: Line 43:
   dev:
   dev:
     secret:
     secret:
       name: "mq-secret"
       name: "sterling-b2bi-mq-secret"
       adminPasswordKey: "adminPassword"
       adminPasswordKey: "adminPassword"
       appPasswordKey: "appPassword"
       appPasswordKey: "appPassword"
Line 50: Line 50:
Instale o helm chart com o seguinte comando de "/charts/stable/ibm-mqadvanced-server-dev folder", assumindo que o arquivo "override.yaml" seja colocado na mesma pasta.
Instale o helm chart com o seguinte comando de "/charts/stable/ibm-mqadvanced-server-dev folder", assumindo que o arquivo "override.yaml" seja colocado na mesma pasta.


  helm install mqsterling --namespace sterling-b2bi-mq --timeout 90m0s -f override.yaml .
  helm install sterling-b2bi-mq --namespace sterling-b2bi-mq --timeout 90m0s -f override.yaml .


Resultado:
Resultado:


  <nowiki>NAME: mqsterling
  <small><nowiki>NAME: sterling-b2bi-mq
LAST DEPLOYED: Sat May 22 18:44:13 2021
LAST DEPLOYED: Sun May 23 08:57:02 2021
NAMESPACE: sterling-b2bi-mq
NAMESPACE: sterling-b2bi-mq
STATUS: deployed
STATUS: deployed
Line 62: Line 62:
NOTES:
NOTES:
Get the MQ Console URL by running these commands:
Get the MQ Console URL by running these commands:
   export CONSOLE_ROUTE=$(kubectl get route mqsterling-ibm-mq-web -n sterling-b2bi-mq -o jsonpath="{.spec.host}")
   export CONSOLE_ROUTE=$(kubectl get route sterling-b2bi-mq-ibm-mq-web -n sterling-b2bi-mq -o jsonpath="{.spec.host}")
   echo https://$CONSOLE_ROUTE/ibmmq/console
   echo https://$CONSOLE_ROUTE/ibmmq/console


The MQ connection information for clients inside the cluster is as follows:
The MQ connection information for clients inside the cluster is as follows:
   mqsterling-ibm-mq.sterling-b2bi-mq.svc:1414
   sterling-b2bi-mq-ibm-mq.sterling-b2bi-mq.svc:1414


To get your 'admin' user password run:
To get your 'admin' user password run:
     MQ_ADMIN_PASSWORD=$(kubectl get secret --namespace sterling-b2bi-mq mq-secret -o jsonpath="{.data.adminPassword}" | base64 --decode; echo)
     MQ_ADMIN_PASSWORD=$(kubectl get secret --namespace sterling-b2bi-mq sterling-b2bi-mq-secret -o jsonpath="{.data.adminPassword}" | base64 --decode; echo)


To get your 'app' user password run:
To get your 'app' user password run:
     MQ_APP_PASSWORD=$(kubectl get secret --namespace sterling-b2bi-mq mq-secret -o jsonpath="{.data.appPassword}" | base64 --decode; echo)</nowiki>
     MQ_APP_PASSWORD=$(kubectl get secret --namespace sterling-b2bi-mq sterling-b2bi-mq-secret -o jsonpath="{.data.appPassword}" | base64 --decode; echo)</nowiki></small>


= Informações de Referência 3 =  
= Informações de Referência 4 =  


informações do banco de dados (para serem usadas posteriormente).
:Ref 3
* dbVendor: db2


1) Obtenha detalhes do serviço para informações de conexão


oc get svc
<small>NAME                              TYPE        CLUSTER-IP      EXTERNAL-IP  PORT(S)            AGE
sterling-b2bi-mq-ibm-mq          ClusterIP  172.xx.6.39    <none>        9443/TCP,1414/TCP  92s
sterling-b2bi-mq-ibm-mq-metrics  ClusterIP  172.xx.60.239  <none>        9157/TCP            92s</small>


2) Obtenha os detalhes de conexão do MQ na interface do usuário do MQ
:Ref 4
* JMS Host : 172.xx.6.39
* JMS Port : 1414
* JMS Connection Name list : 172.xx.6.39(1414)
* JMS Channel : DEV.APP.SVRCONN
* JMS Username : app
* JMS Queue Name : DEV.QUEUE.1
* JMS Secret : sterling-b2bi-mq-secret
=CUIDADO!!! Deletando o Projeto=
Em caso de erro ou se quiser refazer o projeto, execute o comando para deletar o projeto
oc delete project sterling-b2bi-mq


= See Also =
= See Also =


* [[IBM Sterling: Deploy Sterling B2B on OpenShift at IBM Cloud]]
* [[IBM Sterling: Deploy do Sterling B2Bi no OpenShift na IBM Cloud]]


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

Latest revision as of 11:18, 24 May 2021

Procedimento

Realizando o Deploy do MQ

1) Crie um novo projeto no OpenShift para o MQ e defina contas de serviço e permissões.

oc new-project sterling-b2bi-mq

2) Crie o arquivo mq-secret.yaml para deploy do DB2 no openshift

apiVersion: v1
kind: Secret
metadata:  
    name: sterling-b2bi-mq-secret
type: Opaque
stringData:  
    adminPassword: password
    appPassword: password

3) Realize a criação da secreto

oc create -f mq-secret.yaml

4) Instalar o IBM MQ a partir do repositório IBM Github.

Clone os charts do IBM MQ do repositório Github usando o comando abaixo.

git clone https://github.com/IBM/charts.git

Isso criará um diretório chamado “charts”. Vá para a pasta "charts/stable/ibm-mqadvanced-server-dev"

cd charts/stable/ibm-mqadvanced-server-dev

Crie o arquivo override.yaml. Este arquivo sobrepõe os valores do arquivo "values.yaml".

license: "accept"
queueManager:
  name: "b2bi"
  dev:
    secret:
      name: "sterling-b2bi-mq-secret"
      adminPasswordKey: "adminPassword"
      appPasswordKey: "appPassword"

Instale o helm chart com o seguinte comando de "/charts/stable/ibm-mqadvanced-server-dev folder", assumindo que o arquivo "override.yaml" seja colocado na mesma pasta.

helm install sterling-b2bi-mq --namespace sterling-b2bi-mq --timeout 90m0s -f override.yaml .

Resultado:

NAME: sterling-b2bi-mq
LAST DEPLOYED: Sun May 23 08:57:02 2021
NAMESPACE: sterling-b2bi-mq
STATUS: deployed
REVISION: 1
TEST SUITE: None
NOTES:
Get the MQ Console URL by running these commands:
  export CONSOLE_ROUTE=$(kubectl get route sterling-b2bi-mq-ibm-mq-web -n sterling-b2bi-mq -o jsonpath="{.spec.host}")
  echo https://$CONSOLE_ROUTE/ibmmq/console

The MQ connection information for clients inside the cluster is as follows:
  sterling-b2bi-mq-ibm-mq.sterling-b2bi-mq.svc:1414

To get your 'admin' user password run:
    MQ_ADMIN_PASSWORD=$(kubectl get secret --namespace sterling-b2bi-mq sterling-b2bi-mq-secret -o jsonpath="{.data.adminPassword}" | base64 --decode; echo)

To get your 'app' user password run:
    MQ_APP_PASSWORD=$(kubectl get secret --namespace sterling-b2bi-mq sterling-b2bi-mq-secret -o jsonpath="{.data.appPassword}" | base64 --decode; echo)

Informações de Referência 4

1) Obtenha detalhes do serviço para informações de conexão

oc get svc

NAME                              TYPE        CLUSTER-IP      EXTERNAL-IP   PORT(S)             AGE
sterling-b2bi-mq-ibm-mq           ClusterIP   172.xx.6.39     <none>        9443/TCP,1414/TCP   92s
sterling-b2bi-mq-ibm-mq-metrics   ClusterIP   172.xx.60.239   <none>        9157/TCP            92s

2) Obtenha os detalhes de conexão do MQ na interface do usuário do MQ

Ref 4
  • JMS Host : 172.xx.6.39
  • JMS Port : 1414
  • JMS Connection Name list : 172.xx.6.39(1414)
  • JMS Channel : DEV.APP.SVRCONN
  • JMS Username : app
  • JMS Queue Name : DEV.QUEUE.1
  • JMS Secret : sterling-b2bi-mq-secret

CUIDADO!!! Deletando o Projeto

Em caso de erro ou se quiser refazer o projeto, execute o comando para deletar o projeto

oc delete project sterling-b2bi-mq

See Also