From b79821772dbbcdd30c15d2445d1b25f35be3ed7f Mon Sep 17 00:00:00 2001 From: veenamandangada <145746560+veena-ux@users.noreply.github.com> Date: Mon, 25 Nov 2024 23:04:39 +0530 Subject: [PATCH 01/32] Updates the content in whats new 911 and version mapping file name change --- ...version-mapping-9-1-1.adoc => version-mapping.adoc} | 0 .../{whats-changed.adoc => whats-changed copy.adoc} | 0 introduction/release-notes/whats-new-9-1-0.adoc | 6 ++---- introduction/release-notes/whats-new-9-1-1.adoc | 10 ++-------- migration-guide/90x-to-91x.adoc | 6 +++--- migration-guide/now-to-next.adoc | 6 ++---- migration-guide/redhat-to-ibm.adoc | 2 +- nav.adoc | 2 +- 8 files changed, 11 insertions(+), 21 deletions(-) rename introduction/release-notes/{version-mapping-9-1-1.adoc => version-mapping.adoc} (100%) rename introduction/release-notes/{whats-changed.adoc => whats-changed copy.adoc} (100%) diff --git a/introduction/release-notes/version-mapping-9-1-1.adoc b/introduction/release-notes/version-mapping.adoc similarity index 100% rename from introduction/release-notes/version-mapping-9-1-1.adoc rename to introduction/release-notes/version-mapping.adoc diff --git a/introduction/release-notes/whats-changed.adoc b/introduction/release-notes/whats-changed copy.adoc similarity index 100% rename from introduction/release-notes/whats-changed.adoc rename to introduction/release-notes/whats-changed copy.adoc diff --git a/introduction/release-notes/whats-new-9-1-0.adoc b/introduction/release-notes/whats-new-9-1-0.adoc index 229bb103..268d11f4 100644 --- a/introduction/release-notes/whats-new-9-1-0.adoc +++ b/introduction/release-notes/whats-new-9-1-0.adoc @@ -50,7 +50,5 @@ An additional section is available inside the documentation that summarizes the == Download documents -A download document that contains the information for obtaining {PRODUCT_LONG} ({PRODUCT_SHORT}) {VERSION}, earlier release and its fix releases, currently Version {VERSION_910}. -{PRODUCT_SHORT} versions are designated with a numerical Major.Minor.Patch following Open Source community Semantic Versioning principle. -Fixes for on-premise installs are available through IBM Fix Central, and {CANVAS} container images are available through Quay Container Registry. -For more information, see https://www.ibm.com/support/pages/node/7151078[BAMOE 9.1 Download Document]. \ No newline at end of file +A download document that contains the information for obtaining {PRODUCT_LONG} can be found here +. All {PRODUCT_SHORT} versions are indicated with a numerical Major.Minor.Patch following Open Source community Semantic Versioning principles. Fixes for on-premise installs are available through IBM Fix Central, and {CANVAS} container images are available through Quay Container Registry. diff --git a/introduction/release-notes/whats-new-9-1-1.adoc b/introduction/release-notes/whats-new-9-1-1.adoc index 6e23eecc..2fa041d0 100644 --- a/introduction/release-notes/whats-new-9-1-1.adoc +++ b/introduction/release-notes/whats-new-9-1-1.adoc @@ -31,14 +31,8 @@ For more information, see xref:supported-environments.adoc[Supported Environment == System requirements -A detailed system requirements that can be accessed using the IBM Support site link for {PRODUCT} {VERSION_911} release. -See https://www.ibm.com/software/reports/compatibility/clarity-reports/report/html/softwareReqsForProduct?deliverableId=839878FFE5974B07B85E83D0B1D368B0[Detailed system requirements]. - -An additional section is available inside the documentation that summarizes the tested and supported configurations for {PRODUCT_SHORT} {VERSION}. See xref:supported-environments.html[Supported Environments] +This section covers the supported configurations for versions {PRODUCT} {VERSION_911} and {VERSION_910}. For more information, see xref:supported-environments.html[Supported Environments] == Download documents -A download document that contains the information for obtaining {PRODUCT_LONG} ({PRODUCT_SHORT}) {VERSION}, earlier release and its fix releases, currently Version {VERSION_910}. -{PRODUCT_SHORT} versions are designated with a numerical Major.Minor.Patch following Open Source community Semantic Versioning principle. -Fixes for on-premise installs are available through IBM Fix Central, and {CANVAS} container images are available through Quay Container Registry. -For more information, see https://www.ibm.com/support/pages/node/7151078[BAMOE 9.1 Download Document]. \ No newline at end of file +For more information on {PRODUCT_LONG} version {VERSION} download document, see https://www.ibm.com/support/pages/node/7151078[BAMOE 9.1 Download Document]. \ No newline at end of file diff --git a/migration-guide/90x-to-91x.adoc b/migration-guide/90x-to-91x.adoc index b9e12638..1db0a5ce 100644 --- a/migration-guide/90x-to-91x.adoc +++ b/migration-guide/90x-to-91x.adoc @@ -156,10 +156,10 @@ You must also report to IBM that a dependency is missing so that the problem can -See xref:../introduction/release-notes/version-mapping-9-1-1.adoc[version mapping for {PRODUCT} version 9.1.1] +See xref:../introduction/release-notes/version-mapping.adoc[version mapping for {PRODUCT_SHORT}]. [start=5] -. Add the `IBM ILMT Compliance Library` to the `pom.xml` _(this is required to report on subscription entitlement usage within the system)_: +. Add the `IBM ILMT Compliance Library` to the `pom.xml` _(this is required to report on subscription entitlement usage within the system)_: + [source,xml] ---- @@ -322,7 +322,7 @@ Previously, the {PRODUCT_SHORT} version {VERSION_90x} used the BOM version {BOM_ Now, both versions are {BOM_VERSION_911}. Update the following lines in your `pom.xml`: + -[source,xml] +[source,xml,subs="attributes+"] ---- bamoe-bom --- {BOM_VERSION_901} diff --git a/migration-guide/now-to-next.adoc b/migration-guide/now-to-next.adoc index c337fca1..49316953 100644 --- a/migration-guide/now-to-next.adoc +++ b/migration-guide/now-to-next.adoc @@ -34,7 +34,7 @@ See https://quarkus.io/guides/maven-tooling[Quarkus and Maven] for more details. ==== Update Maven Settings -The `settings.xml` file is a repository for customizing Maven’s global operational parameters, distinguishing itself from the `pom.xml` by its non-association with particular projects. +A 'pom.xml' file is associated with a particular project whereas the Maven 'settings.xml' file is used to customize global operational parameters across projects. This file includes configurations such as the location of the local repository, alternative sources for remote repositories, and inputting credentials, among others. There are two directories for the storage of the settings.xml file: @@ -187,9 +187,7 @@ During the course of your Maven dependency update, if you encounter any dependen You must also report to IBM that a dependency is missing so that the problem can be resolved in the next release. ==== -The following table is useful in determining which community release is bound to the section details of the mapping of https://www.kie.org/[KIE Community] releases to the current {PRODUCT_LONG} enterprise release. - - +See the following version mappping table for {PRODUCT_SHORT}. .Version Mapping for {PRODUCT} Version 9.0 [cols="1,1,1"] diff --git a/migration-guide/redhat-to-ibm.adoc b/migration-guide/redhat-to-ibm.adoc index 1ea733d7..42dc0bd0 100644 --- a/migration-guide/redhat-to-ibm.adoc +++ b/migration-guide/redhat-to-ibm.adoc @@ -91,7 +91,7 @@ The following archives are typically used in migrating to {PRODUCT_SHORT}: In the displayed table, you must replace **VERSION** with the version of {PRODUCT_SHORT} you are migrating to, such as {VERSION_8_LATEST}. ==== -_Now that you have the files, you can start to migrate our environment._ +Now that you have the files, you can start the migration process. === Step 2: Update Maven Configuration diff --git a/nav.adoc b/nav.adoc index bc01cbc4..a858e962 100644 --- a/nav.adoc +++ b/nav.adoc @@ -4,7 +4,7 @@ ** xref:introduction/release-notes/release-notes-main.html[Release notes] *** xref:introduction/release-notes/whats-new-9-1-1.html[What's new in 9.1.1] *** xref:introduction/release-notes/whats-new-9-1-0.html[What's new in 9.1.0] -*** xref:introduction/release-notes/version-mapping-9-1-1.html[Version mapping in 9.1.1] +*** xref:introduction/release-notes/version-mapping.html[Version mapping] *** xref:introduction/release-notes/supported-environments.html[Supported environments] *** xref:introduction/release-notes/fix-list.html[Fix list] *** xref:introduction/release-notes/known-limitations.html[Known limitations] From 9b3e09c1450bb361894c06eeb4a02246342a2c62 Mon Sep 17 00:00:00 2001 From: veenamandangada <145746560+veena-ux@users.noreply.github.com> Date: Tue, 26 Nov 2024 14:38:55 +0530 Subject: [PATCH 02/32] Added the download document link --- introduction/release-notes/whats-new-9-1-0.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/introduction/release-notes/whats-new-9-1-0.adoc b/introduction/release-notes/whats-new-9-1-0.adoc index 268d11f4..c04b2049 100644 --- a/introduction/release-notes/whats-new-9-1-0.adoc +++ b/introduction/release-notes/whats-new-9-1-0.adoc @@ -50,5 +50,5 @@ An additional section is available inside the documentation that summarizes the == Download documents -A download document that contains the information for obtaining {PRODUCT_LONG} can be found here +A download document that contains the information for obtaining {PRODUCT_LONG} can be found https://www.ibm.com/support/pages/node/7151078[here]. . All {PRODUCT_SHORT} versions are indicated with a numerical Major.Minor.Patch following Open Source community Semantic Versioning principles. Fixes for on-premise installs are available through IBM Fix Central, and {CANVAS} container images are available through Quay Container Registry. From d0cf6ca21d53eb6cfb1a2023027bd2e9879959ca Mon Sep 17 00:00:00 2001 From: veenamandangada <145746560+veena-ux@users.noreply.github.com> Date: Tue, 26 Nov 2024 14:45:56 +0530 Subject: [PATCH 03/32] Updated the version mapping --- partials/version-mapping-now.adoc | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/partials/version-mapping-now.adoc b/partials/version-mapping-now.adoc index c8bbdef2..c554f513 100644 --- a/partials/version-mapping-now.adoc +++ b/partials/version-mapping-now.adoc @@ -38,5 +38,10 @@ | `8.0.5.redhat-00001` | `7.67.2.Final-redhat-00017` +| `IBM BAMOE 8.0.6` +| `RHPAM/RHDM 7.13.6` +| `8.0.5.redhat-00001` +| `7.67.2.Final-redhat-00017` + |=== From 0a38b181e153359957f2d97b2a9c5700f489a5e9 Mon Sep 17 00:00:00 2001 From: veenamandangada <145746560+veena-ux@users.noreply.github.com> Date: Tue, 26 Nov 2024 19:42:04 +0530 Subject: [PATCH 04/32] updating the versions across the documents --- installation/configure-maven.adoc | 2 +- introduction/release-notes/version-mapping.adoc | 9 +++++++++ migration-guide/90x-to-91x.adoc | 2 +- migration-guide/now-to-next.adoc | 15 +-------------- migration-guide/redhat-to-ibm.adoc | 4 ++-- partials/maven-bom-next.adoc | 6 +++--- partials/maven-bom-techpreview.adoc | 6 +++--- ...n-mapping-now.adoc => version-mapping-v8.adoc} | 0 ...ping-next.adoc => version-mapping-v9copy.adoc} | 0 9 files changed, 20 insertions(+), 24 deletions(-) rename partials/{version-mapping-now.adoc => version-mapping-v8.adoc} (100%) rename partials/{version-mapping-next.adoc => version-mapping-v9copy.adoc} (100%) diff --git a/installation/configure-maven.adoc b/installation/configure-maven.adoc index 0d2b4fbc..8e3a4b28 100644 --- a/installation/configure-maven.adoc +++ b/installation/configure-maven.adoc @@ -223,7 +223,7 @@ To configure the {PRODUCT_SHORT} Maven repository locally follow these steps: . Extract the downloaded archive. . Go to the `~/.m2/` directory and open the Maven `settings.xml` file in a text editor or IDE. . Add the following lines to the `` element of the Maven settings.xml file, where `` is the path of the Maven repository that you downloaded. - The format of `` must be `file://$PATH`. For example, `file:///home/userX/bamoe-{VERSION}-maven-repository/:`. + The format of `` must be `file://$PATH`. For example, `file:///home/userX/bamoe-{VERSION}-maven-repository/:` + [source] ---- diff --git a/introduction/release-notes/version-mapping.adoc b/introduction/release-notes/version-mapping.adoc index 645d2d63..7eda5627 100644 --- a/introduction/release-notes/version-mapping.adoc +++ b/introduction/release-notes/version-mapping.adoc @@ -11,9 +11,18 @@ Following table displays the version mapping for version {VERSION_911}: | IBM BAMOE 9.1.0 | {BOM_VERSION_910} | {BOM_VERSION_910} + | IBM BAMOE 9.1.1 | {BOM_VERSION_911} | {BOM_VERSION_911} +| IBM BAMOE 9.1.0-TechPreview +| 9.1.0-TechPreview +| 9.1.0-TechPreview + +//| `IBM BAMOE 9.2.0` +//| `9.2.0-Final` +//| `9.2.0-Final` + |=== diff --git a/migration-guide/90x-to-91x.adoc b/migration-guide/90x-to-91x.adoc index 1db0a5ce..10faf6ee 100644 --- a/migration-guide/90x-to-91x.adoc +++ b/migration-guide/90x-to-91x.adoc @@ -156,7 +156,7 @@ You must also report to IBM that a dependency is missing so that the problem can -See xref:../introduction/release-notes/version-mapping.adoc[version mapping for {PRODUCT_SHORT}]. +See xref:../introduction/release-notes/version-mapping.adoc[version mapping for {PRODUCT_SHORT}] version 9.1. [start=5] . Add the `IBM ILMT Compliance Library` to the `pom.xml` _(this is required to report on subscription entitlement usage within the system)_: diff --git a/migration-guide/now-to-next.adoc b/migration-guide/now-to-next.adoc index 49316953..f31e48d8 100644 --- a/migration-guide/now-to-next.adoc +++ b/migration-guide/now-to-next.adoc @@ -187,21 +187,8 @@ During the course of your Maven dependency update, if you encounter any dependen You must also report to IBM that a dependency is missing so that the problem can be resolved in the next release. ==== -See the following version mappping table for {PRODUCT_SHORT}. +See xref:../introduction/release-notes/version-mapping.adoc[version mapping for {PRODUCT_SHORT}] version 9.1. -.Version Mapping for {PRODUCT} Version 9.0 -[cols="1,1,1"] -|=== -| Product Version | BOM Version | Maven Library Version - -| IBM BAMOE 9.0.0 -| {BOM_VERSION_900} -| {BOM_VERSION_900} -| IBM BAMOE 9.0.1 -| {BOM_VERSION_901} -| {BOM_VERSION_901} - -|=== [start=5] . Add the `IBM ILMT Compliance Library` to the `pom.xml` _(this is required to report on subscription entitlement usage within the system)_: + diff --git a/migration-guide/redhat-to-ibm.adoc b/migration-guide/redhat-to-ibm.adoc index 42dc0bd0..dd9a5633 100644 --- a/migration-guide/redhat-to-ibm.adoc +++ b/migration-guide/redhat-to-ibm.adoc @@ -142,7 +142,7 @@ It is highly recommended to use bill of materials (BOM) to manage project depend A Bill of materials (BOM) can be added to an existing POM file by adding it to the **_dependencyManagement_** section as a dependency with a pom type: -include::../partials/maven-bom-now.adoc[] +include:/partials/maven-bom-now.adoc[]:.. When a bill of materials (BOM) is used, it is not necessary to specify the dependency's version, as that appears from the BOM, so your dependencies end up like the following: @@ -176,7 +176,7 @@ During the course of your Maven dependency update, if you encounter any dependen {PRODUCT_LONG} version {VERSION_80} is based on the former Red Hat 7.13.x offering: -include::../partials/version-mapping-now.adoc[] +include::../partials/version-mapping-v8.adoc[] == Step 3: Update tooling & runtime diff --git a/partials/maven-bom-next.adoc b/partials/maven-bom-next.adoc index 623b9ec8..79a0df78 100644 --- a/partials/maven-bom-next.adoc +++ b/partials/maven-bom-next.adoc @@ -1,15 +1,15 @@ -[source,xml] +[source,xml,subs="attributes+"] ---- com.ibm.bamoe bamoe-bom - + {BOM_VERSION_911} import pom ---- -include::version-mapping-next.adoc[] +See xref:../introduction/release-notes/version-mapping.adoc[version mapping for {PRODUCT_SHORT}] version 9.1. diff --git a/partials/maven-bom-techpreview.adoc b/partials/maven-bom-techpreview.adoc index 90d08656..8c4f9a2f 100644 --- a/partials/maven-bom-techpreview.adoc +++ b/partials/maven-bom-techpreview.adoc @@ -1,15 +1,15 @@ -[source,xml] +[source,xml,subs="attributes+"] ---- com.ibm.bamoe bamoe-techpreview-bom - + {BOM_VERSION_911} import pom ---- -include::version-mapping-next.adoc[] +See xref:../introduction/release-notes/version-mapping.adoc[version mapping for {PRODUCT_SHORT}] version 9.1. diff --git a/partials/version-mapping-now.adoc b/partials/version-mapping-v8.adoc similarity index 100% rename from partials/version-mapping-now.adoc rename to partials/version-mapping-v8.adoc diff --git a/partials/version-mapping-next.adoc b/partials/version-mapping-v9copy.adoc similarity index 100% rename from partials/version-mapping-next.adoc rename to partials/version-mapping-v9copy.adoc From dfe1c7bfaf46eb1726dbc07298dbf8db8a188685 Mon Sep 17 00:00:00 2001 From: veenamandangada <145746560+veena-ux@users.noreply.github.com> Date: Tue, 26 Nov 2024 19:46:48 +0530 Subject: [PATCH 05/32] correcting the broken links --- installation/configure-maven.adoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/installation/configure-maven.adoc b/installation/configure-maven.adoc index 8e3a4b28..ca25c026 100644 --- a/installation/configure-maven.adoc +++ b/installation/configure-maven.adoc @@ -162,7 +162,7 @@ docker run -d -p :8080 quay.io/bamoe/maven-repository:{IMAGE_VERSION} ---- -- -You can verify the repository is running by accessing the repository in your browser at http://localhost:/com/ibm/bamoe. +You can verify the repository is running by accessing the repository in your browser at \ http://localhost:/com/ibm/bamoe. === Configure Maven with the container image URL: To configure Maven with a container image follow these steps: @@ -223,7 +223,7 @@ To configure the {PRODUCT_SHORT} Maven repository locally follow these steps: . Extract the downloaded archive. . Go to the `~/.m2/` directory and open the Maven `settings.xml` file in a text editor or IDE. . Add the following lines to the `` element of the Maven settings.xml file, where `` is the path of the Maven repository that you downloaded. - The format of `` must be `file://$PATH`. For example, `file:///home/userX/bamoe-{VERSION}-maven-repository/:` + The format of `` must be \`file://$PATH`. For example, \`file:///home/userX/bamoe-{VERSION}-maven-repository/:` + [source] ---- From 3fbe66554b872aa8af90a00562d5b9e8e19f080b Mon Sep 17 00:00:00 2001 From: veenamandangada <145746560+veena-ux@users.noreply.github.com> Date: Tue, 26 Nov 2024 20:05:04 +0530 Subject: [PATCH 06/32] correcting the broken links --- installation/configure-maven.adoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/installation/configure-maven.adoc b/installation/configure-maven.adoc index ca25c026..84f95299 100644 --- a/installation/configure-maven.adoc +++ b/installation/configure-maven.adoc @@ -162,7 +162,7 @@ docker run -d -p :8080 quay.io/bamoe/maven-repository:{IMAGE_VERSION} ---- -- -You can verify the repository is running by accessing the repository in your browser at \ http://localhost:/com/ibm/bamoe. +You can verify the repository is running by accessing the repository in your browser at \http://localhost:/com/ibm/bamoe. === Configure Maven with the container image URL: To configure Maven with a container image follow these steps: @@ -223,7 +223,7 @@ To configure the {PRODUCT_SHORT} Maven repository locally follow these steps: . Extract the downloaded archive. . Go to the `~/.m2/` directory and open the Maven `settings.xml` file in a text editor or IDE. . Add the following lines to the `` element of the Maven settings.xml file, where `` is the path of the Maven repository that you downloaded. - The format of `` must be \`file://$PATH`. For example, \`file:///home/userX/bamoe-{VERSION}-maven-repository/:` + The format of `` must be \file://$PATH. For example, \file:///home/userX/bamoe-{VERSION}-maven-repository/: + [source] ---- From 1f79782ce5541fa283ee6d1c665248ad69cef212 Mon Sep 17 00:00:00 2001 From: veenamandangada <145746560+veena-ux@users.noreply.github.com> Date: Tue, 26 Nov 2024 20:31:24 +0530 Subject: [PATCH 07/32] corrected the file name to maven bom v8 doc --- migration-guide/redhat-to-ibm.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/migration-guide/redhat-to-ibm.adoc b/migration-guide/redhat-to-ibm.adoc index dd9a5633..b6ee12e4 100644 --- a/migration-guide/redhat-to-ibm.adoc +++ b/migration-guide/redhat-to-ibm.adoc @@ -142,7 +142,7 @@ It is highly recommended to use bill of materials (BOM) to manage project depend A Bill of materials (BOM) can be added to an existing POM file by adding it to the **_dependencyManagement_** section as a dependency with a pom type: -include:/partials/maven-bom-now.adoc[]:.. +include:/partials/maven-bom-v8.adoc[]: When a bill of materials (BOM) is used, it is not necessary to specify the dependency's version, as that appears from the BOM, so your dependencies end up like the following: From 4caca760b9cea07efb979b25029048627fbe945d Mon Sep 17 00:00:00 2001 From: veenamandangada <145746560+veena-ux@users.noreply.github.com> Date: Tue, 26 Nov 2024 21:35:23 +0530 Subject: [PATCH 08/32] Updated the file name to maven bom now --- migration-guide/redhat-to-ibm.adoc | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/migration-guide/redhat-to-ibm.adoc b/migration-guide/redhat-to-ibm.adoc index b6ee12e4..bf73587e 100644 --- a/migration-guide/redhat-to-ibm.adoc +++ b/migration-guide/redhat-to-ibm.adoc @@ -142,7 +142,7 @@ It is highly recommended to use bill of materials (BOM) to manage project depend A Bill of materials (BOM) can be added to an existing POM file by adding it to the **_dependencyManagement_** section as a dependency with a pom type: -include:/partials/maven-bom-v8.adoc[]: +include::../partials/maven-bom-now.adoc[] When a bill of materials (BOM) is used, it is not necessary to specify the dependency's version, as that appears from the BOM, so your dependencies end up like the following: @@ -178,6 +178,7 @@ During the course of your Maven dependency update, if you encounter any dependen include::../partials/version-mapping-v8.adoc[] + == Step 3: Update tooling & runtime Automated update tools are often provided with both patch updates and new minor versions of {PRODUCT} to facilitate updating certain components such as Decision/Business Central, KIE Server, and the headless controller. From 4090dbd0a5e133f122194769a2b1182345feb2c8 Mon Sep 17 00:00:00 2001 From: veenamandangada <145746560+veena-ux@users.noreply.github.com> Date: Wed, 27 Nov 2024 17:51:01 +0530 Subject: [PATCH 09/32] checking the syntax for path --- installation/configure-maven.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/installation/configure-maven.adoc b/installation/configure-maven.adoc index 84f95299..a6ac2338 100644 --- a/installation/configure-maven.adoc +++ b/installation/configure-maven.adoc @@ -223,7 +223,7 @@ To configure the {PRODUCT_SHORT} Maven repository locally follow these steps: . Extract the downloaded archive. . Go to the `~/.m2/` directory and open the Maven `settings.xml` file in a text editor or IDE. . Add the following lines to the `` element of the Maven settings.xml file, where `` is the path of the Maven repository that you downloaded. - The format of `` must be \file://$PATH. For example, \file:///home/userX/bamoe-{VERSION}-maven-repository/: + The format of `` must be '\file://$PATH'. For example, \file:///home/userX/bamoe-{VERSION}-maven-repository/: + [source] ---- From 9c691035bc8bad805760dd5b59b0eb38821b8f7e Mon Sep 17 00:00:00 2001 From: veenamandangada <145746560+veena-ux@users.noreply.github.com> Date: Wed, 27 Nov 2024 18:00:48 +0530 Subject: [PATCH 10/32] Updates to the page --- introduction/release-notes/whats-new-9-1-1.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/introduction/release-notes/whats-new-9-1-1.adoc b/introduction/release-notes/whats-new-9-1-1.adoc index 2fa041d0..150b50ea 100644 --- a/introduction/release-notes/whats-new-9-1-1.adoc +++ b/introduction/release-notes/whats-new-9-1-1.adoc @@ -31,7 +31,7 @@ For more information, see xref:supported-environments.adoc[Supported Environment == System requirements -This section covers the supported configurations for versions {PRODUCT} {VERSION_911} and {VERSION_910}. For more information, see xref:supported-environments.html[Supported Environments] +This section covers the supported configurations for {PRODUCT_SHORT} versions {VERSION_911} and {VERSION_910}. == Download documents From 4d1c1d0bc07fbe1b7e2efc843cfc3d7d48db39f4 Mon Sep 17 00:00:00 2001 From: veenamandangada <145746560+veena-ux@users.noreply.github.com> Date: Wed, 27 Nov 2024 18:11:06 +0530 Subject: [PATCH 11/32] correcting the syntax of the broken link --- installation/configure-maven.adoc | 4 ++-- introduction/release-notes/whats-new-9-1-0.adoc | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/installation/configure-maven.adoc b/installation/configure-maven.adoc index a6ac2338..c93893bc 100644 --- a/installation/configure-maven.adoc +++ b/installation/configure-maven.adoc @@ -162,7 +162,7 @@ docker run -d -p :8080 quay.io/bamoe/maven-repository:{IMAGE_VERSION} ---- -- -You can verify the repository is running by accessing the repository in your browser at \http://localhost:/com/ibm/bamoe. +You can verify the repository is running by accessing the repository in your browser at '\http://localhost:/com/ibm/bamoe'. === Configure Maven with the container image URL: To configure Maven with a container image follow these steps: @@ -223,7 +223,7 @@ To configure the {PRODUCT_SHORT} Maven repository locally follow these steps: . Extract the downloaded archive. . Go to the `~/.m2/` directory and open the Maven `settings.xml` file in a text editor or IDE. . Add the following lines to the `` element of the Maven settings.xml file, where `` is the path of the Maven repository that you downloaded. - The format of `` must be '\file://$PATH'. For example, \file:///home/userX/bamoe-{VERSION}-maven-repository/: + The format of `` must be '\file://$PATH'. For example, '\file:///home/userX/bamoe-{VERSION}-maven-repository/': + [source] ---- diff --git a/introduction/release-notes/whats-new-9-1-0.adoc b/introduction/release-notes/whats-new-9-1-0.adoc index c04b2049..c885da26 100644 --- a/introduction/release-notes/whats-new-9-1-0.adoc +++ b/introduction/release-notes/whats-new-9-1-0.adoc @@ -50,5 +50,5 @@ An additional section is available inside the documentation that summarizes the == Download documents -A download document that contains the information for obtaining {PRODUCT_LONG} can be found https://www.ibm.com/support/pages/node/7151078[here]. -. All {PRODUCT_SHORT} versions are indicated with a numerical Major.Minor.Patch following Open Source community Semantic Versioning principles. Fixes for on-premise installs are available through IBM Fix Central, and {CANVAS} container images are available through Quay Container Registry. +A download document that contains the information for obtaining {PRODUCT_LONG} can be found https://www.ibm.com/support/pages/node/7151078[here]. +All {PRODUCT_SHORT} versions are indicated with a numerical Major.Minor.Patch following Open Source community Semantic Versioning principles. Fixes for on-premise installs are available through IBM Fix Central, and {CANVAS} container images are available through Quay Container Registry. From 9f91eddcd4093b3491ca5f185bc0b0e7c5c68531 Mon Sep 17 00:00:00 2001 From: veenamandangada <145746560+veena-ux@users.noreply.github.com> Date: Wed, 27 Nov 2024 19:22:15 +0530 Subject: [PATCH 12/32] updates to the versions --- installation/configure-maven.adoc | 4 ++-- introduction/release-notes/version-mapping.adoc | 2 +- introduction/release-notes/whats-new-9-1-0.adoc | 9 +++------ introduction/release-notes/whats-new-9-1-1.adoc | 4 +--- partials/version-mapping-v8.adoc | 6 +++--- 5 files changed, 10 insertions(+), 15 deletions(-) diff --git a/installation/configure-maven.adoc b/installation/configure-maven.adoc index c93893bc..9e729ca0 100644 --- a/installation/configure-maven.adoc +++ b/installation/configure-maven.adoc @@ -162,7 +162,7 @@ docker run -d -p :8080 quay.io/bamoe/maven-repository:{IMAGE_VERSION} ---- -- -You can verify the repository is running by accessing the repository in your browser at '\http://localhost:/com/ibm/bamoe'. +You can verify the repository is running by accessing the repository in your browser at '+ http://localhost:/com/ibm/bamoe +'. === Configure Maven with the container image URL: To configure Maven with a container image follow these steps: @@ -223,7 +223,7 @@ To configure the {PRODUCT_SHORT} Maven repository locally follow these steps: . Extract the downloaded archive. . Go to the `~/.m2/` directory and open the Maven `settings.xml` file in a text editor or IDE. . Add the following lines to the `` element of the Maven settings.xml file, where `` is the path of the Maven repository that you downloaded. - The format of `` must be '\file://$PATH'. For example, '\file:///home/userX/bamoe-{VERSION}-maven-repository/': + The format of `` must be '+ file://$PATH +'. For example, '+ file:///home/userX/bamoe-{VERSION}-maven-repository/ +': + [source] ---- diff --git a/introduction/release-notes/version-mapping.adoc b/introduction/release-notes/version-mapping.adoc index 7eda5627..54bdadb7 100644 --- a/introduction/release-notes/version-mapping.adoc +++ b/introduction/release-notes/version-mapping.adoc @@ -1,7 +1,7 @@ = Version mapping include::../../partials/attributes.adoc[] -Following table displays the version mapping for version {VERSION_911}: +The following table displays the version mapping for version {VERSION_911}: .Version Mapping for {PRODUCT} Version 9.1 [cols="1,1,1"] diff --git a/introduction/release-notes/whats-new-9-1-0.adoc b/introduction/release-notes/whats-new-9-1-0.adoc index c885da26..645db7f4 100644 --- a/introduction/release-notes/whats-new-9-1-0.adoc +++ b/introduction/release-notes/whats-new-9-1-0.adoc @@ -9,8 +9,6 @@ include::../../partials/attributes.adoc[] * Quarkus LTS upgrade - Supports the latest Long-Term Support (LTS) version of Quarkus 3.8.4 by enhancing performance and reliability. -For more information, see xref:supported-environments.adoc[Supported Environments] - === Transition to downstream build @@ -42,11 +40,10 @@ A sample package that includes 19 additional examples, 16 of which focus on work xref:../../getting-started/examples.adoc[Learn more...] == System requirements + +You can find the detailed system requirements by accessing the following link: https://www.ibm.com/software/reports/compatibility/clarity-reports/report/html/softwareReqsForProduct?deliverableId=839878FFE5974B07B85E83D0B1D368B0[Detailed system requirements]. -A detailed system requirements that can be accessed using the IBM Support site link for {PRODUCT} {VERSION_911} release. -See https://www.ibm.com/software/reports/compatibility/clarity-reports/report/html/softwareReqsForProduct?deliverableId=839878FFE5974B07B85E83D0B1D368B0[Detailed system requirements]. - -An additional section is available inside the documentation that summarizes the tested and supported configurations for {PRODUCT_SHORT} {VERSION}. See xref:supported-environments.html[Supported Environments] +An additional section can be found inside the documentation that summarizes the tested and supported configurations. See xref:supported-environments.html[Supported Environments] == Download documents diff --git a/introduction/release-notes/whats-new-9-1-1.adoc b/introduction/release-notes/whats-new-9-1-1.adoc index 150b50ea..fa551c2a 100644 --- a/introduction/release-notes/whats-new-9-1-1.adoc +++ b/introduction/release-notes/whats-new-9-1-1.adoc @@ -26,12 +26,10 @@ For more information on using the editors, see xref:../../tools/editors-librarie * Google Chrome - Latest release * Postgres - 16.4 -For more information, see xref:supported-environments.adoc[Supported Environments] - == System requirements -This section covers the supported configurations for {PRODUCT_SHORT} versions {VERSION_911} and {VERSION_910}. +You can find the supported configurations for {PRODUCT_SHORT} version {VERSION_911} in the following link: xref:supported-environments.adoc[Supported Environments] == Download documents diff --git a/partials/version-mapping-v8.adoc b/partials/version-mapping-v8.adoc index c554f513..18dee2e0 100644 --- a/partials/version-mapping-v8.adoc +++ b/partials/version-mapping-v8.adoc @@ -39,9 +39,9 @@ | `7.67.2.Final-redhat-00017` | `IBM BAMOE 8.0.6` -| `RHPAM/RHDM 7.13.6` -| `8.0.5.redhat-00001` -| `7.67.2.Final-redhat-00017` +| `N/A` +| `8.0.6.redhat-00006` +| `7.67.2.Final-redhat-00025` |=== From fe5663fd930ef5a4501a5091daa6d6b62a6ac120 Mon Sep 17 00:00:00 2001 From: veenamandangada <145746560+veena-ux@users.noreply.github.com> Date: Wed, 27 Nov 2024 19:35:52 +0530 Subject: [PATCH 13/32] updates to the pages --- introduction/release-notes/version-mapping.adoc | 2 +- introduction/release-notes/whats-new-9-1-1.adoc | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/introduction/release-notes/version-mapping.adoc b/introduction/release-notes/version-mapping.adoc index 54bdadb7..60b7fcb9 100644 --- a/introduction/release-notes/version-mapping.adoc +++ b/introduction/release-notes/version-mapping.adoc @@ -1,7 +1,7 @@ = Version mapping include::../../partials/attributes.adoc[] -The following table displays the version mapping for version {VERSION_911}: +The following table displays the version mapping for {PRODUCT_SHORT} version 9.1: .Version Mapping for {PRODUCT} Version 9.1 [cols="1,1,1"] diff --git a/introduction/release-notes/whats-new-9-1-1.adoc b/introduction/release-notes/whats-new-9-1-1.adoc index fa551c2a..f495128d 100644 --- a/introduction/release-notes/whats-new-9-1-1.adoc +++ b/introduction/release-notes/whats-new-9-1-1.adoc @@ -29,7 +29,7 @@ For more information on using the editors, see xref:../../tools/editors-librarie == System requirements -You can find the supported configurations for {PRODUCT_SHORT} version {VERSION_911} in the following link: xref:supported-environments.adoc[Supported Environments] +You can find the supported configurations in the following link: xref:supported-environments.adoc[Supported Environments] == Download documents From 3e0abf6ae26f74342ba10b29c75a183ec66d9e87 Mon Sep 17 00:00:00 2001 From: veenamandangada <145746560+veena-ux@users.noreply.github.com> Date: Wed, 27 Nov 2024 21:24:06 +0530 Subject: [PATCH 14/32] corrected the formatting --- installation/configure-maven.adoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/installation/configure-maven.adoc b/installation/configure-maven.adoc index 9e729ca0..d44c5184 100644 --- a/installation/configure-maven.adoc +++ b/installation/configure-maven.adoc @@ -162,7 +162,7 @@ docker run -d -p :8080 quay.io/bamoe/maven-repository:{IMAGE_VERSION} ---- -- -You can verify the repository is running by accessing the repository in your browser at '+ http://localhost:/com/ibm/bamoe +'. +You can verify the repository is running by accessing the repository in your browser at `+http://localhost:/com/ibm/bamoe+`. === Configure Maven with the container image URL: To configure Maven with a container image follow these steps: @@ -223,7 +223,7 @@ To configure the {PRODUCT_SHORT} Maven repository locally follow these steps: . Extract the downloaded archive. . Go to the `~/.m2/` directory and open the Maven `settings.xml` file in a text editor or IDE. . Add the following lines to the `` element of the Maven settings.xml file, where `` is the path of the Maven repository that you downloaded. - The format of `` must be '+ file://$PATH +'. For example, '+ file:///home/userX/bamoe-{VERSION}-maven-repository/ +': + The format of `` must be `+file://$PATH+`. For example, `+file:///home/userX/bamoe-{VERSION}-maven-repository/+`: + [source] ---- From abcdf969c8f6895baa33287c1319e7833c892550 Mon Sep 17 00:00:00 2001 From: veenamandangada <145746560+veena-ux@users.noreply.github.com> Date: Mon, 2 Dec 2024 11:26:42 +0530 Subject: [PATCH 15/32] technical to technology update --- introduction/release-notes/supported-environments.adoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/introduction/release-notes/supported-environments.adoc b/introduction/release-notes/supported-environments.adoc index fc30f988..05fce529 100644 --- a/introduction/release-notes/supported-environments.adoc +++ b/introduction/release-notes/supported-environments.adoc @@ -81,7 +81,7 @@ The following web browsers were tested as part of the {PRODUCT_SHORT} {VERSION_9 |=== -The following database was tested as part of the {PRODUCT_SHORT} {VERSION_911} release process for the stateful process technical preview: +The following database was tested as part of the {PRODUCT_SHORT} {VERSION_911} release process for the stateful process technology preview: [%header,cols=2] [%autowidth] @@ -197,7 +197,7 @@ The following web browsers were tested as part of the {PRODUCT_SHORT} {VERSION_9 |=== -The following database was tested as part of the {PRODUCT_SHORT} {VERSION_910} release process for the stateful process technical preview: +The following database was tested as part of the {PRODUCT_SHORT} {VERSION_910} release process for the stateful process technology preview: [%header,cols=2] [%autowidth] From 73b1d9f29f7d94ff5fae151b814280119b33f749 Mon Sep 17 00:00:00 2001 From: veenamandangada <145746560+veena-ux@users.noreply.github.com> Date: Mon, 2 Dec 2024 11:32:21 +0530 Subject: [PATCH 16/32] corrected to postgresql --- introduction/release-notes/whats-new-9-1-1.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/introduction/release-notes/whats-new-9-1-1.adoc b/introduction/release-notes/whats-new-9-1-1.adoc index f495128d..ef28a6fd 100644 --- a/introduction/release-notes/whats-new-9-1-1.adoc +++ b/introduction/release-notes/whats-new-9-1-1.adoc @@ -24,7 +24,7 @@ For more information on using the editors, see xref:../../tools/editors-librarie * OpenShift Container Platform - 4.15 * Kubernetes - 1.30 * Google Chrome - Latest release -* Postgres - 16.4 +* PostgreSQL - 16.4 == System requirements From 1aa64cb3e35a26f57586572fa89d467752fae8b2 Mon Sep 17 00:00:00 2001 From: veenamandangada <145746560+veena-ux@users.noreply.github.com> Date: Mon, 2 Dec 2024 11:35:01 +0530 Subject: [PATCH 17/32] update to the title standalone editors --- introduction/release-notes/whats-new-9-1-1.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/introduction/release-notes/whats-new-9-1-1.adoc b/introduction/release-notes/whats-new-9-1-1.adoc index ef28a6fd..1bf73371 100644 --- a/introduction/release-notes/whats-new-9-1-1.adoc +++ b/introduction/release-notes/whats-new-9-1-1.adoc @@ -4,7 +4,7 @@ include::../../partials/attributes.adoc[] {PRODUCT_LONG}, version {VERSION_911} introduces significant enhancements and capabilities as well as providing critical security and known issue fixes. -=== Standalone editors released in version {VERSION_911} +=== Standalone editors Standalone BPMN and DMN Editors can be embedded in your application from version {VERSION_911} . The same editors used in both BAMOE Canvas and BAMOE Developer Tools for VS Code are available as standalone Javascript libraries that can be imported into any frontend web application. They are available in two separate libraries that can be installed from https://www.npmjs.com/org/ibm[npm] or downloaded from Passport advantage, see https://www.ibm.com/support/pages/node/7151078[BAMOE 9.1 Download Document]: From bc486f12c53c56b3cc7c12c8aa16a11159ad4559 Mon Sep 17 00:00:00 2001 From: veenamandangada <145746560+veena-ux@users.noreply.github.com> Date: Mon, 2 Dec 2024 11:39:20 +0530 Subject: [PATCH 18/32] Updates to the starting paragraph --- introduction/release-notes/whats-new-9-1-1.adoc | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/introduction/release-notes/whats-new-9-1-1.adoc b/introduction/release-notes/whats-new-9-1-1.adoc index 1bf73371..d9786d1d 100644 --- a/introduction/release-notes/whats-new-9-1-1.adoc +++ b/introduction/release-notes/whats-new-9-1-1.adoc @@ -1,7 +1,8 @@ = What's new in version 9.1.1 include::../../partials/attributes.adoc[] -{PRODUCT_LONG}, version {VERSION_911} introduces significant enhancements and capabilities as well as providing critical security and known issue fixes. + +This version includes new standalone editors and some changes to the technology stack as well as providing critical security and known issue fixes. === Standalone editors From 131515abda9c38ce68bfa1a16d7a0303c1c9abf3 Mon Sep 17 00:00:00 2001 From: veenamandangada <145746560+veena-ux@users.noreply.github.com> Date: Mon, 2 Dec 2024 13:09:30 +0530 Subject: [PATCH 19/32] updates to the version mapping content --- introduction/release-notes/version-mapping.adoc | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/introduction/release-notes/version-mapping.adoc b/introduction/release-notes/version-mapping.adoc index 60b7fcb9..98418d5e 100644 --- a/introduction/release-notes/version-mapping.adoc +++ b/introduction/release-notes/version-mapping.adoc @@ -16,9 +16,6 @@ The following table displays the version mapping for {PRODUCT_SHORT} version 9.1 | {BOM_VERSION_911} | {BOM_VERSION_911} -| IBM BAMOE 9.1.0-TechPreview -| 9.1.0-TechPreview -| 9.1.0-TechPreview //| `IBM BAMOE 9.2.0` //| `9.2.0-Final` @@ -26,3 +23,4 @@ The following table displays the version mapping for {PRODUCT_SHORT} version 9.1 |=== +The stateful process technology preview can be accessed via the product BOM and Maven library versions. From 4cb3a6a95b8443c3f31b0fa757ca879719fedd38 Mon Sep 17 00:00:00 2001 From: veenamandangada <145746560+veena-ux@users.noreply.github.com> Date: Mon, 2 Dec 2024 13:23:02 +0530 Subject: [PATCH 20/32] version change update --- introduction/release-notes/release-notes-main.adoc | 6 +++--- partials/attributes.adoc | 1 + 2 files changed, 4 insertions(+), 3 deletions(-) diff --git a/introduction/release-notes/release-notes-main.adoc b/introduction/release-notes/release-notes-main.adoc index 32330403..4fbe72be 100644 --- a/introduction/release-notes/release-notes-main.adoc +++ b/introduction/release-notes/release-notes-main.adoc @@ -1,12 +1,12 @@ = Release notes include::../../partials/attributes.adoc[] -The release notes contain information that is important for the successful installation and use of {PRODUCT_LONG} {VERSION_911} and its product modules and components. +The release notes contain information that is important for the successful installation and use of {PRODUCT_LONG} {VERSION_91X} and its product modules and components. - xref:whats-new-9-1-1.adoc[What's new in 9.1.1] -- xref:whats-new-9-1-1.adoc[What's new in 9.1.0] +- xref:whats-new-9-1-0.adoc[What's new in 9.1.0] - xref:version-mapping-9-1-1.adoc[Version mapping in 9.1.1] -- xref:supported-environments.adoc[Suported Environments] +- xref:supported-environments.adoc[Supported Environments] - xref:fix-list.adoc[Fix List] - xref:known-limitations.adoc[Known Limitations] diff --git a/partials/attributes.adoc b/partials/attributes.adoc index d1d9e8f7..5a4e811b 100644 --- a/partials/attributes.adoc +++ b/partials/attributes.adoc @@ -15,6 +15,7 @@ :VERSION_910: 9.1.0 :VERSION_911: 9.1.1 :VERSION_90X : 9.0.x +:VERSION_91X : 9.1.x :VERSION: {VERSION_911} :PRODUCT_VERSION: {VERSION} :VERSION_80: 8.0.x From 24d2eb7bc50404ec5a60827217f244a5346314a5 Mon Sep 17 00:00:00 2001 From: veenamandangada <145746560+veena-ux@users.noreply.github.com> Date: Mon, 2 Dec 2024 13:30:45 +0530 Subject: [PATCH 21/32] updates to release notes main page --- introduction/release-notes/release-notes-main.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/introduction/release-notes/release-notes-main.adoc b/introduction/release-notes/release-notes-main.adoc index 4fbe72be..a8d50ff6 100644 --- a/introduction/release-notes/release-notes-main.adoc +++ b/introduction/release-notes/release-notes-main.adoc @@ -5,7 +5,7 @@ The release notes contain information that is important for the successful insta - xref:whats-new-9-1-1.adoc[What's new in 9.1.1] - xref:whats-new-9-1-0.adoc[What's new in 9.1.0] -- xref:version-mapping-9-1-1.adoc[Version mapping in 9.1.1] +- xref:version-mapping-9-1-1.adoc[Version mapping] - xref:supported-environments.adoc[Supported Environments] - xref:fix-list.adoc[Fix List] - xref:known-limitations.adoc[Known Limitations] From 9198357b19f1b5b10e5fd3fb8471b36989836d3e Mon Sep 17 00:00:00 2001 From: veenamandangada <145746560+veena-ux@users.noreply.github.com> Date: Mon, 2 Dec 2024 13:36:36 +0530 Subject: [PATCH 22/32] version update in version mapping page --- introduction/release-notes/version-mapping.adoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/introduction/release-notes/version-mapping.adoc b/introduction/release-notes/version-mapping.adoc index 98418d5e..c8c8c46c 100644 --- a/introduction/release-notes/version-mapping.adoc +++ b/introduction/release-notes/version-mapping.adoc @@ -1,9 +1,9 @@ = Version mapping include::../../partials/attributes.adoc[] -The following table displays the version mapping for {PRODUCT_SHORT} version 9.1: +The following table displays the version mapping for {PRODUCT_SHORT} version {VERSION_91X}: -.Version Mapping for {PRODUCT} Version 9.1 +.Version Mapping for {PRODUCT} version {VERSION_91X} [cols="1,1,1"] |=== | Product Version | BOM Version | Maven Library Version From 95ab302bcdc6f6af910691fa4e973c84d5399cf0 Mon Sep 17 00:00:00 2001 From: veenamandangada <145746560+veena-ux@users.noreply.github.com> Date: Mon, 2 Dec 2024 21:28:24 +0530 Subject: [PATCH 23/32] Removed repeated versions --- installation/build-maven-repo.adoc | 2 +- installation/upgrading.adoc | 2 +- introduction/release-notes/whats-new-9-1-0.adoc | 4 ++-- migration-guide/90x-to-91x.adoc | 2 +- partials/gav-mapping-all.adoc | 2 ++ 5 files changed, 7 insertions(+), 5 deletions(-) diff --git a/installation/build-maven-repo.adoc b/installation/build-maven-repo.adoc index c2a28ef2..f1026be0 100644 --- a/installation/build-maven-repo.adoc +++ b/installation/build-maven-repo.adoc @@ -1,4 +1,4 @@ -= Build and run your own BAMOE v9.1.x Maven Repository image on OpenShift += Build and run your own BAMOE version 9.1.x Maven Repository image on OpenShift include::../partials/attributes.adoc[] If you cannot run the container with elevated privileges, follow these instructions to build a version that does not require the elevated privileges. diff --git a/installation/upgrading.adoc b/installation/upgrading.adoc index 41647e46..451e8c94 100644 --- a/installation/upgrading.adoc +++ b/installation/upgrading.adoc @@ -31,4 +31,4 @@ The general guidelines are: * xref:../installation/gav-mapping-rules.adoc[Drools Maven mappings] for anything related to rules or decisions. * xref:../installation/gav-mapping-process.adoc[jBPM Maven mappings] for anything related to BPMN-based stateless/stateful processes. * xref:../installation/gav-mapping-kogito.adoc[Kogito Maven mappings] for anything related to infrastructure or extended services. -* xref:../installation/gav-mapping-kie.adoc[KIE Maven mappings] for anything else that doesn't fall into the above categories. +* xref:../installation/gav-mapping-kie.adoc[KIE Maven mappings] for anything else that does not fall into the above categories. diff --git a/introduction/release-notes/whats-new-9-1-0.adoc b/introduction/release-notes/whats-new-9-1-0.adoc index 645db7f4..9fcb1e3b 100644 --- a/introduction/release-notes/whats-new-9-1-0.adoc +++ b/introduction/release-notes/whats-new-9-1-0.adoc @@ -3,7 +3,7 @@ include::../../partials/attributes.adoc[] {PRODUCT_LONG}, version {VERSION_910} introduces significant enhancements and capabilities as well as providing critical security and known issue fixes. -{PRODUCT_SHORT} version {VERSION_910} supports the following: +This release supports the following: * Java upgrade - Incorporates an upgraded technology stack featuring Java 17 and Jakarta EE 10. @@ -12,7 +12,7 @@ include::../../partials/attributes.adoc[] === Transition to downstream build -* Independent build - With the version {VERSION_910} release, BAMOE employs a complete downstream build by eliminating any dependency on open-source binaries. +* Independent build - In this release, BAMOE employs a complete downstream build by eliminating any dependency on open-source binaries. * Maven Repository Distribution: diff --git a/migration-guide/90x-to-91x.adoc b/migration-guide/90x-to-91x.adoc index 10faf6ee..405bb5ce 100644 --- a/migration-guide/90x-to-91x.adoc +++ b/migration-guide/90x-to-91x.adoc @@ -181,7 +181,7 @@ This is due to importing the `bamoe-bom` into the project, where the various dep + For this example, you will be creating a project with only DMN files. So you must add the the Drools Kogito Quarkus dependency. -In the {PRODUCT_SHORT} version {VERSION} some dependencies had a slight name change, refer to the xref:../partials/gav-mapping-all.adoc[GAV mapping table] and update accordingly. +In the {PRODUCT_SHORT} version {VERSION} some dependencies had a slight name change, see section, 'Maven libraries mapping guide' in xref:../installation/upgrading.adoc[Upgrading] and update accordingly. + [source,xml] ---- diff --git a/partials/gav-mapping-all.adoc b/partials/gav-mapping-all.adoc index 67a9f3c6..5c7c1ba7 100644 --- a/partials/gav-mapping-all.adoc +++ b/partials/gav-mapping-all.adoc @@ -1,3 +1,5 @@ + + .KIE Related Mapping for {PRODUCT} Version {VERSION_910} [cols="3,2,2,1"] |=== From 2eaabc791a299a363c657a0572f7a76b17978fe6 Mon Sep 17 00:00:00 2001 From: veenamandangada <145746560+veena-ux@users.noreply.github.com> Date: Tue, 3 Dec 2024 12:58:05 +0530 Subject: [PATCH 24/32] Updates in whats new --- installation/upgrading.adoc | 2 +- introduction/release-notes/whats-new-9-1-1.adoc | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/installation/upgrading.adoc b/installation/upgrading.adoc index 451e8c94..7956d001 100644 --- a/installation/upgrading.adoc +++ b/installation/upgrading.adoc @@ -20,7 +20,7 @@ You can use https://docs.openshift.com/container-platform/4.14/applications/depl For the new DMN editor: After upgrade, the New DMN Editor will be opened automatically when you first access it in Canvas or Developer tools for VS Code. -Existing DMN files (any version) can be opened directly in the editor. For more information, see xref:../tools/authoring-decisions.adoc[Authoring decisions] +Existing DMN files (any version) can be opened directly in the editor. For more information, see xref:../editing/authoring-decisions.adoc[Authoring decisions] == Maven libraries mapping guide diff --git a/introduction/release-notes/whats-new-9-1-1.adoc b/introduction/release-notes/whats-new-9-1-1.adoc index d9786d1d..623ea30e 100644 --- a/introduction/release-notes/whats-new-9-1-1.adoc +++ b/introduction/release-notes/whats-new-9-1-1.adoc @@ -7,7 +7,7 @@ This version includes new standalone editors and some changes to the technology === Standalone editors -Standalone BPMN and DMN Editors can be embedded in your application from version {VERSION_911} . The same editors used in both BAMOE Canvas and BAMOE Developer Tools for VS Code are available as standalone Javascript libraries that can be imported into any frontend web application. They are available in two separate libraries that can be installed from https://www.npmjs.com/org/ibm[npm] or downloaded from Passport advantage, see https://www.ibm.com/support/pages/node/7151078[BAMOE 9.1 Download Document]: +You can embedd the Standalone BPMN and DMN Editors in your application. The same editors used in both BAMOE Canvas and BAMOE Developer Tools for VS Code are available as standalone Javascript libraries that can be imported into any frontend web application. They are available in two separate libraries that can be installed from https://www.npmjs.com/org/ibm[npm] or downloaded from Passport advantage, see https://www.ibm.com/support/pages/node/7151078[BAMOE 9.1 Download Document]: * @ibm/bamoe-standalone-bpmn-and-dmn-editors-classic : The classic DMN and BPMN Editors * @ibm/bamoe-standalone-dmn-editor : The new DMN Editor @@ -17,7 +17,7 @@ For more information on using the editors, see xref:../../tools/editors-librarie === Modernized Technology Stack -{PRODUCT_SHORT} version {VERSION_911} supports the following new versions for the technology stack: +The following new versions are supported for the technology stack: * IBM Semeru Runtime Open Edition - 17.0.11.0 * Quarkus - 3.8.6 From 6508aef406337129251fe69374d077f89fae0720 Mon Sep 17 00:00:00 2001 From: veenamandangada <145746560+veena-ux@users.noreply.github.com> Date: Wed, 4 Dec 2024 01:40:34 +0530 Subject: [PATCH 25/32] updated image versions 910 to 911 --- installation/build-maven-repo.adoc | 4 ++-- installation/canvas.adoc | 12 ++++++------ introduction/release-notes/whats-new-9-1-0.adoc | 4 +++- migration-guide/90x-to-91x.adoc | 11 +++++------ migration-guide/now-to-next.adoc | 2 +- tools/create-custom-dev-deployment-image.adoc | 4 ++-- tools/dev-deployments.adoc | 8 ++++---- workflow/consoles.adoc | 14 +++++++------- 8 files changed, 30 insertions(+), 29 deletions(-) diff --git a/installation/build-maven-repo.adoc b/installation/build-maven-repo.adoc index f1026be0..cc5abcce 100644 --- a/installation/build-maven-repo.adoc +++ b/installation/build-maven-repo.adoc @@ -76,7 +76,7 @@ spec: output: to: kind: ImageStreamTag - name: bamoe-maven-repository-image:{IMAGE_VERSION_910} + name: bamoe-maven-repository-image:{IMAGE_VERSION} strategy: dockerStrategy: dockerfilePath: Dockerfile @@ -103,7 +103,7 @@ oc start-build --from-dir=. bamoe-maven-repository-image --follow + [source,shell,subs="attributes+"] ---- -oc new-app --image-stream bamoe-maven-repository-image:{IMAGE_VERSION_910} --name bamoe-maven-repo +oc new-app --image-stream bamoe-maven-repository-image:{IMAGE_VERSION} --name bamoe-maven-repo oc create route edge --service=bamoe-maven-repo ---- diff --git a/installation/canvas.adoc b/installation/canvas.adoc index ee9dd6de..9647cc51 100644 --- a/installation/canvas.adoc +++ b/installation/canvas.adoc @@ -13,9 +13,9 @@ It depends on two backend applications to provide full functionality: {CANVAS} and its two backend applications are available as container images. These images are published to Quay.io and can be used to run containers locally or with any cloud provider. -* Canvas → https://quay.io/repository/bamoe/canvas[https://quay.io/repository/bamoe/canvas] @ {IMAGE_VERSION_910} -* Extended Services → https://quay.io/repository/bamoe/extended-services[https://quay.io/repository/bamoe/extended-services] @ {IMAGE_VERSION_910} -* CORS Proxy → https://quay.io/repository/bamoe/cors-proxy[https://quay.io/repository/bamoe/cors-proxy] @ {IMAGE_VERSION_910} +* Canvas → https://quay.io/repository/bamoe/canvas[https://quay.io/repository/bamoe/canvas] @ {IMAGE_VERSION} +* Extended Services → https://quay.io/repository/bamoe/extended-services[https://quay.io/repository/bamoe/extended-services] @ {IMAGE_VERSION} +* CORS Proxy → https://quay.io/repository/bamoe/cors-proxy[https://quay.io/repository/bamoe/cors-proxy] @ {IMAGE_VERSION} NOTE: All three image versions must be the same for deployment to work. @@ -87,7 +87,7 @@ NOTE: All services will be available via `https`, which means that if you're dep [source,shell,subs="attributes+"] ---- -docker run -p 21345:21345 -it quay.io/bamoe/extended-services:{IMAGE_VERSION_910} +docker run -p 21345:21345 -it quay.io/bamoe/extended-services:{IMAGE_VERSION} # Add the -d flag to run in detached mode. ---- Access the API through port 21345, no additional configuration is necessary. @@ -97,7 +97,7 @@ Access the API through port 21345, no additional configuration is necessary. [source,shell,subs="attributes+"] ---- -docker run -p 8090:8080 -it quay.io/bamoe/cors-proxy:{IMAGE_VERSION_910} +docker run -p 8090:8080 -it quay.io/bamoe/cors-proxy:{IMAGE_VERSION} # Add the -d flag to run in detached mode. ---- The API is accessible via port 8090 (8080 is reserved for the bamoe-canvas image). No additional configuration is necessary. @@ -116,7 +116,7 @@ If you are running locally, following the previous steps, use this command to st docker run -p 8080:8080 -it \ -e KIE_SANDBOX_EXTENDED_SERVICES_URL=http://localhost:21345 \ -e KIE_SANDBOX_CORS_PROXY_URL=http://localhost:8090 \ - quay.io/bamoe/canvas:{IMAGE_VERSION_910} + quay.io/bamoe/canvas:{IMAGE_VERSION} # Add the -d flag to run in detached mode. ---- The HTTP server is accessed via port 8080. diff --git a/introduction/release-notes/whats-new-9-1-0.adoc b/introduction/release-notes/whats-new-9-1-0.adoc index 9fcb1e3b..697381cc 100644 --- a/introduction/release-notes/whats-new-9-1-0.adoc +++ b/introduction/release-notes/whats-new-9-1-0.adoc @@ -3,7 +3,9 @@ include::../../partials/attributes.adoc[] {PRODUCT_LONG}, version {VERSION_910} introduces significant enhancements and capabilities as well as providing critical security and known issue fixes. -This release supports the following: +This release supports the following features: + +=== Modernized Technology Stack * Java upgrade - Incorporates an upgraded technology stack featuring Java 17 and Jakarta EE 10. diff --git a/migration-guide/90x-to-91x.adoc b/migration-guide/90x-to-91x.adoc index 405bb5ce..2d4e84b3 100644 --- a/migration-guide/90x-to-91x.adoc +++ b/migration-guide/90x-to-91x.adoc @@ -11,12 +11,11 @@ include::../partials/91x-prerequisites.adoc[] == Procedure -The project migration from {PRODUCT_SHORT} version {VERSION_90X} to {PRODUCT_SHORT} version {VERSION} requires a few steps. -Before proceeding, ensure that all prerequisite tools are installed or updated, then you need to properly set up Maven. +This section describes the process to migrate your projects from version {VERSION_90X} to {VERSION}. Before you start, ensure that you have installed or updated all prerequisite tools. This migration guide will show two ways of migrating your project. One way of migrating is by creating a new project from scratch and then moving the assets to it. -In the other way, you will be updating an existing BAMOE version {VERSION_90X} project. -Either way, the first step is to set up the Maven configuration. +The other way is by updating an existing BAMOE version {VERSION_90X} project. +The next step is to set up the Maven configuration. === Update Maven configuration @@ -156,7 +155,7 @@ You must also report to IBM that a dependency is missing so that the problem can -See xref:../introduction/release-notes/version-mapping.adoc[version mapping for {PRODUCT_SHORT}] version 9.1. +See xref:../introduction/release-notes/version-mapping.adoc[version mapping for {PRODUCT_SHORT} version {VERSION_91X}]. [start=5] . Add the `IBM ILMT Compliance Library` to the `pom.xml` _(this is required to report on subscription entitlement usage within the system)_: @@ -334,7 +333,7 @@ Update the following lines in your `pom.xml`: [start=3] . Update the dependencies GAV. + -In the {PRODUCT_SHORT} version {VERSION} some dependencies had a slight name change, refer to the xref:../partials/gav-mapping-all.adoc[GAV mapping table] and update accordingly. +In the {PRODUCT_SHORT} version {VERSION} some dependencies had a slight name change, see section, 'Maven libraries mapping guide' in xref:../installation/upgrading.adoc[Upgrading] and update accordingly. + One of the renamed dependencies is the `groupdId=org.kie.kogito` and `artifactId=kogito-quarkus`, which was renamed to `groupdId=org.jbpm` and `jbpm-with-drools-quarkus`. + diff --git a/migration-guide/now-to-next.adoc b/migration-guide/now-to-next.adoc index f31e48d8..7c45b631 100644 --- a/migration-guide/now-to-next.adoc +++ b/migration-guide/now-to-next.adoc @@ -187,7 +187,7 @@ During the course of your Maven dependency update, if you encounter any dependen You must also report to IBM that a dependency is missing so that the problem can be resolved in the next release. ==== -See xref:../introduction/release-notes/version-mapping.adoc[version mapping for {PRODUCT_SHORT}] version 9.1. +See xref:../introduction/release-notes/version-mapping.adoc[version mapping for {PRODUCT_SHORT} version {VERSION_91X}]. [start=5] . Add the `IBM ILMT Compliance Library` to the `pom.xml` _(this is required to report on subscription entitlement usage within the system)_: diff --git a/tools/create-custom-dev-deployment-image.adoc b/tools/create-custom-dev-deployment-image.adoc index b0ea8f2c..fd2ca9ce 100644 --- a/tools/create-custom-dev-deployment-image.adoc +++ b/tools/create-custom-dev-deployment-image.adoc @@ -13,14 +13,14 @@ For convenience, one of the deployment options in {CANVAS} allows the user to in == Example 1: Using the Canvas Dev Deployment Base image -The `quay.io/bamoe/canvas-dev-deployment-base:{IMAGE_VERSION_910}` image is used as a base since it already has the `dev-deployment-upload-service` pre-configured. +The `quay.io/bamoe/canvas-dev-deployment-base:{IMAGE_VERSION}` image is used as a base since it already has the `dev-deployment-upload-service` pre-configured. === Containerfile [source,docker,subs="+attributes"] ---- # Set the base image with Java 17, Maven, and the dev-deployment-upload-service. -FROM quay.io/bamoe/canvas-dev-deployment-base:{IMAGE_VERSION_910} +FROM quay.io/bamoe/canvas-dev-deployment-base:{IMAGE_VERSION} # Start as root to get elevated access. USER root diff --git a/tools/dev-deployments.adoc b/tools/dev-deployments.adoc index 872f5a11..9ffecf85 100644 --- a/tools/dev-deployments.adoc +++ b/tools/dev-deployments.adoc @@ -42,8 +42,8 @@ NOTE: The DMN Form Webapp only works for Decisions. Workflows should be handled Images used in this deployment: -- https://quay.io/repository/bamoe/canvas-dev-deployment-quarkus-blank-app[Canvas Dev Deployment Quarkus Blank App]: `quay.io/bamoe/canvas-dev-deployment-quarkus-blank-app:{IMAGE_VERSION_910}` -- https://quay.io/repository/bamoe/canvas-dev-deployment-dmn-form-webapp[Canvas Dev Deployment DMN Form Webapp]: `quay.io/bamoe/canvas-dev-deployment-dmn-form-webapp:{IMAGE_VERSION_910}` +- https://quay.io/repository/bamoe/canvas-dev-deployment-quarkus-blank-app[Canvas Dev Deployment Quarkus Blank App]: `quay.io/bamoe/canvas-dev-deployment-quarkus-blank-app:{IMAGE_VERSION}` +- https://quay.io/repository/bamoe/canvas-dev-deployment-dmn-form-webapp[Canvas Dev Deployment DMN Form Webapp]: `quay.io/bamoe/canvas-dev-deployment-dmn-form-webapp:{IMAGE_VERSION}` == Custom Image @@ -60,9 +60,9 @@ This combination of parameters makes it a highly flexible option, but should be Images used in this deployment: -- https://quay.io/repository/bamoe/canvas-dev-deployment-base[Canvas Dev Deployment Base]: `quay.io/bamoe/canvas-dev-deployment-base:{IMAGE_VERSION_910}` +- https://quay.io/repository/bamoe/canvas-dev-deployment-base[Canvas Dev Deployment Base]: `quay.io/bamoe/canvas-dev-deployment-base:{IMAGE_VERSION}` -NOTE: This image is used by default, but it can be changed to any other available image. If using another image, it's recommended creating it based off of `quay.io/bamoe/canvas-dev-deployment-base:{IMAGE_VERSION_910}`, xref:create-custom-dev-deployment-image.html[more information here]) +NOTE: This image is used by default, but it can be changed to any other available image. If using another image, it's recommended creating it based off of `quay.io/bamoe/canvas-dev-deployment-base:{IMAGE_VERSION}`, xref:create-custom-dev-deployment-image.html[more information here]) === Deployment tokens diff --git a/workflow/consoles.adoc b/workflow/consoles.adoc index d41846db..7407d81f 100644 --- a/workflow/consoles.adoc +++ b/workflow/consoles.adoc @@ -117,7 +117,7 @@ quarkus.http.cors=true .Running the Management Console [source,subs="attributes"] ---- -$ docker run -p 8280:8080 quay.io/bamoe/management-console:{IMAGE_VERSION_910} +$ docker run -p 8280:8080 quay.io/bamoe/management-console:{IMAGE_VERSION} ---- + [NOTE] @@ -128,7 +128,7 @@ Also, the Management Console uses the default Data Index Service port 8180. If you modified this port in your Data Index Service instance, you can set the new Data Index URL using the `RUNTIME_TOOLS_MANAGEMENT_CONSOLE_DATA_INDEX_ENDPOINT` environment variable like: [source,subs="attributes"] ---- -$ docker run -e RUNTIME_TOOLS_MANAGEMENT_CONSOLE_DATA_INDEX_ENDPOINT=http:/_HOST_:_PORT_/graphql -p 8280:8080 quay.io/bamoe/management-console:{IMAGE_VERSION_910} +$ docker run -e RUNTIME_TOOLS_MANAGEMENT_CONSOLE_DATA_INDEX_ENDPOINT=http:/_HOST_:_PORT_/graphql -p 8280:8080 quay.io/bamoe/management-console:{IMAGE_VERSION} ---- ==== @@ -324,7 +324,7 @@ $ docker run -e RUNTIME_TOOLS_MANAGEMENT_CONSOLE_KOGITO_ENV_MODE=PROD -e KOGITO_CONSOLES_KEYCLOAK_URL=http://localhost:8480/auth -e KOGITO_CONSOLES_KEYCLOAK_REALM=kogito -e KOGITO_CONSOLES_KEYCLOAK_CLIENT_ID=kogito-console-react - -p 8280:8080 quay.io/bamoe/management-console:{IMAGE_VERSION_910} + -p 8280:8080 quay.io/bamoe/management-console:{IMAGE_VERSION} ---- == Task Console @@ -427,7 +427,7 @@ In a command terminal, enter the following command to run the Task Console: .Running the Task Console [source,subs="attributes"] ---- -$ docker run -p 8280:8080 quay.io/bamoe/task-console:{IMAGE_VERSION_910} +$ docker run -p 8280:8080 quay.io/bamoe/task-console:{IMAGE_VERSION} ---- [NOTE] @@ -438,7 +438,7 @@ Also, the Task Console uses the default Data Index Service port 8180. If you modified this port in your Data Index Service instance, you can set the new Data Index URL using the `RUNTIME_TOOLS_TASK_CONSOLE_DATA_INDEX_ENDPOINT` environment variable like: [source,subs="attributes"] ---- -$ docker run -e RUNTIME_TOOLS_TASK_CONSOLE_DATA_INDEX_ENDPOINT=http:/_HOST_:_PORT_/graphql -p 8280:8080 quay.io/bamoe/task-console:{IMAGE_VERSION_910} +$ docker run -e RUNTIME_TOOLS_TASK_CONSOLE_DATA_INDEX_ENDPOINT=http:/_HOST_:_PORT_/graphql -p 8280:8080 quay.io/bamoe/task-console:{IMAGE_VERSION} ---- ==== @@ -453,7 +453,7 @@ These states are used in the *Task Inbox* default filter. Without this property, .Configuring custom task states for the Task Console [source,subs="attributes"] ---- -$ docker run -e RUNTIME_TOOLS_TASK_CONSOLE_KOGITO_TASK_STATES_LIST=Started,Pending,Finished,Cancelled -e RUNTIME_TOOLS_TASK_CONSOLE_KOGITO_TASK_ACTIVE_STATES_LIST=Started,Pending -p 8280:8080 quay.io/bamoe/task-console:{IMAGE_VERSION_910} +$ docker run -e RUNTIME_TOOLS_TASK_CONSOLE_KOGITO_TASK_STATES_LIST=Started,Pending,Finished,Cancelled -e RUNTIME_TOOLS_TASK_CONSOLE_KOGITO_TASK_ACTIVE_STATES_LIST=Started,Pending -p 8280:8080 quay.io/bamoe/task-console:{IMAGE_VERSION} ---- .Task Console @@ -513,5 +513,5 @@ $ docker run -e RUNTIME_TOOLS_TASK_CONSOLE_KOGITO_ENV_MODE=PROD -e KOGITO_CONSOLES_KEYCLOAK_URL=http://localhost:8480/auth -e KOGITO_CONSOLES_KEYCLOAK_REALM=kogito -e KOGITO_CONSOLES_KEYCLOAK_CLIENT_ID=kogito-console-react - -p 8280:8080 quay.io/bamoe/task-console:{IMAGE_VERSION_910} + -p 8280:8080 quay.io/bamoe/task-console:{IMAGE_VERSION} ---- \ No newline at end of file From 3239d0b25aaba3490c8aa4524b4fabdf4d27b6a3 Mon Sep 17 00:00:00 2001 From: veenamandangada <145746560+veena-ux@users.noreply.github.com> Date: Wed, 4 Dec 2024 20:38:48 +0530 Subject: [PATCH 26/32] fixed broken links --- editing/creating-new-projects.adoc | 4 ++-- getting-started/orchestrating.adoc | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/editing/creating-new-projects.adoc b/editing/creating-new-projects.adoc index 8b7b128f..fb7a6ce1 100644 --- a/editing/creating-new-projects.adoc +++ b/editing/creating-new-projects.adoc @@ -40,7 +40,7 @@ image::tools/newProject/canvas-dmn-single-file-workspace-overview.png[Editor pag . *Kebab menu* → Additional operations. From here you can create a new commit in your project or delete your file. . *“Problems” tab* → Lets you see what's wrong with your file, both statically and when running it. - More on running Decisions in the xref:../tools/running-decisions.adoc[Running Decisions] section. + More on running Decisions in the xref:../editing/running-decisions.adoc[Running Decisions] section. From here, you can make this currently one-file project into a more complex one. Let's do that by creating another file using the “New file menu”. You'll see that there are new controls available on the screen. @@ -67,6 +67,6 @@ image::tools/newProject/canvas-multi-file-workspace-overview.png['Editor page on More on all of that at xref:../tools/working-with-git.adoc[Working with Git]. You can click this element to see all the changes you made to your repository since your last Commit and revert them all, if you want. To revert changes to individual files, use the “File switcher”. -Now that you're familiar with the elements of {CANVAS}, you can jump to xref:../tools/authoring-decisions.adoc[Authoring Decisions] or xref:../tools/authoring-workflows.adoc[Authoring Workflows] to start authoring Decisions and Workflows to create a Business Automation project. xref:../tools/applying-accelerators.adoc[Applying Accelerators] can also be interesting if you're starting a new project directly from BAMOE Canvas. +Now that you're familiar with the elements of {CANVAS}, you can jump to xref:../editing/authoring-decisions.adoc[Authoring Decisions] or xref:../editing/authoring-workflows.adoc[Authoring Workflows] to start authoring Decisions and Workflows to create a Business Automation project. xref:../tools/applying-accelerators.adoc[Applying Accelerators] can also be interesting if you're starting a new project directly from BAMOE Canvas. diff --git a/getting-started/orchestrating.adoc b/getting-started/orchestrating.adoc index 807f4469..6f8d8a62 100644 --- a/getting-started/orchestrating.adoc +++ b/getting-started/orchestrating.adoc @@ -18,7 +18,7 @@ The tasks must be deployed with a process in the same application. In Kogito, the decisions can be expressed in different domains or assets, such as DMN and DRL. All the assets, including BPMN, DMN, and DRL must be placed in the resources folder. -When the example application is running, there also must be different running processes, such as a process using a business rule task, containing the URL as `http://localhost:8080/traffic`. +When the example application is running, there also must be different running processes, such as a process using a business rule task, containing the URL as `+http://localhost:8080/traffic+`. == Traffic violations example for embedded method From abe6c9fadd19f4a10802480c337304f0c5ef47ca Mon Sep 17 00:00:00 2001 From: veenamandangada <145746560+veena-ux@users.noreply.github.com> Date: Thu, 5 Dec 2024 21:17:15 +0530 Subject: [PATCH 27/32] version updates --- editing/authoring-scesim.adoc | 11 ++++------- getting-started/orchestrating.adoc | 6 +++--- installation/upgrading.adoc | 2 +- introduction/components.adoc | 4 ++-- .../release-notes/supported-environments.adoc | 4 ++-- migration-guide/redhat-to-ibm.adoc | 2 +- 6 files changed, 13 insertions(+), 16 deletions(-) diff --git a/editing/authoring-scesim.adoc b/editing/authoring-scesim.adoc index b9a96d82..17e1d46a 100644 --- a/editing/authoring-scesim.adoc +++ b/editing/authoring-scesim.adoc @@ -1,4 +1,4 @@ -= Authoring Scenario Simulations += Authoring test Scenarios include::../partials/attributes.adoc[] As a developer of business decisions, you can use test scenarios in {PRODUCT} to test the decision logic in your {PRODUCT} decision services. Test scenarios enable you to ensure that your {PRODUCT} decision services are functioning properly and as expected as you develop your {PRODUCT} project. @@ -29,13 +29,10 @@ NOTE: All the DMN-based scesim assets created prior to version {VERSION} will re NOTE: All the DMN-based scesim assets are compatible only with DMN 1.2 models. Due to this, use DMN Classic Editor instead of DMN New Editor to create DMN models, that will be tested using `.scesim` file. -=== Prerequisites -* {PRODUCT_SHORT} {VERSION_910} -* {DEV_TOOLS} {VERSION_910} -* VSCode (1.66.0+) -* Optional: Language Support for Java(TM) by Red Hat (1.32+) VSCode extension - === Project Setup + +To run this scenario, you must have set up {PRODUCT_SHORT} and Developer Tools for VS Code. See xref:../installation/installation.adoc. Optionally, you can use Language Support for Java(TM). + ==== Cloning the Example Project If you are a new {PRODUCT_SHORT} user and you don't have any project to set up yet, or you prefer having an out-of-the-box project to deal with, you can use the previously mentioned example in the `incubator-kie-kogito-examples` repository. diff --git a/getting-started/orchestrating.adoc b/getting-started/orchestrating.adoc index 6f8d8a62..3225aa49 100644 --- a/getting-started/orchestrating.adoc +++ b/getting-started/orchestrating.adoc @@ -3,7 +3,7 @@ include::../partials/attributes.adoc[] The following example is a workflow scenario in {PRODUCT} that demonstrates how you can use process definitions to orchestrate your {PRODUCT} decision services. The example of a traffic violations project describes how to use decisions within the processes and how to integrate decisions in an embedded way using the business rule tasks, which must be deployed with a process in the same application. -NOTE: {PRODUCT} fully supports Straight-Through-Processing (STP) where processes are integrating decisions without any safe points and without persistence. For more {PRODUCT} examples that use process capabilities, see the references below. Stateful processing is provided as a technology preview (xref:../workflow/overview.adoc[Stateful processs overview]) in the {VERSION_910}. +NOTE: {PRODUCT} fully supports Straight-Through-Processing (STP) where processes are integrating decisions without any safe points and without persistence. For more {PRODUCT} examples that use process capabilities, see the references below. Stateful processing is provided as a technology preview (xref:../workflow/overview.adoc[Stateful processs overview]) in the {VERSION_910} and {VERSION_911}. The following diagram illustrates how decisions are integrated with processes: @@ -162,7 +162,7 @@ image::traffic-violation-dmn-businessrule.png[Image of traffic violation task (D The properties that are required to be set for the DMN service task include `Rule Language`, which must be set as `DMN`. Also, you must set the values for `Namespace` and DMN Model Name` properties as defined in the DMN model, such as `TrafficViolation.dmn`. For example, you can set the following values: - Rule Language: `DMN` -- Namespace: `https://github.com/kiegroup/drools/kie-dmn/_A4BCA8B8-CF08-433F-93B2-A2598F19ECFF` +- Namespace: `+https://github.com/kiegroup/drools/kie-dmn/_A4BCA8B8-CF08-433F-93B2-A2598F19ECFF+` - DMN Model Name: `Traffic Violation` The input for the traffic violation task includes `Driver` and `Violation` variables, and the output includes `Suspended` and `Fine` in the Data Assignment property. @@ -182,7 +182,7 @@ You can start the Quarkus server with the following command in the project root: mvn quarkus:dev ---- -Then you can check the application Swagger UI at `http://localhost:8080/q/swagger-ui/#/` +Then you can check the application Swagger UI at `+http://localhost:8080/q/swagger-ui/#/+` === Other examples diff --git a/installation/upgrading.adoc b/installation/upgrading.adoc index 7956d001..ea7bfc14 100644 --- a/installation/upgrading.adoc +++ b/installation/upgrading.adoc @@ -24,7 +24,7 @@ Existing DMN files (any version) can be opened directly in the editor. For more == Maven libraries mapping guide -With the transition of the KIE projets to the Apache Software Foundation (ASF), it has become necessary to rename a number of Maven modules. The following table(s) describe the changes to the Maven GAV (GroupID/ArtifactID/Version) in {VERSION_910}: +With the transition of the KIE projets to the Apache Software Foundation (ASF), it has become necessary to rename a number of Maven modules. The following table(s) describe the changes to the Maven GAV (GroupID/ArtifactID/Version) that happened in {VERSION_910}: The general guidelines are: diff --git a/introduction/components.adoc b/introduction/components.adoc index c5fe4127..b550966e 100644 --- a/introduction/components.adoc +++ b/introduction/components.adoc @@ -5,7 +5,7 @@ include::../partials/attributes.adoc[] {PRODUCT_LONG} is a developer-first technology that offers a highly customizable set-up and solution. {PRODUCT_SHORT} is developed using well-known technologies, specifications, and open standards. The design of an automation solution, including the components that are part of the application lifecycle, can be easily be adapted to different scenarios. The modular structure of the solution allows for custom, lightweight deployment units that efficiently use computational resources by including only what is needed. -This approach is possible with {PRODUCT_SHORT} v9.1 through the architectural design of the solution, which allows the creation of solutions targeting the automation of decisions, business rules, straight-through processes, and long-running business processes. +This approach is possible with {PRODUCT_SHORT} version 9.1 through the architectural design of the solution, which allows the creation of solutions targeting the automation of decisions, business rules, straight-through processes, and long-running business processes. Services designed to address particular domain business problems can improve team performance and simplify the application lifecycle from development to deployment. An automation solution with IBM BAMOE includes: @@ -41,7 +41,7 @@ More complex scenarios can be implemented through the orchestration of business [IMPORTANT] ==== -The stateful process automation feature is a technology preview in IBM {PRODUCT_SHORT} v9.1.0. For more information, see xref:../workflow/overview.html[Stateful processs overview]. +The stateful process automation feature is a technology preview in IBM {PRODUCT_SHORT} version {VERSION_910} and {VERSION_911}. For more information, see xref:../workflow/overview.html[Stateful processs overview]. ==== == Components overview diff --git a/introduction/release-notes/supported-environments.adoc b/introduction/release-notes/supported-environments.adoc index 05fce529..b7b7f10c 100644 --- a/introduction/release-notes/supported-environments.adoc +++ b/introduction/release-notes/supported-environments.adoc @@ -1,8 +1,8 @@ -= BAMOE version 9.1 supported configurations += Supported environments include::../../partials/attributes.adoc[] -This section summarizes the tested and supported configurations available for {PRODUCT_SHORT} {VERSION}. Support is available for any issues you identify while using the functionality provided in the product in production or development, physical or virtual environments, and depending on your subscription agreement. For any supplementary details, in particular for patch releases, you can see the https://www.ibm.com/software/reports/compatibility/clarity-reports/report/html/softwareReqsForProduct?deliverableId=1EA3BE2E21944FDABF4A432FD818E438[IBM Support site link]. +This section summarizes the tested and supported configurations available for {PRODUCT_SHORT} {VERSION_91X}. Support is available for any issues you identify while using the functionality provided in the product in production or development, physical or virtual environments, and depending on your subscription agreement. For any supplementary details, in particular for patch releases, you can see the https://www.ibm.com/software/reports/compatibility/clarity-reports/report/html/softwareReqsForProduct?deliverableId=1EA3BE2E21944FDABF4A432FD818E438[IBM Support site link]. A supported configuration includes the application containers, the JVM version families and their corresponding Operating Systems. diff --git a/migration-guide/redhat-to-ibm.adoc b/migration-guide/redhat-to-ibm.adoc index bf73587e..2436142d 100644 --- a/migration-guide/redhat-to-ibm.adoc +++ b/migration-guide/redhat-to-ibm.adoc @@ -8,7 +8,7 @@ The offerings formally known as {RH_PAM} / {RH_DM} were transitioned to IBM in 2 {PRODUCT} version {VERSION_80} provides a seemless upgrade path for customers and workloads formally leveraging the Red Hat offerings. By remaining a functionally equivalent product to the Red Hat offering, customers can easily migrate from the former Red Hat offering once they have purchased an IBM subscription for {PRODUCT}. This section provides guidance on how to migrate from the former Red Hat offerings of {RH_PAM} / {RH_DM} to {PRODUCT} version {VERSION_80}. -It is recommended that you follow this migration path before attempting to migrate to the next generation of the product known as {PRODUCT} version {VERSION_910}. +It is recommended that you follow this migration path before attempting to migrate to the next generation of the product known as {PRODUCT} version {VERSION_91X}. If you have designed your jBPM application based on the deployment of the KIE Server using Spring Boot and want to upgrade from the latest community version to the enterprise-supported {PRODUCT_LONG} version 8.0.x, you can find more information on the procedure in the following link. See, https://community.ibm.com/community/user/automation/blogs/tim-wuthenow/2023/06/16/community-to-enterprise-bamoe. As both projects are based on Maven architectures, the process is considerably simplified, by design. From d4d09c3c45d3a9ac9d8c3c64529904748fe508bd Mon Sep 17 00:00:00 2001 From: veenamandangada <145746560+veena-ux@users.noreply.github.com> Date: Fri, 6 Dec 2024 00:24:40 +0530 Subject: [PATCH 28/32] updated image version --- installation/canvas.adoc | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/installation/canvas.adoc b/installation/canvas.adoc index 9647cc51..ddaa9478 100644 --- a/installation/canvas.adoc +++ b/installation/canvas.adoc @@ -38,7 +38,7 @@ export APP_NAME_BAMOE_CANVAS=bamoe-canvas + [source,shell,subs="attributes+"] ---- -oc new-app quay.io/bamoe/extended-services:{IMAGE_VERSION_910} --name=$APP_NAME_EXTENDED_SERVICES +oc new-app quay.io/bamoe/extended-services:{IMAGE_VERSION} --name=$APP_NAME_EXTENDED_SERVICES oc create route edge --service=$APP_NAME_EXTENDED_SERVICES oc label services/$APP_NAME_EXTENDED_SERVICES app.kubernetes.io/part-of=$APP_PART_OF oc label routes/$APP_NAME_EXTENDED_SERVICES app.kubernetes.io/part-of=$APP_PART_OF @@ -49,7 +49,7 @@ oc label deployments/$APP_NAME_EXTENDED_SERVICES app.openshift.io/runtime=golang + [source,shell,subs="attributes+"] ---- -oc new-app quay.io/bamoe/cors-proxy:{IMAGE_VERSION_910} --name=$APP_NAME_CORS_PROXY +oc new-app quay.io/bamoe/cors-proxy:{IMAGE_VERSION} --name=$APP_NAME_CORS_PROXY oc create route edge --service=$APP_NAME_CORS_PROXY oc label services/$APP_NAME_CORS_PROXY app.kubernetes.io/part-of=$APP_PART_OF oc label routes/$APP_NAME_CORS_PROXY app.kubernetes.io/part-of=$APP_PART_OF @@ -60,7 +60,7 @@ oc label deployments/$APP_NAME_CORS_PROXY app.openshift.io/runtime=nodejs + [source,shell,subs="attributes+"] ---- -oc new-app quay.io/bamoe/canvas:{IMAGE_VERSION_910} --name=$APP_NAME_BAMOE_CANVAS \ +oc new-app quay.io/bamoe/canvas:{IMAGE_VERSION} --name=$APP_NAME_BAMOE_CANVAS \ -e KIE_SANDBOX_EXTENDED_SERVICES_URL=https://$(oc get route $APP_NAME_EXTENDED_SERVICES --output jsonpath={.spec.host}) \ -e KIE_SANDBOX_CORS_PROXY_URL=https://$(oc get route $APP_NAME_CORS_PROXY --output jsonpath={.spec.host}) oc create route edge --service=$APP_NAME_BAMOE_CANVAS From 0e850ce47561deb5cc4692adeb5c54a66b546c9a Mon Sep 17 00:00:00 2001 From: veenamandangada <145746560+veena-ux@users.noreply.github.com> Date: Fri, 6 Dec 2024 00:48:02 +0530 Subject: [PATCH 29/32] fixed grammar issues --- editing/authoring-scesim.adoc | 4 ++-- installation/licensing.adoc | 6 +++--- runtime-services-modeling/building-decision-services.adoc | 2 +- runtime-services-modeling/drl-rules-embedded-java-mode.adoc | 2 +- 4 files changed, 7 insertions(+), 7 deletions(-) diff --git a/editing/authoring-scesim.adoc b/editing/authoring-scesim.adoc index 17e1d46a..d3bda20b 100644 --- a/editing/authoring-scesim.adoc +++ b/editing/authoring-scesim.adoc @@ -31,10 +31,10 @@ NOTE: All the DMN-based scesim assets are compatible only with DMN 1.2 models. D === Project Setup -To run this scenario, you must have set up {PRODUCT_SHORT} and Developer Tools for VS Code. See xref:../installation/installation.adoc. Optionally, you can use Language Support for Java(TM). +To run this scenario, you must have set up {PRODUCT_SHORT} and Developer Tools for VS Code. See xref:../installation/installation.adoc[Installation]. Optionally, you can use Language Support for Java(TM). ==== Cloning the Example Project -If you are a new {PRODUCT_SHORT} user and you don't have any project to set up yet, or you prefer having an out-of-the-box project to deal with, you can use the previously mentioned example in the `incubator-kie-kogito-examples` repository. +If you are a new {PRODUCT_SHORT} user and you do not have any project to set up yet, or you prefer having an out-of-the-box project to deal with, you can use the previously mentioned example in the `incubator-kie-kogito-examples` repository. 1. Clone the `incubator-kie-kogito-examples` repository. 2. Open VSCode and navigate to `incubator-kie-kogito-examples/kogito-quarkus-examples/dmn-quarkus-example`. diff --git a/installation/licensing.adoc b/installation/licensing.adoc index e6a8723c..5ed9d03b 100644 --- a/installation/licensing.adoc +++ b/installation/licensing.adoc @@ -47,7 +47,7 @@ For both components, {PRODUCT_DM} and {PRODUCT_PAM}, clients can expect the foll === Licensing for Disaster Recovery or Backup -When considering backup installations, active licenses are required for backup copies that are running simultaneously with the primary installation. Inactive or idling backup copies typically don't need extra licenses. In-depth information can be found in the https://www.ibm.com/about/software-licensing/assets/guides_pdf/Backup.pdf[Backup and Disaster Recovery Licensing Guide]. +When considering backup installations, active licenses are required for backup copies that are running simultaneously with the primary installation. Inactive or idling backup copies typically do not need extra licenses. In-depth information can be found in the https://www.ibm.com/about/software-licensing/assets/guides_pdf/Backup.pdf[Backup and Disaster Recovery Licensing Guide]. You can find the latest LI information for the available components, parts, and software versions in the https://www.ibm.com/about/software-licensing/us-en/product_search?search=5900-AR4&type=pid&platform=[License Information (LI) for {PRODUCT_LONG}]. @@ -86,9 +86,9 @@ In short, {PRODUCT_LONG} deployments are licensed by *Virtual Processor Core (VP Regarding the usage of the product in association with the entitled number of VPCs: -** Active subscriptions allow product deployments into as many environments as clients choose, as long as they don’t exceed the total number of VPCs they have purchased. +** Active subscriptions allow product deployments into as many environments as clients choose, as long as they do not exceed the total number of VPCs they have purchased. ** The number of entitlements must cover the highest expected usage of VPCs during peak periods. -** Clients are responsible for ensuring they don’t exceed their deployment entitlement. +** Clients are responsible for ensuring they do not exceed their deployment entitlement. Additional information, can be found at https://www.ibm.com/software/passportadvantage/about_software_licensing.html[IBM Licensing Metrics]. diff --git a/runtime-services-modeling/building-decision-services.adoc b/runtime-services-modeling/building-decision-services.adoc index 4ba4676e..bf3a9662 100644 --- a/runtime-services-modeling/building-decision-services.adoc +++ b/runtime-services-modeling/building-decision-services.adoc @@ -9,7 +9,7 @@ Before you can begin developing {PRODUCT} services, you need to create a Maven p .Procedure . Run {CANVAS} - see the xref:../installation/canvas.adoc[installation] chapter for more details on how to install and run it. -. If you don't already have a project or an asset file, create a DMN or BPMN file. +. If you do not already have a project or an asset file, create a DMN or BPMN file. . Use the xref:../tools/applying-accelerators.adoc[accelerator] functionality in {CANVAS} to create a project that is buildable and deployable. diff --git a/runtime-services-modeling/drl-rules-embedded-java-mode.adoc b/runtime-services-modeling/drl-rules-embedded-java-mode.adoc index ad3a73e0..f0eb4968 100644 --- a/runtime-services-modeling/drl-rules-embedded-java-mode.adoc +++ b/runtime-services-modeling/drl-rules-embedded-java-mode.adoc @@ -148,7 +148,7 @@ The `KieRuntime` provides methods that are applicable to both rules and processe === Globals Globals are named objects that are made visible to the Drools rule engine, but in a way that is fundamentally different from the one for facts: changes in the object backing a global do not trigger reevaluation of rules. Still, globals are useful for providing static information, as an object offering services that are used in the RHS of a rule, or as a means to return objects from the Drools rule engine. -When you use a global on the LHS of a rule, make sure it is immutable, or, at least, don't expect changes to have any effect on the behavior of your rules. +When you use a global on the LHS of a rule, make sure it is immutable, or, at least, do not expect changes to have any effect on the behavior of your rules. A global must be declared in a rules file, then it needs to be backed up with a Java object. From 80e16a7038638c9157b147ead4b399f97d6b103d Mon Sep 17 00:00:00 2001 From: veenamandangada <145746560+veena-ux@users.noreply.github.com> Date: Fri, 6 Dec 2024 00:50:32 +0530 Subject: [PATCH 30/32] change in the heading --- editing/authoring-scesim.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/editing/authoring-scesim.adoc b/editing/authoring-scesim.adoc index d3bda20b..f562e8a1 100644 --- a/editing/authoring-scesim.adoc +++ b/editing/authoring-scesim.adoc @@ -1,4 +1,4 @@ -= Authoring test Scenarios += Authoring test scenarios include::../partials/attributes.adoc[] As a developer of business decisions, you can use test scenarios in {PRODUCT} to test the decision logic in your {PRODUCT} decision services. Test scenarios enable you to ensure that your {PRODUCT} decision services are functioning properly and as expected as you develop your {PRODUCT} project. From d2128c557d85a681d3b13e8560cb928774dffb50 Mon Sep 17 00:00:00 2001 From: veenamandangada <145746560+veena-ux@users.noreply.github.com> Date: Fri, 6 Dec 2024 13:14:51 +0530 Subject: [PATCH 31/32] topic name change in the link --- editing/authoring-scesim.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/editing/authoring-scesim.adoc b/editing/authoring-scesim.adoc index f562e8a1..769bfcde 100644 --- a/editing/authoring-scesim.adoc +++ b/editing/authoring-scesim.adoc @@ -31,7 +31,7 @@ NOTE: All the DMN-based scesim assets are compatible only with DMN 1.2 models. D === Project Setup -To run this scenario, you must have set up {PRODUCT_SHORT} and Developer Tools for VS Code. See xref:../installation/installation.adoc[Installation]. Optionally, you can use Language Support for Java(TM). +To run this scenario, you must have set up {PRODUCT_SHORT} and Developer Tools for VS Code. See xref:../installation/installation.adoc[Installing]. Optionally, you can use Language Support for Java(TM). ==== Cloning the Example Project If you are a new {PRODUCT_SHORT} user and you do not have any project to set up yet, or you prefer having an out-of-the-box project to deal with, you can use the previously mentioned example in the `incubator-kie-kogito-examples` repository. From 5db9e29c95127b1b5f5b5a2b2f9e36ebfa66094d Mon Sep 17 00:00:00 2001 From: veenamandangada <145746560+veena-ux@users.noreply.github.com> Date: Fri, 6 Dec 2024 14:53:55 +0530 Subject: [PATCH 32/32] rhpam version changes implemented --- migration-guide/redhat-to-ibm.adoc | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/migration-guide/redhat-to-ibm.adoc b/migration-guide/redhat-to-ibm.adoc index 2436142d..5507712f 100644 --- a/migration-guide/redhat-to-ibm.adoc +++ b/migration-guide/redhat-to-ibm.adoc @@ -432,20 +432,20 @@ They are all mapped by the version progression, so it will be fairly quick. So, for instance, if you are running a PostgreSQL database, you must do the following: . Connect to your database instance using your method of preference. -. Apply the SQL scripts appropriate for the version you are migrating from up to RHPAM 7.13. +. Apply the SQL scripts appropriate for the version you are migrating from up to RHPAM 7.13.x [source,shell,subs="attributes+"] ---- ... +$ psql -h $dbhost -U $user < rhpam-7.11-to-7.12.sql +$ psql -h $dbhost -U $user < rhpam-7.12-to-7.13.sql $ psql -h $dbhost -U $user < rhpam-7.13-to-7.13.1.sql -$ psql -h $dbhost -U $user < rhpam-7.13.1-to-7.13.2.sql -$ psql -h $dbhost -U $user < rhpam-7.13.2-to-7.13.3.sql ... ---- [NOTE] ==== -{PRODUCT_SHORT} version {VERSION_80}'s database is compatible with {RH_PAM} 7.13, so all you need to do is to update the database to that level, and you will be set to migrate the rest of your application. +{PRODUCT_SHORT} version {VERSION_80}'s database is compatible with {RH_PAM} 7.13.x, so all you need to do is to update the database to that level, and you will be set to migrate the rest of your application. ==== Once you have executed these SQL statements, your datasource is now up to date.