diff --git a/.md_check_config.json b/.md_check_config.json index 9d513d9..108befc 100644 --- a/.md_check_config.json +++ b/.md_check_config.json @@ -8,6 +8,10 @@ { "pattern": "^/LICENSE", "replacement": "{{BASEURL}}/LICENSE" + }, + { + "pattern": "https://www.ibm.com/docs", + "replacement": "https://ibmdocs-test.dcs.ibm.com/docs" } ], "timeout": "20s" diff --git a/README.md b/README.md index 47f1987..5388c52 100644 --- a/README.md +++ b/README.md @@ -5,9 +5,9 @@ This tutorial is for technical and business users who want an introduction to business rules authoring and management with IBM Operational Decision Manager (ODM) running in a container environment. Here are the different offerings where you can use this Getting Started tutorial: * [IBM Operational Decision Manager for Developers](https://hub.docker.com/r/ibmcom/odm/) - To deploy ODM in Docker environments, for evaluation and development purposes. - * [IBM Operational Decision Manager for Developers on Certified Kubernetes](https://artifacthub.io/packages/helm/ibm-odm-charts/ibm-odm-dev/24.0.1) - To deploy ODM on Certified Kubernetes environments, for evaluation and development purposes. - * [IBM Operational Decision Manager for production on Certified Kubernetes](https://www.ibm.com/docs/en/odm/9.0.0?topic=kubernetes-installing-odm-production) - To deploy ODM on Certified Kubernetes environments, for production use. - * [IBM Operational Decision Manager in IBM Cloud Pak for Business Automation in starter mode](https://www.ibm.com/docs/en/cloud-paks/cp-biz-automation/24.0.1?topic=deployments-installing-cp4ba-multi-pattern-starter-deployment) - To deploy ODM on RedHat OpenShift in the context of IBM Cloud Pak for Business Automation in starter mode. + * [IBM Operational Decision Manager for Developers on Certified Kubernetes](https://artifacthub.io/packages/helm/ibm-odm-charts/ibm-odm-dev) - To deploy ODM on Certified Kubernetes environments, for evaluation and development purposes. + * [IBM Operational Decision Manager for production on Certified Kubernetes](https://www.ibm.com/docs/en/odm/9.5.0?topic=kubernetes-installing-odm-production) - To deploy ODM on Certified Kubernetes environments, for production use. + * [IBM Operational Decision Manager in IBM Cloud Pak for Business Automation in starter mode](https://www.ibm.com/docs/en/cloud-paks/cp-biz-automation/25.0.0?topic=deployments-installing-cp4ba-multi-pattern-starter-deployment) - To deploy ODM on RedHat OpenShift in the context of IBM Cloud Pak for Business Automation in starter mode. ## Time required diff --git a/doc/images/scrn_deploy_resnav_icp.jpg b/doc/images/scrn_deploy_resnav_icp.jpg index c4647c1..a13864c 100644 Binary files a/doc/images/scrn_deploy_resnav_icp.jpg and b/doc/images/scrn_deploy_resnav_icp.jpg differ diff --git a/doc/images/scrn_deploy_view_icp.jpg b/doc/images/scrn_deploy_view_icp.jpg index 9908a9c..1af2ad9 100644 Binary files a/doc/images/scrn_deploy_view_icp.jpg and b/doc/images/scrn_deploy_view_icp.jpg differ diff --git a/doc/topics/tut_icp_gs_clean_db_lsn.md b/doc/topics/tut_icp_gs_clean_db_lsn.md index 728d7c6..b51b597 100644 --- a/doc/topics/tut_icp_gs_clean_db_lsn.md +++ b/doc/topics/tut_icp_gs_clean_db_lsn.md @@ -15,7 +15,7 @@ You remove the Miniloan Service decision service from the Decision Center databa 1. Open the Decision Center Business console. 2. Log in as **admin user**. You must be an administrator to remove the decision service. The **business user** cannot remove the decision service. 3. Open the **Library** tab. -4. Hover over the Miniloan Service box, open the drop-down menu, and click **Delete**:![Image shows the drop-down menu](../images/scrn_delete_decision_service.jpg) +4. Click on the drop-down icon that is next to 'Miniloan Service', click **Delete**:![Image shows the drop-down menu](../images/scrn_delete_decision_service.jpg) A warning message opens. Make sure that the message shows the decision service that you want to delete. @@ -29,14 +29,14 @@ You remove the decision artifacts from the Decision Server console. 1. Open the Decision Server console. 2. Log in as **admin user**. -3. Open the **Explorer** tab, and click **RuleApps** under **Navigator**. -4. Select the mydeployment RuleApp, and click **Remove** to delete it. A warning message opens. Make sure that the message shows the RuleApp that you want to delete. -5. Click **Confirm** in the warning message. The console deletes your RuleApp. The RuleApp view opens, and it no longer shows your RuleApp. -6. In the **Explorer** tab, click **Resources** under **Navigator**. +3. Open the **Explorer** tab, and click **RuleApps** at the left-hand sidebar. +4. Select the mydeployment RuleApp checkbox, and click **Delete** to delete it. A warning message opens. Make sure that the message shows the RuleApp that you want to delete. +5. Click **Delete** in the warning message. The console deletes your RuleApp. The RuleApp view opens, and it no longer shows your RuleApp. +6. In the **Explorer** tab, click **Resources** at the left-hand sidebar. 7. Select miniloan-xom.zip, and click **Remove all references**. A warning message opens. It shows the execution object model that you selected. 8. Click **Confirm** in the warning message. Now the execution object model is not referenced from any ruleset or library. 9. Select miniloan-xom.zip, and click **Remove** to remove the execution object model cleanly. -10. In the **Explorer** tab, click **Libraries** under **Navigator**. +10. In the **Explorer** tab, click **Libraries** at the left-hand sidebar. 11. Select mydeployment\_library, and click **Remove** to remove the library. **Note:** You can also remove the Miniloan\_Service\_brm.Branch\_xx\_xx library. This library was created when you ran the test suite. diff --git a/doc/topics/tut_icp_gs_int.md b/doc/topics/tut_icp_gs_int.md index a0675d8..92eb85e 100644 --- a/doc/topics/tut_icp_gs_int.md +++ b/doc/topics/tut_icp_gs_int.md @@ -20,13 +20,13 @@ The tutorial uses a simple decision service that has only one project. The rules * To install **ODM for Developers**, follow this [documentation](https://hub.docker.com/r/ibmcom/odm/). The Decision Center Business console will be available at the URL http://localhost:9060/decisioncenter. The Decision Server console will be deployed at the URL http://localhost:9060/res. - * To install **ODM for Developers on Certified Kubernetes**, follow this [documentation](https://artifacthub.io/packages/helm/ibm-odm-charts/ibm-odm-dev/24.0.0#installing-the-chart). - Refer to [Accessing ODM](https://artifacthub.io/packages/helm/ibm-odm-charts/ibm-odm-dev/24.0.0#accessing-odm) to retrieve the URLs. + * To install **ODM for Developers on Certified Kubernetes**, follow this [documentation](https://artifacthub.io/packages/helm/ibm-odm-charts/ibm-odm-dev/#installing-the-chart). + Refer to [Accessing ODM](https://artifacthub.io/packages/helm/ibm-odm-charts/ibm-odm-dev/#accessing-odm) to retrieve the URLs. - * To install **ODM for production on Certified Kubernetes**, follow this [documentation](https://www.ibm.com/docs/en/odm/9.0.0?topic=production-installing-helm-release-odm). - Refer to [Configuring external access](https://www.ibm.com/docs/en/odm/9.0.0?topic=tasks-configuring-external-access) to retrieve the URLs. + * To install **ODM for production on Certified Kubernetes**, follow this [documentation](https://www.ibm.com/docs/en/odm/9.5.0?topic=production-installing-helm-release-odm). + Refer to [Configuring external access](https://www.ibm.com/docs/en/odm/9.5.0?topic=tasks-configuring-external-access) to retrieve the URLs. - * To install **ODM with IBM Cloud Pak for Business Automation in starter mode**, follow this [documentation](https://www.ibm.com/docs/en/cloud-paks/cp-biz-automation/24.0.0?topic=deployments-installing-cp4ba-multi-pattern-starter-deployment). + * To install **ODM with IBM Cloud Pak for Business Automation in starter mode**, follow this [documentation](https://www.ibm.com/docs/en/cloud-paks/cp-biz-automation/25.0.0?topic=deployments-installing-cp4ba-multi-pattern-starter-deployment). Refer to [Retrieve URLs for ODM in CP4BA starter mode and configure users](../topics/tut_icp_gs_odm_cp4ba_prereqs.md). 2. Get the users and passwords. @@ -43,10 +43,10 @@ The tutorial uses a simple decision service that has only one project. The rules * As business user: `rtsUser1`/`rtsUser1` * In **ODM for Developers on Certified Kubernetes**, by default, you can use `odmAdmin` as the admin user and `rtsUser1` as the business user. - Both users implement the defined **usersPassword** parameter, if used, or a custom configuration, if you choose to manually [Configure user access](https://artifacthub.io/packages/helm/ibm-odm-charts/ibm-odm-dev/24.0.0#configuring-user-access). + Both users implement the defined **usersPassword** parameter, if used, or a custom configuration, if you choose to manually [Configure user access](https://artifacthub.io/packages/helm/ibm-odm-charts/ibm-odm-dev/#configuring-user-access). * In **ODM for production on Certified Kubernetes**, by default, you can use `odmAdmin` as the admin user and `rtsUser1` as the business user. - Both users implement the defined **usersPassword** parameter, if used, or the custom configuration, if you choose to manually [Configure user access](https://www.ibm.com/docs/en/odm/9.0.0?topic=production-configuring-user-access). + Both users implement the defined **usersPassword** parameter, if used, or the custom configuration, if you choose to manually [Configure user access](https://www.ibm.com/docs/en/odm/9.5.0?topic=production-configuring-user-access). * In **ODM with IBM Cloud Pak for Business Automation in starter mode**, you can use `cp4admin` as the admin user and add the *ODM Business User* role to `user1`. Refer to [Retrieve URLs for ODM in CP4BA starter mode and configure users](../topics/tut_icp_gs_odm_cp4ba_prereqs.md). diff --git a/doc/topics/tut_icp_gs_test_ruleset_lsn.md b/doc/topics/tut_icp_gs_test_ruleset_lsn.md index cbecb71..ddb78ae 100644 --- a/doc/topics/tut_icp_gs_test_ruleset_lsn.md +++ b/doc/topics/tut_icp_gs_test_ruleset_lsn.md @@ -14,9 +14,9 @@ You view the RuleApp in the Decision Server console and check the status of the 1. Sign in to your instance of the Decision Server console as **admin user**. 2. Click the **Explorer** tab. -3. In the Navigator, expand **RuleApps**, and then /mydeployment/1.0. You see that the Decision Server console contains version 1.0 of mydeployment, which contains version 1.0 of Miniloan\_ServiceRuleset: +3. Expand **RuleApps** at the left-hand sidebar, and then expand */mydeployment/1.0*. You should see that the Decision Server console contains version 1.0 of mydeployment, which contains version 1.0 of Miniloan\_ServiceRuleset: - ![Image shows the navigation menu](../images/scrn_deploy_resnav_icp.jpg) + Image shows the navigation menu 4. Click /Miniloan\_ServiceRuleset/1.0 to view the details of the ruleset in the Ruleset View. The status of the ruleset is enabled, which indicates that the ruleset can be run: @@ -29,7 +29,7 @@ You test the ruleset with a REST request in the Decision Server console. **Procedure** -1. In the Decision Server console, on the Miniloan\_ServiceRuleset page, click **Retrieve HTDS Description File**. +1. In the Decision Server console, on the Miniloan\_ServiceRuleset page, expand the section **Hosted Transparent Decision Services (HTDS) Options** and click **Retrieve HTDS Description File**. 2. Select the **REST** option, and then choose **OpenAPI-JSON** for the format. 3. Click **View** and copy the URL. The decision service URL uses the following format: @@ -41,9 +41,9 @@ You test the ruleset with a REST request in the Decision Server console. > You can export this URL as `DSC_URL` environment variable to execute the request in [Step 3 \(optional\): Testing the execution of the ruleset using curl](../topics/tut_icp_gs_test_ruleset_lsn.md#step-3-optional-testing-the-execution-of-the-ruleset-using-curl). 4. Close the web page. -5. Back on the Miniloan\_ServiceRuleset page, click **Retrieve HTDS Description File**. +5. Back on the Miniloan\_ServiceRuleset page with the **Retrieve HTDS Description File** dialog. 6. Make sure **REST** and **OpenAPI-JSON** are still selected, and click **Test**. -7. On the REST Service page, replace the entire request description with the following text: +7. On the REST Service page, make sure the **Execution Request** option is *JSON* and replace the entire request description with the following text: ```json {