IBM Sterling: Configurando o MQ como Container no OpenShift: Difference between revisions
| Line 55: | Line 55: | ||
|- | |- | ||
| | | | ||
NAME: mqsterling | |||
LAST DEPLOYED: Sat May 22 18:44:13 2021 | LAST DEPLOYED: Sat May 22 18:44:13 2021 | ||
NAMESPACE: sterling-b2bi-mq | NAMESPACE: sterling-b2bi-mq | ||
| Line 64: | Line 64: | ||
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 mqsterling-ibm-mq-web -n sterling-b2bi-mq -o jsonpath="{.spec.host}") | ||
echo https://$CONSOLE_ROUTE/ibmmq/console | echo <nowiki>https://$CONSOLE_ROUTE/ibmmq/console</nowiki> | ||
The MQ connection information for clients inside the cluster is as follows: | The MQ connection information for clients inside the cluster is as follows: | ||
| Line 73: | Line 73: | ||
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) | MQ_APP_PASSWORD=$(kubectl get secret --namespace sterling-b2bi-mq mq-secret -o jsonpath="{.data.appPassword}" | base64 --decode; echo) | ||
|} | |} | ||
Revision as of 21:49, 22 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: 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 (override.yaml) referindo-se ao arquivo "values.yaml".
license: "accept"
queueManager:
name: "b2bi"
dev:
secret:
name: "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 mqsterling --namespace sterling-b2bi-mq --timeout 90m0s -f override.yaml .
|
NAME: mqsterling LAST DEPLOYED: Sat May 22 18:44:13 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 mqsterling-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: mqsterling-ibm-mq.sterling-b2bi-mq.svc:1414 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)
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)
|
Informações de Referência 3
informações do banco de dados (para serem usadas posteriormente).
- Ref 3
- dbVendor: db2