You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+16-3Lines changed: 16 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,8 +14,7 @@ For information of building images with IBM MQ Advanced please refer to [IBM App
14
14
15
15
The IBM App Connect operator now supports a single image which includes both the ACE server runtime as well as an MQ client. This readme will describe how you can build an equivalent image.
16
16
17
-
A pre-built developer edition image can be found at dockerhub - [ibmcom/ace-server](https://hub.docker.com/r/ibmcom/ace-server)
18
-
A pre-built production edition image can be found on IBM Entitled Registry - [Obtaining the IBM App Connect Enterprise server image from the IBM Cloud Container Registry](https://www.ibm.com/docs/en/app-connect/11.0.0?topic=aciccd-obtaining-app-connect-enterprise-server-image-from-cloud-container-registry)
17
+
Pre-built developer and production edition image can be found on IBM Container Registry - [Obtaining the IBM App Connect Enterprise server image from the IBM Cloud Container Registry](https://www.ibm.com/support/knowledgecenter/en/SSTTDS_11.0.0/com.ibm.ace.icp.doc/certc_install_obtaininstallationimageser.html)
19
18
20
19
21
20
## Building a container image
@@ -28,7 +27,19 @@ Choose if you want to have an image with just App Connect Enterprise or an image
28
27
29
28
### Building a container image which contains an IBM Service provided fix for ACE
30
29
31
-
You may have been provided with a fix for App Connect Enterprise by IBM Support, this fix will have a name of the form `12.0.X.Y-ACE-LinuxX64-TF12345.tar.gz`. In order to apply this fix follow these steps.
30
+
You may have been provided with a fix for App Connect Enterprise by IBM Support, this fix will have a name of the form `12.0.X.Y-ACE-LinuxX64-TF12345.tar.gz`. This fix can be used to create a container image in one of two different ways:
31
+
32
+
#### Installation during container image build
33
+
This method builds a new container image derived from an existing ACE container image and applies the ifix using the standard `mqsifixinst.sh` script. The ifix image can be built from any existing ACE container image, e.g. `ace-only`, `ace-mqclient`, or another ifix image. Simply build `Dockerfile.ifix` passing in the full `BASE_IMAGE` name and the `IFIX_ID` arguments set:
#### Pre-applying the fix to the ACE install image
40
+
This method applies the ifix directly to the ACE installation image that is consumed to make the full container image. **NB**: Only follow these instructions if you have been instructed by IBM Support to "manually install" the ifix, or that the above method is not applicable to your issue. If you follow these instructions then the ifix ID will _not_ appear in the output of `mqsiservice -v`.
41
+
42
+
In order to apply this fix manually follow these steps.
32
43
- On a local system extract the App Connect Enterprise archive
33
44
`tar -xvf ace-12.0.1.0.tar.gz`
34
45
- Extract the fix package into expanded App Connect Enterprise installation
@@ -103,6 +114,8 @@ In the `sample` folder there is an example on how to build a server image with a
103
114
-**ACE_ADMIN_SERVER_CERT** - Set this to your Integration Server SSL certificate.
104
115
-**ACE_ADMIN_SERVER_KEY** - Set this to your Integration Server SSL key certificate.
105
116
117
+
-**FORCE_FLOW_HTTPS** - Set to 'true' and the *.key and *.crt present in `/home/aceuser/httpsNodeCerts/` are used to force all your flows to use https
118
+
106
119
## How to dynamically configure the ACE Integration Server
107
120
108
121
To enable dynamic configuration of the ACE Integration Server, this setup supports configuration injected into the image as files.
0 commit comments