ot4i / ace-docker Goto Github PK

Hi,

Checking the instructions provided to create an image with ACE and the MQ Client, the value for BASE_IMAGE is not supplied leading to some confusion. Instead it should have a reference, as the other Build commands to something like {ACE-only-image}. This should help to improve the documentation.

Best regards... Joel

Im deployed the bar application on ace-server and trying to start msgflow with MQ Nodes,
but generate this exception:

2018-09-18 15:22:46.859400: [Thread 24] (Msg 1/2) BIP9320E: Message Flow 'test', 'test' encountered a failure and could not start.
2018-09-18 15:22:46.859464: [Thread 24] (Msg 2/2) BIP2684E: A component was configured to use WebSphere MQ, but the required MQ libraries are not available.
--

How can I configure these MQ libraries to start the msgflow of my application?

Hi Team,

Integration server is throwing "Port bind" issue while trying to start the resource. Here's what I noticed in container logs.

I deleted all the resource and redeployed just the simplyUICard resource mentioned in error logs but still getting the same message. How can I find out the flow which is still using the port 7800 in the container ?

Container Logs
Deploying . . .
2018-09-27 20:17:01.847773: Configuration message received.
2018-09-27 20:17:01.872262: About to 'Initialize' the deployed resource 'simplyUICard' of type 'RestAPI'.
2018-09-27 20:17:01.946880: About to 'Start' the deployed resource 'simplyUICard' of type 'RestAPI'.
registerNativeHTTPNode(): could not bind to port 7800
2018-09-27 20:17:01.953031: Deployed resource 'gen.simplyUICard' (uuid='gen.simplyUICard',type='.MSGFLOW') successfully stopped.
2018-09-27 20:17:01.953196: Message Flow 'gen.simplyUICard', 'gen.simplyUICard' encountered a failure and could not start.
2018-09-27 20:17:01.953253: An error has occurred during HTTP listener startup: the specified TCPIP port (7800) is already in use.
2018-09-27 20:17:01.953606: About to 'Initialize' the deployed resource 'simplyUICard' of type 'RestAPI'.
2018-09-27 20:17:01.953711: About to 'Start' the deployed resource 'simplyUICard' of type 'RestAPI'.
2018-09-27 20:17:01.953772: The integration node successfully processed the deployment request.
2018-09-27 20:17:01.953868: Integration server finished with Configuration message.

I am trying to build am image for ACE RHEL using below command

RedHat Enterprise Linux: ./build-rhel.sh ace-dev-only {buildTag} {ACE-file-in-deps-folder}
I am getting below error when its trying to add aceuser in /etc/sudoers . I am running as a root user and have read permission to file /etc/sudoers.

does anyone has seen this kind of error. need help to resolve this issue.

Step 13/20 : RUN useradd -d /home/aceuser -G mqbrkrs,wheel aceuser && sed -e 's/^%root ./%root ALL=NOPASSWD:ALL/g' -i ../../etc/sudoers && su - aceuser -c '. /opt/ibm/ace-11/server/bin/mqsiprofile && mqsicreateworkdir /home/aceuser/ace-server' && chmod 755 /usr/local/bin/
---> Running in 92d7aee1f971
sed: can't read ../../etc/sudoers: No such file or directory
The command '/bin/sh -c useradd -d /home/aceuser -G mqbrkrs,wheel aceuser && sed -e 's/^%root ./%root ALL=NOPASSWD:ALL/g' -i ../../etc/sudoers && su - aceuser -c '. /opt/ibm/ace-11/server/bin/mqsiprofile && mqsicreateworkdir /home/aceuser/ace-server' && chmod 755 /usr/local/bin/' returned a non-zero code: 2

Hi,
When aceonly image is pulled from openshift using the below command, resulting in a segment violation error,

"oc new-app ibmcom/ace --env LICENSE=accept --env ACE_SERVER_NAME=acetest --env LOG_FORMAT=json"

github.com/ot4i/ace-docker/internal/*logger.(Logger).Debugf(0x0, 0x8ea462, 0x1f, 0xc4200b7d90, 0x1, 0x1)

  | /go/src/github.com/ot4i/ace-docker/internal/logger/logger.go:134 +0x26
  | main.logTermination(0xc4201f00e0, 0x1, 0x1)
  | /go/src/github.com/ot4i/ace-docker/cmd/runaceserver/logging.go:36 +0x16e
  | main.doMain(0xc4200b7f78, 0xc4200de058)
  | /go/src/github.com/ot4i/ace-docker/cmd/runaceserver/main.go:38 +0x11b
  | main.main()
  | /go/src/github.com/ot4i/ace-docker/cmd/runaceserver/main.go:147 +0x22

A nil pointer reference is being passed to 'Debugf' function.

Hello,

I am building ace-mq container on RHEL but i see in the latest update , rhel related docker files are missing. Could you please let me know when those will be added.

And I see ACE and MQ images are mostly using Ubuntu as base image, does this mean, RHEL is not supported for these things?

The rhel/Dockerfile.acerhel and rhel/Dockerfile.acemqrhel files have an instruction around line 30 that copies the file LICENSE to /licenses/licensing.txt. The LICENSE is however not present in the repository, so this instruction causes the build to fail. Can you please add the proper LICENSE file?

Hi there,
ACE image is working fine in local docker engine but throwing below error when uploaded into Openshift? Can you please guide how can I resolve this issue?

1. Openshift Admin team is not allowing us to modify the SCC
2. Openshift is triggering Image with non root user

panic: runtime error: invalid memory address or nil pointer dereference

  | [signal SIGSEGV: segmentation violation code=0x1 addr=0x18 pc=0x6af5b6]
  |  
  | goroutine 1 [running]:
  | github.com/ot4i/ace-docker/internal/logger.(*Logger).Debugf(0x0, 0x8ea498, 0x1f, 0xc4200edd90, 0x1, 0x1)
  | /go/src/github.com/ot4i/ace-docker/internal/logger/logger.go:134 +0x26
  | main.logTermination(0xc4200d60f0, 0x1, 0x1)
  | /go/src/github.com/ot4i/ace-docker/cmd/runaceserver/logging.go:36 +0x16e
  | main.doMain(0xc4200edf78, 0xc42010c058)
  | /go/src/github.com/ot4i/ace-docker/cmd/runaceserver/main.go:38 +0x11b
  | main.main()
  | /go/src/github.com/ot4i/ace-docker/cmd/runaceserver/main.go:147 +0x22

Hi Team,

Please help us by providing the RHEL script for Ace with MQ client, currently we have the one for ubuntu.

We tried to run the ubuntu script but getting file or directory not found error.
Base ace image is a rhel image which is working in openshift environment
Script used :
docker build -t acewithmqclient:latest --build-arg BASE_IMAGE=acewithmqclient:latest -f /home/centos/ace-docker-master/ubuntu/Dockerfile.acemqclient /home/centos/ace-docker-master/ubuntu/
Error
COPY failed: stat /var/lib/docker/tmp/docker-builder032326740/home/centos/ace-docker-master/ubuntu/installMQClient.sh: no such file or directory

Thanks
Ajitesh

Hi,

i'm trying to set up a Salesforce Security Identity with ace -docker. The problem is that Salesforse want's several identifiers and at the moment you provide just -u -p . Can you be so kind add few additional identifiers?

Example:
salesforce::SecurityIdentity -u $USER -p $PASSWORD -c $CLIENT_ID -s $CLIENT_SECRET

mqsisetdbparms ${ACE_SERVER_NAME} -n -u -p
resource1 user1 password1
resource2 user2 password2

Hello
I have dynamically configure the ACE Integration Server.
If I am using --detach option with docker run command there is no issue but if I am using docker run command without --detach option, there is a continuous line of message that is "Integration server not ready yet" appearing but the server working fine

yamlFileInTxtFormat.txt

I have changed the HTTPConnector ListenerPort into 8888 and RestAdminListener port into 7777 at the server.conf.yaml file.

Is this a problem?

Please find the server.conf.yaml file in txt format (as yaml format is unsupported in github) and screenshots of the issue are attached.

We are getting below error when building ace-only container from Linux 64 image on MacBook Kindly help -

Command - ./build-rhel.sh ace-only ace11 11.0.0.3-ACE-LINUX64-DEVELOP.tar.gz

Error -

Step 20/39 : RUN tar xzf $ACE_INSTALL --exclude ace-11.*/tools --strip-components 1 --directory /opt/ibm/ace-11
---> Running in 07bbc5d333ab
tar: server/nodejs/lib/node_modules/ace-admin-server/node_modules/nyc/node_modules/.bin: Directory renamed before its status could be extracted
tar: server/nodejs/lib/node_modules/ace-admin-server/node_modules/nyc/node_modules: Directory renamed before its status could be extracted
tar: server/nodejs/lib/node_modules/ace-admin-server/node_modules/nyc: Directory renamed before its status could be extracted
tar: server/nodejs/lib/node_modules/ace-admin-server/node_modules/stryker-javascript-mutator/node_modules/.bin: Directory renamed before its status could be extracted
tar: server/nodejs/lib/node_modules/ace-admin-server/node_modules/stryker-javascript-mutator/node_modules: Directory renamed before its status could be extracted
tar: server/nodejs/lib/node_modules/ace-admin-server/node_modules/stryker-javascript-mutator: Directory renamed before its status could be extracted
tar: server/nodejs/lib/node_modules/ace-admin-server/node_modules/.bin: Directory renamed before its status could be extracted
tar: server/nodejs/lib/node_modules/ace-admin-server/node_modules/eslint/node_modules/.bin: Directory renamed before its status could be extracted
tar: server/nodejs/lib/node_modules/ace-admin-server/node_modules/eslint/node_modules: Directory renamed before its status could be extracted
tar: server/nodejs/lib/node_modules/ace-admin-server/node_modules/eslint: Directory renamed before its status could be extracted
tar: Exiting with failure status due to previous errors
The command '/bin/sh -c tar xzf $ACE_INSTALL --exclude ace-11.*/tools --strip-components 1 --directory /opt/ibm/ace-11' returned a non-zero code: 2
C02WGAHVHTD

I can't install it using the Windows Installation, any guidance if this feature would be available soon?

My docker build (ising windows 10 docker environment) failed at the extraction of the ace file with:
tar: server/nodejs/lib/node_modules/ace-admin-server/node_modules/escodegen/node_modules/.bin: Directory renamed before its status could be extracted

I could get it running by adding --absolute-names to the tar command

J.

Hi,

I have set ODBCINI , ODBCSYSINI and LIBPATH environment variables during container creation in k8s cluster envand these values are set when container is created. But when I run . mqsiprofile in bin folder, the ODBCSYSINI value is getting overridden , and there are DB connection issues.
ODBCSYSINI is changing to ODBCSYSINI=/opt/ibm/ace-11/ie02/etc.

I get the below error when I run mqsicvp command.

BIP8290I: Verification passed for the ODBC environment.

BIP2393E: Database error: ODBC return code '-1' from data source ''DSN_MULEDB'' using ODBC driver manager ''/opt/ibm/ace-11/ie02/lib/libodbcinterface.so''.

Can you please check and let me know why the odbcsysini environment variable is being overwritten when I run mqsiprofile ?

Container_Startup_ENV.txt
error_log.txt
mqsicvp_error.txt
mqsiprofile_ENV.txt

I successfully built the ACE production (v.11.0.0.4) only image using Ubuntu as the OS, so I've the ace-only image in docker. However, when I tried to build the sample based on the ACE only image, I got ACE's exceptions as shown below. In the "sample/Dockerfile.aceonly" it has the following command. I don't recall the "bars" folder is actually created in the ace-only image. Could this be the problem?

COPY bars_aceonly /home/aceuser/bars

[docker@reg2lxap0034 sample]$ docker build -t aceapp --file Dockerfile.aceonly .
Sending build context to Docker daemon 175.6kB
Step 1/3 : FROM ace-only:latest
---> 97832429ecaf
Step 2/3 : COPY bars_aceonly /home/aceuser/bars
---> 345f1e4b7af9
Step 3/3 : RUN ace_compile_bars.sh
---> Running in b9ee6955e322
BIP2114E: IBM App Connect Enterprise internal error: diagnostic information ''Failed to read ZIP file - could not navigate to first file'', ''/home/aceuser/bars/CallHTTPSEcho.bar'', '1208', '-102'.
An internal software error has occurred in IBM App Connect Enterprise. Further messages may indicate the effect of this error on the component.
Shutdown and restart the component. If the problem continues to occur, then restart the system. If the problem still continues to occur contact your IBM support center.

BIP8081E: An error occurred while processing the command.
An error occurred while the command was running; the command has cleaned up and ended.
Use messages prior to this one to determine the cause of the error.
Check for some common problems:
Does the user id have the correct authorities (for example a member of the mqbrkrs group)?
Is any operating system limit set too low to allow the command to run?
Is the environment correctly set up?
Correct the problem and retry the command, otherwise, contact your IBM support center.
BIP2114E: IBM App Connect Enterprise internal error: diagnostic information ''Failed to read ZIP file - could not navigate to first file'', ''/home/aceuser/bars/HTTPSEcho.bar'', '1208', '-102'.
An internal software error has occurred in IBM App Connect Enterprise. Further messages may indicate the effect of this error on the component.
Shutdown and restart the component. If the problem continues to occur, then restart the system. If the problem still continues to occur contact your IBM support center.

BIP8081E: An error occurred while processing the command.
An error occurred while the command was running; the command has cleaned up and ended.
Use messages prior to this one to determine the cause of the error.
Check for some common problems:
Does the user id have the correct authorities (for example a member of the mqbrkrs group)?
Is any operating system limit set too low to allow the command to run?
Is the environment correctly set up?
Correct the problem and retry the command, otherwise, contact your IBM support center.
The command '/bin/sh -c ace_compile_bars.sh' returned a non-zero code: 81

Hi There,
I am trying to build a ace-mq container but confused with 4th parameter, what should I pass in {MQ_Base_Image_Name}

I am running below command which is keep failing....

./build-rhel.sh ace-mq ace11 11.0.0.4-ACE-LINUX64-DEVELOP.tar.gz ibmcom/ace-mq

Hi,

There is an issue in ace_config_odbcini.sh. Please add space after
[ -s "/home/aceuser/initial-config/odbcini/odbc.ini**"]**; then

I have added this space in my build and then mounted the initial config odbc.ini and setdbparms files. odbc.ini is copied to /home/aceuser/ace-server. But I do not think export variables and setdbparms is not running after container starts to point to these new files.

When I run mqsicvp command , below error is thrown.

BIP8295E: ODBC environment variables have not been set, or are invalid.
The integration node cannot verify user data sources because the ODBCINI, ODBCSYSINI, or IE02_PATH environment variables are not set, or because the ODBCINI environment variable is set incorrectly.
Ensure that the ODBCINI environment variable is set, and see earlier warning messages for further details.

Can you please let me know if I can set these new ODBC values passed in initialconfig files odbcini and setdmparams.txt and export these variables after container starts. Do I need to make modification in any of the build scripts.

I did not find instructions for RHEL image for ACE + MQ Client, can you please share if we have.

Trying to import sample kibana dashboard, resulted in following error.

I am running ACE + MQ in OpenShift. and mounting to dir "/home/aceuser" and "/home/aceuser/initial-config". also placing server-config.ymal file in initial-config dir.

When i am restarting my pod its not coming up. am getting below error.

2019-06-13T16:54:58.449Z Integration server not ready yet
IBM App Connect Enterprise v11004 (integration_server.ace) [Thread 561] (Msg 1/1) BIP2229W: Warning: abend file directory (/home/aceuser/ace-server/config/common/errors) open failed: errno 2. Using directory /tmp 0
IBM App Connect Enterprise v11004 (integration_server.ace) [Thread 561] (Msg 1/1) BIP2229W: Warning: abend file directory (/home/aceuser/ace-server/config/common/errors) open failed: errno 2. Using directory /tmp 0
Failed to open file /home/aceuser/ace-server/config/common/log/integration_server.ace.trace.0.txt with error No such file or directory
Caught unhandled exception in main: BIP2112E: IBM App Connect Enterprise internal error: diagnostic information ''No such file or directory'', '2'. : /jenkins/workspace/S000_Ubuntu_Linux_Build_And_Test/product-build/WMB/src/CommonServices/Unix/ImbFile.cpp: 452: ImbFile::getSize: :
2019-06-13T16:55:03.453Z Integration server not ready yet

When I attempt to build the demo image using the already build ACE 11.0.0.0 base image I gate this error

---> Running in 25e067302822
Removing intermediate container 25e067302822
---> 1225ce2093ae
Step 3/5 : COPY $BAR1 /tmp
---> 002047fa0108
Step 4/5 : RUN bash -c ‘mqsibar -w /home/aceuser/ace-server -a /tmp/$BAR1 -c’
---> Running in 06a55cabc4e0
Sourcing profile
-w: $'\342\200\230mqsibar': command not found
The command '/bin/sh -c bash -c ‘mqsibar -w /home/aceuser/ace-server -a /tmp/$BAR1 -c’' returned a non-zero code: 127

Hi Team,
we built the new image by using the shell script available at Docker Hub (provided by IBM) and the IBM ACE tar (downloaded from IBM official passport portal) on RHEL server (v7)with the required accesses. The built image is getting deployed successfully and working fine with docker on local machine and the RHEL server(where image was built). However when we tried to deploy the same image on OpenShift, we are getting the below error. We discussed about this issue with OpenShift folks and they suggested us to follow the IBM documentation to deploy the image on OpenShift. Does IBM have any documentation to deploy the built ACE image on OpenShift ?
RHEL version was 7.6 on the server in which we built the image.
openshift repository(Quay) the image passed with zero Vulnerabilities, from where we deployed the image.
Rhel tar used from passport :-IBM_ACE_11.0.0.4_LNX_X8664_INCTKT.tar
RHEL specific scripts were used to built the image.
https://github.com/ot4i/ace-docker/blob/master/rhel/Dockerfile.acerhel
Log :-
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x18 pc=0x6af5b6]

goroutine 1 [running]:
github.com/ot4i/ace-docker/internal/logger.(*Logger).Debugf(0x0, 0x8ea498, 0x1f, 0xc42006dd90, 0x1, 0x1)
/go/src/github.com/ot4i/ace-docker/internal/logger/logger.go:134 +0x26
main.logTermination(0xc42009d090, 0x1, 0x1)
/go/src/github.com/ot4i/ace-docker/cmd/runaceserver/logging.go:36 +0x16e
main.doMain(0xc42006df78, 0xc4200341d8)
/go/src/github.com/ot4i/ace-docker/cmd/runaceserver/main.go:38 +0x11b
main.main()
/go/src/github.com/ot4i/ace-docker/cmd/runaceserver/main.go:147 +0x22

I am trying to build ACE-MQ RHEL image which is asking RHEL MQ image as input (which I have build with https://github.com/ibm-messaging/mq-container instructions). The ACE-MQ build script is failing with below error -

Step 11/31 : RUN yum update -y &&      yum upgrade -y &&      yum install -y sudo openssl -y &&          yum -y clean all &&      rm -rf /var/lib/apt/lists/* /var/cache/yum
 ---> Running in e2f887b4d1cc

Loaded plugins: ovl, product-id, search-disabled-repos, subscription-manager
This system is not registered with an entitlement server. You can use subscription-manager to register.
There are no enabled repos.
 Run "yum repolist all" to see the repos you have.
 To enable Red Hat Subscription Management repositories:
     subscription-manager repos --enable <repo>
 To enable custom repositories:
     yum-config-manager --enable <repo>

Hi,
just wondering about the dynamic configuration:

• what is the idea: map an external volume to /home/aceuser/initial-config
  or
• copy configuration data at docker build time into the image ?

Thanks
Joerg

Hi Team,
ACE-only Docker Image build is failing with below error -

`
Step 3/21 : LABEL summary "$SUMMARY" description "$DESCRIPTION" io.k8s.description "$DESCRIPTION" io.k8s.display-name "Integration Server for App Connect Enterprise on ICP" io.openshift.tags "$PRODNAME,$COMPNAME" com.redhat.component "$PRODNAME-$COMPNAME" name "$PRODNAME/$COMPNAME" vendor "IBM" version "11.0.0.3" release "1" license "IBM" maintainer "Hybrid Integration Platform Cloud" io.openshift.expose-services "" usage ""
---> Running in f34e7cd24931
---> 85930d72539d
Removing intermediate container f34e7cd24931
Step 4/21 : RUN mkdir /licenses
---> Running in 86182c076266

mkdir: cannot create directory '/licenses': Permission denied
The command '/bin/sh -c mkdir /licenses' returned a non-zero code: 1

`
Please help

After I built the ACE production only v11.0.0.5 with ubi and then with the MQ Client, I noticed that the "/var/mqm" folder was instructed to be removed in the "ubi/install-mq.sh". This doesn't allow me to edit the "/var/mqm/mqclient.ini" file to create a CertificateLabel. And I wasn't able to run the "dspmqver" command to confirm the installation. I commented out that line in the script and rebuilt the image. I'm just wondering if the removal of the "/var/mqm" folder was done intentionally or not.

What would be the good way to override bar file with respect to images. Should we override the barfile (for various environments) before/outside the image? or Add bar override as one of the step within the image?

In the "/home/aceuser/initial-config/setdbparms/setdbparms.txt" file, I've a line as shown below, and the ace_config_setdbparms.sh splited the line into 'myresource', '"dummy', and 'test"'.

myresource "dummy test" password

https://github.com/ot4i/ace-docker/blob/998b617463ad8d37b3174179598d519c71c6bef5/ace_config_setdbparms.sh#L29

So, I also tried to run the ace_mqsicommand.sh inside the docker container and I got the following exception

BIP8038E: An invalid combination of options was selected. The command specified represents an invalid combination of options and parameters. Refer to the IBM App Connect Enterprise online documentation for the list of valid options for this command. Correct and reissue the command.

I think the "mqsi$*" might need to be changed to "mqsi$@" to handle space chars inside a quote.

https://github.com/ot4i/ace-docker/blob/998b617463ad8d37b3174179598d519c71c6bef5/ace_mqsicommand.sh#L14

In order to fix this issue temporarily, I had to issue the ". /opt/ibm/ace-11/server/bin/mqsiprofile", and then ran the "mqsisetdbparms" command directly.

Hi,

I am running ACE 11.0.0.4 in openshift and I am trying to configure database. I have placed odbc.ini file in sample/initial-config/odbcini/ and setdbparams file in sample/initial-config/setdbparms/ folder . and build an app image. Now where should i place the fiels in server and how it will configure the DB connection in container. Need some clarity on same.If we have any detail step how to configure DB it will be very helpful.

Hi,
I'm trying to pull the newest ACE image with "docker pull ibmcom/ace:11.0.0.5", but it gives me the "Error response from daemon: manifest for ibmcom/ace:11.0.0.5 not found" error.

I have pulled the ibmcom/ace:latest but it would nice to use the actual version tag to keep up with the versions.

Thank you!

When I logged in to the bash console as the default "aceuser", the following first line was displayed.

To run a command as administrator (user "root"), use "sudo ".

However, when I tried to run "sudo su - mqm", I got the following exception:

sudo: effective uid is not 0, is /usr/bin/sudo on a file system with the 'nosuid' option set or an NFS file system without root privileges?

Any ideas why I can't run the sudo command?

Hi,

i tried to insert the salesforce credentials, but got an error. (See error log below)
Do you have any solution for that?

mqsisetdbparms -w /home/aceuser/ace-server -n salesforce::SecurityIdentity -u myUsername -p myPassword -c myClientID -s myClientSecret

2019-07-15T12:34:50.841Z Stopping Integration Server 2019-07-15T12:34:50.841Z Integration Server stopped 2019-07-15T12:34:50.841Z Stopping Queue Mgr 2019-07-15T12:34:50.841Z Queue Mgr stopped 2019-07-15T12:34:50.841Z Shutdown complete 2019-07-15T12:35:00.649Z Image created: 2019-06-28T14:32:45+00:00 2019-07-15T12:35:00.650Z Image revision: Not specified 2019-07-15T12:35:00.650Z Image source: Not specified 2019-07-15T12:35:00.747Z ACE version: 11005 2019-07-15T12:35:00.747Z ACE level: S000-L190627.15920 2019-07-15T12:35:00.747Z ACE build type: Production, 64 bit, amd64_linux_2 2019-07-15T12:35:00.747Z Checking for valid working directory 2019-07-15T12:35:00.747Z Checking if work dir is already initialized 2019-07-15T12:35:00.747Z Checking for contents in the work dir 2019-07-15T12:35:00.747Z Work dir initialization complete 2019-07-15T12:35:00.747Z Performing initial configuration of integration server 2019-07-15T12:35:00.747Z No content server url available 2019-07-15T12:35:00.747Z Processing configuration in folder setdbparms 2019-07-15T12:35:00.758Z+00:00 Handling setdbparms configuration 2019-07-15T12:35:00.761Z+00:00 **Setting user and password for resource mqsisetdbparms** 2019-07-15T12:35:00.839Z Error processing configuration in folder setdbparms: /usr/local/bin/ace_config_setdbparms.sh: exit status 5: BIP8129W: Sets the credentials of resources that are associated with an integration node. Syntax (1): mqsisetdbparms [<integrationNodeName> | -w <work-dir>] -n <resource> [-u <userId>] [-p <password>] [-f] Syntax (2): mqsisetdbparms [<integrationNodeName> | -w <work-dir>] -n <resource> -d [-f] Syntax (3): mqsisetdbparms [<integrationNodeName> | -w <work-dir>] -n <resource> [-u <userId>] [-i <ssh_identiy>] [-r <passphrase>] [-f] Syntax (4): mqsisetdbparms [<integrationNodeName> | -w <work-dir>] -n <resource> [-u <userId>] [-p <password>] [-c <client identity>] [-s <client secret>] [-f] Syntax (5): mqsisetdbparms [<integrationNodeName> | -w <work-dir>] -n <resource> [-u <userId>] [-p <password>] [-k <API key>] [-f] Command options, syntax (1): <integrationNodeName> The integration node name. -w <work-dir> The work directory of an integration server -n <resource> The type and name of the resource with which the <userId> and <password> are associated. -u <userId> The user identifier associated with <resource>. If the resource already exists and a user ID is associated with the resource, you do not need to set this parameter. If the resource does not already exist, you must set this parameter. -p <password> The password associated with <resource>. You must set the <userId> and <password>. Command options, syntax (2) <integrationNodeName> The integration node name. -w <work-dir> The work directory of an integration server -n <resource> The type and name of the resource with which the <userId> and <password> are associated. -d Deletes the <resource>, <userId>, and <password> information. Command options, syntax (3): <integrationNodeName> The integration node name. -w <work-dir> The work directory of an integration server -n <resource> The type and name of the resource with which the <userId> and <ssh_identity> are associated. -u <userId> The user identifier associated with <resource>. If the resource already exists and a user ID is associated with the resource, you do not need to set this parameter. If the resource does not already exist, you must set this parameter. -i <ssh_identity> The fully qualified path to the SSH identity associated with <resource>. You must set the <userId> and <ssh_identity>. -r <passphrase> The passphrase associated with <ssh_identity>. The passphrase is optional. Command options, syntax (4): <integrationNodeName> The integration node name. -w <work-dir> The work directory of an integration server -n <resource> The type and name of the resource with which the <userId> and <password> are associated. -u <userId> The user identifier associated with <resource>. If the resource already exists and a user ID is associated with the resource, you do not need to set this parameter. If the resource does not already exist, you must set this parameter. -p <password> The password associated with <resource>. You must set the <userId> and <password>. -c <client identity> The client identity associated with <resource>. -s <client secret> The client secret associated with <resource>. Command options, syntax (5): <integrationNodeName> The integration node name. -w <work-dir> The work directory of an integration server -n <resource> The type and name of the resource with which the <userId>, <password>, and <API key> are associated. You must specify a user ID, an API key, or a user ID and an API key. If you specify a user ID, you must also specify a password. You can specify a password without a user ID if the resource already exists and a user ID is already associated with the resource. -u <userId> The user identifier associated with <resource>. -p <password> The password associated with <resource>. -k <API key> The API key associated with <resource>. The resource can be one of the following types. Each type is determined by the syntax of the <resource> parameter: -n odbc::<Data Source Name>[::<integration server name>] The ODBC Data Source Name, with optional integration server name -n ftp::<security identity> The FTP server security identity specified on File nodes. -n jms::<JMS connection factory name> The JMS ConnectionFactory used by a JMS node. -n jndi::<JNDI administered object name> The JNDI name associated with a JMS ConnectionFactory or Destination. -n jdbc::<security identity> The JDBC security identity. -n <data source name> The Data Source Name (DNS) that is used in Compute, Mapping, or Database nodes. -n mq::<security identity> The IBM MQ security identity used to connect to a secured queue manager from MQ nodes. -n mqtt::<security identity> The MQTT security identity used to connect to a secured MQTT server. -n eis::<adapter name> The adapter name used by the WebSphere Adapters nodes. -n email::<security identity> User identity for the EmailInput node or EmailServer policy. -n ims::<security identity> The IMS Connect security identity specified on an IMS node. -n cics::<security_identity> The CICS security identity specified on a CICSRequest node. -n sftp::<security_identity> The SFTP security identity used on a File node. -n cd::<security_identity> The Connect:Direct security identity used on the CD nodes. cd::default is the default security identity used by the nodes. -n wxs::<security_identity> The WebSphere eXtreme Scale security identity used by the WebSphere eXtreme Scale policy. -n brokerKeystore::password The keystore password used by the integration node. -n brokerTruststore::password The truststore password used by the integration node. -n brokerTruststore::keypass::encKey The private key password used by the integration node. -n httpproxy::HTTPPROXY or -n httpproxy::<proxy server> The HTTP proxy security credentials used for request nodes, connectors and services in the integration node. -n salesforce::<security identity> The Salesforce server security identity specified on a Salesforce node. -n loopback::<security identity> The LoopBack connector security identity specified on a LoopBackRequest node. -n rest::<security identity> The REST security identity specified on a REST request node. -n kafka::KAFKA::<server name> The Kafka security identity used for Kafka nodes deployed to an Integration server. When using this command with an integration node name, by default it processes with the integration node running, but the operational changes do not take effect until the integration server, or servers, using the <resource> are restarted. Use the -f option to force a check that the integration node <integrationNodeName> is stopped before this command is allowed to run, thereby ensuring that the changes take effect for all integration servers as soon as the integration node is next started. However, using this option means that the integration node has to be stopped before this command can be run. When using this command with an integration server work directory, the -f option can not be used. BIP8005E: Flag or argument 'user' missing. The command will result in no action being taken, a required flag or a flag's argument is missing. Correct and reissue the command. 2019-07-15T12:35:00.839Z [/usr/local/bin/ace_config_setdbparms.sh: exit status 5: BIP8129W: Sets the credentials of resources that are associated with an integration node. Syntax (1): mqsisetdbparms [<integrationNodeName> | -w <work-dir>] -n <resource> [-u <userId>] [-p <password>] [-f] Syntax (2): mqsisetdbparms [<integrationNodeName> | -w <work-dir>] -n <resource> -d [-f] Syntax (3): mqsisetdbparms [<integrationNodeName> | -w <work-dir>] -n <resource> [-u <userId>] [-i <ssh_identiy>] [-r <passphrase>] [-f] Syntax (4): mqsisetdbparms [<integrationNodeName> | -w <work-dir>] -n <resource> [-u <userId>] [-p <password>] [-c <client identity>] [-s <client secret>] [-f] Syntax (5): mqsisetdbparms [<integrationNodeName> | -w <work-dir>] -n <resource> [-u <userId>] [-p <password>] [-k <API key>] [-f] Command options, syntax (1): <integrationNodeName> The integration node name. -w <work-dir> The work directory of an integration server -n <resource> The type and name of the resource with which the <userId> and <password> are associated. -u <userId> The user identifier associated with <resource>. If the resource already exists and a user ID is associated with the resource, you do not need to set this parameter. If the resource does not already exist, you must set this parameter. -p <password> The password associated with <resource>. You must set the <userId> and <password>. Command options, syntax (2) <integrationNodeName> The integration node name. -w <work-dir> The work directory of an integration server -n <resource> The type and name of the resource with which the <userId> and <password> are associated. -d Deletes the <resource>, <userId>, and <password> information. Command options, syntax (3): <integrationNodeName> The integration node name. -w <work-dir> The work directory of an integration server -n <resource> The type and name of the resource with which the <userId> and <ssh_identity> are associated. -u <userId> The user identifier associated with <resource>. If the resource already exists and a user ID is associated with the resource, you do not need to set this parameter. If the resource does not already exist, you must set this parameter. -i <ssh_identity> The fully qualified path to the SSH identity associated with <resource>. You must set the <userId> and <ssh_identity>. -r <passphrase> The passphrase associated with <ssh_identity>. The passphrase is optional. Command options, syntax (4): <integrationNodeName> The integration node name. -w <work-dir> The work directory of an integration server -n <resource> The type and name of the resource with which the <userId> and <password> are associated. -u <userId> The user identifier associated with <resource>. If the resource already exists and a user ID is associated with the resource, you do not need to set this parameter. If the resource does not already exist, you must set this parameter. -p <password> The password associated with <resource>. You must set the <userId> and <password>. -c <client identity> The client identity associated with <resource>. -s <client secret> The client secret associated with <resource>. Command options, syntax (5): <integrationNodeName> The integration node name. -w <work-dir> The work directory of an integration server -n <resource> The type and name of the resource with which the <userId>, <password>, and <API key> are associated. You must specify a user ID, an API key, or a user ID and an API key. If you specify a user ID, you must also specify a password. You can specify a password without a user ID if the resource already exists and a user ID is already associated with the resource. -u <userId> The user identifier associated with <resource>. -p <password> The password associated with <resource>. -k <API key> The API key associated with <resource>. The resource can be one of the following types. Each type is determined by the syntax of the <resource> parameter: -n odbc::<Data Source Name>[::<integration server name>] The ODBC Data Source Name, with optional integration server name -n ftp::<security identity> The FTP server security identity specified on File nodes. -n jms::<JMS connection factory name> The JMS ConnectionFactory used by a JMS node. -n jndi::<JNDI administered object name> The JNDI name associated with a JMS ConnectionFactory or Destination. -n jdbc::<security identity> The JDBC security identity. -n <data source name> The Data Source Name (DNS) that is used in Compute, Mapping, or Database nodes. -n mq::<security identity> The IBM MQ security identity used to connect to a secured queue manager from MQ nodes. -n mqtt::<security identity> The MQTT security identity used to connect to a secured MQTT server. -n eis::<adapter name> The adapter name used by the WebSphere Adapters nodes. -n email::<security identity> User identity for the EmailInput node or EmailServer policy. -n ims::<security identity> The IMS Connect security identity specified on an IMS node. -n cics::<security_identity> The CICS security identity specified on a CICSRequest node. -n sftp::<security_identity> The SFTP security identity used on a File node. -n cd::<security_identity> The Connect:Direct security identity used on the CD nodes. cd::default is the default security identity used by the nodes. -n wxs::<security_identity> The WebSphere eXtreme Scale security identity used by the WebSphere eXtreme Scale policy. -n brokerKeystore::password The keystore password used by the integration node. -n brokerTruststore::password The truststore password used by the integration node. -n brokerTruststore::keypass::encKey The private key password used by the integration node. -n httpproxy::HTTPPROXY or -n httpproxy::<proxy server> The HTTP proxy security credentials used for request nodes, connectors and services in the integration node. -n salesforce::<security identity> The Salesforce server security identity specified on a Salesforce node. -n loopback::<security identity> The LoopBack connector security identity specified on a LoopBackRequest node. -n rest::<security identity> The REST security identity specified on a REST request node. -n kafka::KAFKA::<server name> The Kafka security identity used for Kafka nodes deployed to an Integration server. When using this command with an integration node name, by default it processes with the integration node running, but the operational changes do not take effect until the integration server, or servers, using the <resource> are restarted. Use the -f option to force a check that the integration node <integrationNodeName> is stopped before this command is allowed to run, thereby ensuring that the changes take effect for all integration servers as soon as the integration node is next started. However, using this option means that the integration node has to be stopped before this command can be run. When using this command with an integration server work directory, the -f option can not be used. BIP8005E: Flag or argument 'user' missing. The command will result in no action being taken, a required flag or a flag's argument is missing. Correct and reissue the command.] 2019-07-15T12:35:00.839Z Stopping Integration Server 2019-07-15T12:35:00.839Z Integration Server stopped 2019-07-15T12:35:00.839Z Stopping Queue Mgr 2019-07-15T12:35:00.839Z Queue Mgr stopped 2019-07-15T12:35:00.839Z Shutdown complete

Hello,

when I want to build the ace-base ( cd 11.0.0.0/ace/ubuntu-1604/base
docker build -t ace:11.0.0.0 .) I get the following error:

unable to prepare context: unable to evaluate symlinks in Dockerfile path: lstat /var/lib/snapd/void/Dockerfile: no such file or directory

How can I solve this?

$ sudo docker build -t ace-mq:11.0.0.3 --build-arg ACE_INSTALL=ace-docker-master/deps --file ace-docker-master/ubuntu/Dockerfile.acemq .
[sudo] password for ibmtec:
Sending build context to Docker daemon 27.61MB
Step 1/38 : ARG BASE_IMAGE=ibmcom/mq:9.1.0.0
Step 2/38 : FROM golang:1.10.3 as builder
---> d0e7a411e3da
Step 3/38 : WORKDIR /go/src/github.com/ot4i/ace-docker/
---> Using cache
---> 56defa02e68d
Step 4/38 : ARG IMAGE_REVISION="Not specified"
---> Using cache
---> c66cb082091c
Step 5/38 : ARG IMAGE_SOURCE="Not specified"
---> Using cache
---> b2e886e32d2d
Step 6/38 : COPY cmd/ ./cmd
COPY failed: stat /var/lib/docker/tmp/docker-builder477502786/cmd: no such file or directory

(ACE_11:)aceuser@ar003-ibm-ace-server-dev-5f9f6f8968-gl2zv:~$ /usr/local/bin/ace_config_setdbparms.sh
{"host":"ar003-ibm-ace-server-dev-5f9f6f8968-gl2zv","ibm_datetime":"2019-03-05T09:01:14.145Z+00:00","ibm_processId":"4402","ibm_processName":"ace_config_setdbparms.sh","ibm_serverName":"ar003","ibm_userName":"aceuser","message":"Handling setdbparms configuration","ibm_type":"ace_containerlog"}
/usr/local/bin/ace_config_setdbparms.sh: line 19: [: missing `]'
{"host":"ar003-ibm-ace-server-dev-5f9f6f8968-gl2zv","ibm_datetime":"2019-03-05T09:01:14.171Z+00:00","ibm_processId":"4402","ibm_processName":"ace_config_setdbparms.sh","ibm_serverName":"ar003","ibm_userName":"aceuser","message":"setdbparms configuration complete","ibm_type":"ace_containerlog"}

Hi,
what would be a sample infrastructure to monitor ACE with Prometheus and Grafana ?
J.

Hi,

The Rhel build for ace fails due to below issue.

Step 5/18 : RUN /opt/ibm/ace-11/ace make registry global accept license silently
---> Running in 4314826e5b87

/bin/sh: /opt/ibm/ace-11/ace: No such file or directory
The command '/bin/sh -c /opt/ibm/ace-11/ace make registry global accept license silently' returned a non-zero code: 127

I am using 11.0.0.3-ACE-LINUX64-DEVELOP.tar.gz. (./build-rhel.sh ace-dev-only ace11 11.0.0.3-ACE-LINUX64-DEVELOP.tar.gz) to build the image.

Below are the file when I run tar xzf 11.0.0.3-ACE-LINUX64-DEVELOP.tar.gz

drwxrwxr-x. 2 root root 4096 Dec 19 12:55 extensions
drwxr-xr-x. 5 root root 4096 Dec 19 12:56 ie02
drwxrwxr-x. 2 root root 4096 Dec 19 12:56 swidtag
drwxrwxr-x. 15 root root 4096 Dec 19 12:56 readmes
drwxrwxr-x. 2 root root 4096 Dec 19 12:56 license
drwxrwxr-x. 1 root root 26616 Dec 19 12:56 ace
drwxrwxr-x. 13 root root 4096 Dec 19 12:56 tools
drwxrwxr-x. 36 root root 4096 Dec 19 12:56 server
drwxrwxr-x. 10 root root 4096 Dec 19 12:58 common

Please let me know why the build is failing even when ace file is present in the tar.

ACE_MQ image is throwing below error when trying to run it in local docker -

. /opt/mqm/bin/setmqenv
/build/slot1/p910_P/src/cmd/tools/mqrc/mqrc.c[2129]
lpiObtainQMDetails --> 545261715

When looked into the details, find out the reason the "authentication problem" but the command is running by "mqm" user which have all the access.

When I build the base image I get flurry of errors

Sending build context to Docker daemon 7.168kB
Step 1/12 : FROM ubuntu:16.04
---> b9e15a5d1e1a
Step 2/12 : LABEL "maintainer"="Dan Robinson [email protected]" "product.id"="447aefb5fd1342d5b893f3934dfded73" "product.name"="IBM App Connect Enterprise" "product.version"="11.0.0.0"
---> Running in 9724ac78ff1c
Removing intermediate container 9724ac78ff1c
---> dbf4aabc4e7b
Step 3/12 : WORKDIR /opt/ibm
---> Running in 1decba8f01c6
Removing intermediate container 1decba8f01c6
---> f23e8c919810
Step 4/12 : RUN apt update && apt -y install --no-install-recommends curl rsyslog sudo && curl http://public.dhe.ibm.com/ibmdl/export/pub/software/websphere/integration/ACE-LINUX64-DEVELOPER.tar.gz | tar xz --exclude ace-11.0.0.0/tools --directory /opt/ibm/ && /opt/ibm/ace-11.0.0.0/ace make registry global accept license silently && apt remove -y curl && rm -rf /var/lib/apt/lists/*
---> Running in 87d472ca5c5b

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

Err:1 http://archive.ubuntu.com/ubuntu xenial InRelease
Could not connect to archive.ubuntu.com:80 (91.189.88.162). - connect (111: Connection refused) [IP: 91.189.88.162 80]
Err:2 http://archive.ubuntu.com/ubuntu xenial-updates InRelease
Unable to connect to archive.ubuntu.com:http: [IP: 91.189.88.162 80]
Err:3 http://archive.ubuntu.com/ubuntu xenial-backports InRelease
Unable to connect to archive.ubuntu.com:http: [IP: 91.189.88.162 80]
Err:4 http://security.ubuntu.com/ubuntu xenial-security InRelease
Could not connect to security.ubuntu.com:80 (91.189.88.149). - connect (111: Connection refused) [IP: 91.189.88.149 80]
Reading package lists...
Building dependency tree...
Reading state information...
All packages are up to date.
W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/xenial/InRelease Could not connect to archive.ubuntu.com:80 (91.189.88.162). - connect (111: Connection refused) [IP: 91.189.88.162 80]
W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/xenial-updates/InRelease Unable to connect to archive.ubuntu.com:http: [IP: 91.189.88.162 80]
W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/xenial-backports/InRelease Unable to connect to archive.ubuntu.com:http: [IP: 91.189.88.162 80]
W: Failed to fetch http://security.ubuntu.com/ubuntu/dists/xenial-security/InRelease Could not connect to security.ubuntu.com:80 (91.189.88.149). - connect (111: Connection refused) [IP: 91.189.88.149 80]
W: Some index files failed to download. They have been ignored, or old ones used instead.

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

Reading package lists...
Building dependency tree...
Reading state information...
Package rsyslog is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Unable to locate package curl
E: Package 'rsyslog' has no installation candidate
E: Unable to locate package sudo
The command '/bin/sh -c apt update && apt -y install --no-install-recommends curl rsyslog sudo && curl http://public.dhe.ibm.com/ibmdl/export/pub/software/websphere/integration/ACE-LINUX64-DEVELOPER.tar.gz | tar xz --exclude ace-11.0.0.0/tools --directory /opt/ibm/ && /opt/ibm/ace-11.0.0.0/ace make registry global accept license silently && apt remove -y curl && rm -rf /var/lib/apt/lists/*' returned a non-zero code: 100

hi,

i am creating base image for ace & mq with 11.0.0.5 and am getting below error.

Step 27/42 : RUN microdnf install --nodocs openssl util-linux unzip python2 && microdnf clean all
---> Running in 0c920c3bfb70
/bin/sh: microdnf: command not found
The command '/bin/sh -c microdnf install --nodocs openssl util-linux unzip python2 && microdnf clean all' returned a non-zero code: 127
[root@localhost ace-docker]#

so i want to understand how can i resolve this error.

Hi,

We are trying to configure MQ SSL properties on the ACE MQOutput node.

mqKeyRepository configuration needs to be configured under BrokerRegistry in server.conf.yaml file. We tried KDB and JKS keystores but only KDB is accepted. Also, the keystore file needs to be stashed.

Current scripts use the java keytool (/jre/bin/keytool) command but building kdb and password stash using keytool is not possible.

Could you please advise whether JKS is supported for mqKeyRepository ?

or any helm chart update possible with "runmqckm" tool?

Thanks for your help.

Regards,
Gopal

Please add support for shared-classes
copy dependency jar files to /var/mqsi/shared-classes or /home/aceuser/ace-server/shared-classes

I was able to run the CallMQMultiEcho application from within Docker, but not from outside. I could not use amqsputc to put a message into the input queue:
$ sudo docker exec -e MQSAMP_USER_ID=aceuser -e MQSERVER='ACE.SVRCONN/TCP/localhost(1414)' -it acemqapp /opt/mqm/samp/bin/amqsputc MULTIIN QMGR
Returned:
/opt/mqm/samp/bin/amqsputc: error while loading shared libraries: libmqic_r.so: cannot open shared object file: No such file or directory
I then searched libmqic_r.so in the Docker image but could not find it. It seems that the MQ client is not installed in the Docker image.
Any idea?

I am attempting to build the ace only docker image in a virtual machine running ubuntu 18.04 Server

I have a NAT network adapter and can access the external internet via the corporate proxy. I set the proxy on the VM and on the /etc/systemd/system/snap.docker.dockerd.service file.

This allows me to run docker build and pull the base images. However while running the build it calls microdnf from the minimal-ubi image. This is failing with the following message.

(microdnf:6): libdnf-WARNING **: 13:44:05.047: Skipping refresh of ubi-7: cannot update repo 'ubi-7': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried; Last error: Curl error (28): Timeout was reached for https://cdn-ubi.redhat.com/content/public/ubi/dist/ubi/server/7/7Server/x86_64/os/repodata/repomd.xml [Resolving timed out after 30000 milliseconds]

I have searched but can find no way to provide to microdnf the proxy server.

Any guidance on this would be appreciated,

Hi,

I am trying to build RHEL Ace Image on a VM. And i want to use the VM's licenses to build the image. But the build is pulling rhel image from FROM registry.access.redhat.com/rhel7 and failing due to Loaded plugins: ovl, product-id, search-disabled-repos, subscription-manager
This system is not registered with an entitlement server. You can use subscription-manager to register.
There are no enabled repos.
But when i run the updates on VM, the yum commands are successfully completed. Please let me know what changes to do in Dockerfile so as to use VM's subscription manager or how I can use VM's licenses when building image.

Hi @IBMRob
I am facing below error while creating an ACE-MQ image, can you please guide me -

Host OS - **RHEL  release 7.5 (Maipo)**
Command - **sudo ./build-rhel.sh ace-mq ace-mq 11.0.0.4-ACE-LINUX64-DEVELOP.tar.gz ibmcom/mq**

Error:  (when start execution of Dockerfile.acemqrhel file in rhrl folder)
Step 5/23 : RUN sed -i 's/# minlen = 9/minlen = 9/'  /etc/security/pwquality.conf && sed -i 's/PASS_MIN_DAYS\t0/PASS_MIN_DAYS\t1/'  /etc/login.defs &&    sed -i 's/PASS_MAX_DAYS\t99999/PASS_MAX_DAYS\t90/'  /etc/login.defs
 ---> Running in 48fa7bb8345f

sed: can't read /etc/security/pwquality.conf: No such file or directory
The command '/bin/sh -c sed -i 's/# minlen = 9/minlen = 9/'  /etc/security/pwquality.conf && sed -i 's/PASS_MIN_DAYS\t0/PASS_MIN_DAYS\t1/'  /etc/login.defs &&    sed -i 's/PASS_MAX_DAYS\t99999/PASS_MAX_DAYS\t90/'  /etc/login.defs' returned a non-zero cod

Hi,
just as a proposal:
you could manage a single dockerfile by providing the verion number as variable if you stay with the numbering scheme from IIB ($version-IIB-LINUX64-DEVELOPER.tar.gz) and adopt this for ACE ($version-ACE-LINUX64-DEVELOPER.tar.gz)
Similar approach for:

• overwriting the curl base address
• changing the name (going from DEV to PROD)
  Cheers
  J.