vania-janet/multiturn-rag-retrieval-data huggingface dataset:
* [DevOps native tools, including open toolchains in IBM Cloud® Continuous Delivery](https://www.ibm.com/cloud/architecture/toolchains/)





 Context 



* The retailer is faced with strong competitive pressures. First, they need to mask the complexity of crossing into new products and new channels. For example, they need to expand product sophistication. At the same time, it needs to be simpler for their customers to jump across brands.
* That ability to jump brand means that the retail ecosystem requires connectivity to business partners. Then, the cloud can bring new value from business partners, customers, and other external players.
* Burst user events, like Black Friday, strain existing online systems, forcing the retailer to over-provision the compute infrastructure.
* The retailer’s Developers needed to constantly evolve apps, but traditional tools slowed their ability to deploy updates and features frequently, especially when they collaborate with business partner teams.







 Solution 

A smarter shopping experience is needed to increase customer retention and gross profit margin. The retailer’s traditional sales model was suffering due to the lack of business partner inventory for cross-sales and up-sales. Their shoppers are looking for increased convenience, so that they can quickly find related items together, such as yoga pants and mats.

The retailer must also provide customers with useful content, such as product information, alternative product information, reviews, and real-time inventory visibility. And those customers want it while online and in-store through personal mobile devices and mobile-equipped store associates.

The solution is made up of the following primary components.



* INVENTORY: App for business partner ecosystem that aggregates and communicates inventory, especially new product introductions, including APIs for business partners to reuse in their own retail and B2B apps
* CROSS- AND UP-SALES: App that surfaces cross-sell and up-sell opportunities with APIs that can be used in various e-commerce and mobile apps
* DEVELOPMENT ENVIRONMENT: Kubernetes clusters for Dev, Test, and Production systems increase collaboration and data sharing among the retailer and its business partners



For the retailer to work with global business partners, the inventory APIs required changes to fit each region’s language and market preferences.
Knative add-on is unsupported
: The Knative add-on is automatically removed from your cluster. Instead, use the [Knative open source project](https://knative.dev/docs/install/) or [IBM Cloud® Code Engine](https://cloud.ibm.com/docs/codeengine?topic=codeengine-getting-started), which includes Knative's open-source capabilities.

Worker node versions
: Worker node fix pack update change log documentation is available for version [4.5.24_1526_openshift](https://cloud.ibm.com/docs/openshift?topic=openshift-changelog_archive4524_1526), [4.4.31_1530_openshift](https://cloud.ibm.com/docs/openshift?topic=openshift-changelog_archive4431_1530), [4.3.40_1551_openshift](https://cloud.ibm.com/docs/openshift?topic=openshift-changelog_archive4340_1551), and [3.11.346_1578_openshift](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_311311346_1578).





 14 January 2021 

Cluster autoscaler
: Cluster autoscaler add-on patch update 1.0.1_210 is released. For more information, see the [Cluster autoscaler add-on change log](https://cloud.ibm.com/docs/openshift?topic=openshift-ca_changelog).





 12 January 2021 

Ingress resources
: Added example Ingress resource definitions that are compatible with Kubernetes version 1.19.

Kubernetes benchmarks
: Added how to [run the CIS Kubernetes benchmark tests on your own worker nodes](https://cloud.ibm.com/docs/openshift?topic=openshift-cis-benchmarkcis-worker-test).
A subset of those options for the [CA](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-adv-deploymentibp-console-adv-deployment-ca-customization), [peer](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-adv-deploymentibp-console-adv-deployment-peer-create-json) and [ordering node](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-adv-deploymentibp-console-adv-deployment-orderer-create-json) can now be overridden by using the console or the [APIs](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-v2-apisibp-v2-apis-custom).

Full Java smart contract development support

In addition to smart contracts written in JavaScript, TypeScript, and Go programming languages, it is now possible to deploy Java smart contracts from the console. Moreover, Java can be freely mixed and matched with other application and smart contract programming languages, including JavaScript, TypeScript, and Go. This heterogeneous programming language support enables an organization to capitalize on the full range of its development skills.

In order to use Java chaincode, developers should be aware that:



* Java 11 is required to execute Java smart contracts.
* Gradle v4.x and Maven v3.x are used to build Java smart contracts.
* Custom Gradle versions can be used by using a Gradle wrapper.
* Java smart contracts require the fabric-chaincode-shim at v1.4.6 or later, as this version is the first version that includes support for Java 11.
* For an example of a Java smart contract, see the [FabCar Java smart contract](https://github.com/hyperledger/fabric-samples/tree/release-1.4/chaincode/fabcar/java) from Fabric v1.4.



v2 APIs available
If you created your app by using the app create command and you specified the --build-source option to build the container image from local or repository source, and you want to change your app to point to a different container image, you must first remove the association of the build from your app. For example, run ibmcloud ce application update -n APP_NAME --build-clear. After you remove the association of the build from your app, you can update the app to reference a different image.
* If you are starting with source code that resides in a Git repository, you can choose to let Code Engine take care of building the image from your source and deploying the app with a single operation. In this scenario, Code Engine uploads your image to IBM Cloud® Container Registry. To learn more, see [Deploying your app from repository source code](https://cloud.ibm.com/docs/codeengine?topic=codeengine-app-source-code). If you want more control over the build of your image, then you can choose to [build the image](https://cloud.ibm.com/docs/codeengine?topic=codeengine-build-image) with Code Engine before you deploy your app.
* If you are starting with source code that resides on a local workstation, you can choose to let Code Engine take care of building the image from your source and deploying the app with a single CLI command. In this scenario, Code Engine uploads your image to IBM Cloud® Container Registry. To learn more, see [Deploying your app from local source code with the CLI](https://cloud.ibm.com/docs/codeengine?topic=codeengine-app-local-source-code). If you want more control over the build of your image, then you can choose to [build the image](https://cloud.ibm.com/docs/codeengine?topic=codeengine-build-image) with Code Engine before you deploy your app.

For example, you might choose to let Code Engine handle the build of your local source while you evolve the development of your source for the app.
It might also be necessary to select the latest version in order to have access to the latest features. Note that if you select any version higher than v2.0, no smart contract container will be deployed along with your peer. Instead, each smart contract will be deployed into its own pod when it is deployed on the channel or invoked for the first time. Golang smart contracts that are currently running on a Fabric v1.4 peer need to be upgraded if you plan to run them on a Fabric v2.x peer. See this [topic](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-smart-contracts-v2ibp-console-smart-contracts-v2-write-package-vendor) on vendoring the shim for more information.
* Click Next.



7. The last side panel asks you to Associate an identity to make it the admin of your peer. For the purpose of this tutorial, make your organization admin, Org1 MSP Admin, the admin of your peer as well. It is possible to register and enroll a different identity with the Org1 CA and make that identity the admin of your peer, but this tutorial uses the Org1 MSP Admin identity.
8. Review the summary and click Add peer. The Edit configuration JSON button allows you to override configuration settings for the peer. For this tutorial, the default settings are sufficient. See [Customizing a peer configuration](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-adv-deploymentibp-console-adv-deployment-peer-create-json) to learn more about the options that are available.







 Task: Deploying a peer 



Table 7. Deploying a peer

 Display name MSP ID Enroll ID Secret 

 Create Peer Peer Org1 org1msp 
 CA Org1 CA 
 Peer Identity peer1 peer1pw 
 Administrator certificate org1msp 
 Associate identity Org1 MSP Admin 



In a production scenario, it is recommended that each organization deploy three peers to each channel.
Visit [Getting started with Watson Assistant](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-getting-started) for a tutorial series on building in the new experience.



 Switching the experience 

You can easily switch back and forth between the new experience and the classic experience. However, the new experience provides a simplified user interface, an improved deployment process, and access to the latest features. For more information, see [Migrating to the new experience](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-migrate-overview). If you do need to switch, see [Switching between new and classic experiences](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-switch-experience).





 Using Watson Assistant 

Watson Assistant can be deployed as a managed cloud service or can be installed on premises. This documentation only applies to a managed cloud service or IBM Cloud Pak® for Data version 4.6 or later, and describes how to use the product regardless of how it is deployed. Information that applies exclusively to one deployment type is denoted by the appropriate tag:



IBM Cloud Pak for Data

IBM Cloud Pak® for Data version 4.6 or later for installed instances.
IBM Cloud

IBM Cloud for managed instances that are hosted by IBM Cloud.
You can specify a base Cloud Functions image in your Dockerfile and also specify the dependencies to install when you build your Docker image. You can then specify your custom Docker image when you deploy your app in Cloud Functions. Note that only public Docker images are supported.

Example command

ibmcloud fn action create <action_name> <app_code.py> --docker <dockerhub_username>/<repo_name>:<tag_name>

If your app code is larger than the maximum codeSize described in the [Action Limits](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-limitslimits_actions), you can combine this method with [Packaging multiple Python files into a compressed file](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-prepprep_python_pkg).

For more information, see [Packaging large Python dependencies in a custom Docker image](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-prepprep_python_docker).





 Packaging your app within a custom Docker image 

When to use this method

Your app requires dependencies that are not included with the base Cloud Functions [Python runtime](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-runtimesopenwhisk_ref_python_environments) and your app code, even when it is compressed into a .zip file, is still larger than the maximum codeSize as described in the [Action Limits](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-limitslimits_actions). If so, you can install those dependencies into a custom Docker image and include your app code in the action/exec folder of the Docker skeleton. You can then specify your custom Docker image when you deploy your app in Cloud Functions. During deployment, you do not need to specify for your app code. Note that only public Docker images are supported.

Example command
* [Creating a trigger for an Event Streams package outside IBM Cloud](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-pkg_event_streamseventstreams_trigger_outside)
* [Listening for messages](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-pkg_event_streamseventstreams_listen_messages)
* [Messages are batched](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-pkg_event_streamseventstreams_batched)



* [References for Event Streams](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-pkg_event_streamsmessage_references)



[Mobile SDK](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-pkg_mobile_sdkpkg_mobile_sdk)



* [Add the SDK to your app](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-pkg_mobile_sdkadd-mobile-sdk-app)



* [Install mobile SDK with CocoaPods](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-pkg_mobile_sdkinstall-mobile-sdk-cocoapods)
* [Install mobile SDK with Carthage](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-pkg_mobile_sdkinstall-mobile-sdk-carthage)
* [Install mobile SDK from source code](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-pkg_mobile_sdkinstall-mobile-sdk-source-code)
Deployment strategies
2. Click Continue.







 Configure the application source code repo 

In the Application step, that recommended options for the application source code repo are displayed by default. To view all of the available options for the underlying Git integration, click Advanced Options. By default, the toolchain uses the default sample that clones the sample app as an IBM-hosted Git Repos and Issue Tracking repo.

Zoom

![Kubernetes secure app repository](https://cloud.ibm.com/docs-content/v1/content/562806c0b18119f4d21cb66f5ae6d051634b4a16/ContinuousDelivery/images/ds_kub_setup_app_repo.png)

Figure 3. Kubernetes secure app repository

You can change the name of the app repo. The region of the repo remains the same as the region of the toolchain.

The toolchain template provides a [sample NodeJS](https://us-south.git.cloud.ibm.com/open-toolchain/hello-compliance-app) app. If you want to link an existing Application repo for the toolchain, select Bring your own app and specify the URL for the repo. The toolchain supports linking only to existing Git Repos and Issue Tracking repos.

By default, the application repo template is cloned to your Git Repos and Issue Tracking org. To change the org, enable Advanced options and specify the repo owner.





 Configure the inventory repo 

The inventory repo records the details of the artifacts that are built by the continuous integration toolchains. You can either create a new inventory repo that is a clone of the [inventory repo template](https://us-south.git.cloud.ibm.com/open-toolchain/compliance-inventory) or use an existing inventory repo that you share between toolchains.

Zoom

!
For more information regarding FCM body, see [here](https://firebase.google.com/docs/cloud-messaging/concept-options).

For compatibility with an earlier version for existing Push notification customers, the previous unified data format is still supported but is deprecated.



 Example: Deprecated Push notification service compatible format: 

"ibmenfcmbody": "{"en_data":{"alert":" Password will expire in 10 Days. Please log in to the Bank home page and click on Change Password link to change your password. ", "android_title":"Change Password"}}"







 ibmenapnsbody(string/json) 

This attribute is needed if you want to send push notification to an iOS device. This is the body that you want to send to APNs server, this must be JSON in string format. For more information regarding APNs body, follow this documentation [here](https://developer.apple.com/library/archive/documentation/NetworkingInternet/Conceptual/RemoteNotificationsPG/CreatingtheNotificationPayload.html).

For compatibility with an earlier version for existing Push notification customers, the previous unified data format is still supported but is deprecated.



 Example: Deprecated Push notification service compatible format:
As this change is made, support for the collector-based architecture (v1) that currently resides in the Hybrid Cloud section of the UI will be removed. If you are exclusively evaluating IBM Cloud resources, you can start migrating at any time to the improved user experience by creating an attachment. If you are working using a collector to evaluate a hybrid cloud scenario, additional information will be available about your migration plan soon.





 13 March 2023 

New version of the IBM Cloud Security Best Practices library
: Version 1.1.0 of the IBM Cloud Security Best Practices library and profile are now available. For more information, see the [Change log](https://cloud.ibm.com/docs/security-compliance?topic=security-compliance-ibm-sec-best-practices-change-log).





 3 February 2023 

New version of the IBM Cloud for Financial Services library
: Version 1.1.0 of the IBM Cloud for Financial Services library and profile are now available. For more information, see the [Change log](https://cloud.ibm.com/docs/security-compliance?topic=security-compliance-fs-change-log).





 14 December 2022 

A new and improved experience for Security and Compliance Center is now available!
: We've been working in the background for the past several months to incorporate all of the feedback that we've received and we’re excited to share our new and improved architecture with you. When you work with our new architecture, there are a few changes to terminology and functionality that you’ll need to be aware of.



* Enterprise support: Hierarchical management of organizational compliance
* Simplified setup: There is no need to create service IDs, write IAM policies, or manage API keys when working with IBM Cloud.
* More customization: Create version-able controls, profiles, and assessments through simple declarative rules and then customize evaluation parameters for each attachment.
* New profile format: Moving from a goal-based architecture to an assessment based architecture to provide more transparency into how evaluations are conducted.
* Customer-owned storage: Duration and capacity limits for saved monitoring results are removed by allowing you to secure your compliance data in your own Cloud Object Storage bucket
There are various ways to implement a compliant bastion solution, but we show you how to configure a bastion host in your VPC by using Teleport Enterprise Edition, along with Object Storage and App ID for enhanced security. You will learn how to set up a Teleport-based solution that meets the previously described IBM Cloud Framework for Financial Services requirements.

Object Storage App ID

+2

Virtual Private Cloud (VPC),IBM Cloud Framework for Financial Services



* 2 hours
* 2023-05-11



[Adding Spectrum multicluster (SMC) to Spectrum Symphony ](https://cloud.ibm.com/docs/hpc-spectrum-symphony?topic=hpc-spectrum-symphony-smc-adding-to-symphony)Adding Spectrum multicluster (SMC) to Spectrum Symphony

The Spectrum multicluster feature in IBM Spectrum Symphony Advanced Edition is used to connect multiple IBM Spectrum Symphony clusters into a federation cluster. Using this feature, you can:

Virtual Private Cloud (VPC) IBM Spectrum Symphony



* 1 hour
* 2023-05-02



[Provisioning an IBM Cloud virtual server for VPC](https://cloud.ibm.com/docs/ibm-cloud-provider-for-terraform?topic=ibm-cloud-provider-for-terraform-sample_vpc_config)Provisioning an IBM Cloud virtual server for VPC

Use IBM Cloud Provider plug-in to provision a VPC, and set up networking for your VPC, and provision a virtual server for VPC in your IBM Cloud account. A VPC allows you to create your own space in IBM Cloud so that you can run an isolated environment in the public cloud with custom network policies.

Virtual Private Cloud (VPC) Terraform on IBM Cloud



* 2 hours
* 2023-04-21



[Updating VPC worker nodes that use OpenShift Data Foundation](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift-storage-update-vpc)Updating VPC worker nodes that use OpenShift Data Foundation
Integrate third-party services using hooks 

IBM® Cloud Foundry is deprecated and no longer supported as of 1 June 2023. For more information, see the [deprecation details](https://cloud.ibm.com/docs/cloud-foundry-public?topic=cloud-foundry-public-deprecationdep_details).

You can use hooks to easily integrate third-party services in the SDK for Node.js buildpack. Note that IBM® does not provide support for any third-party services that you integrate. For more information about support, see [Third-party services](https://cloud.ibm.com/docs/cloud-foundry-public?topic=cloud-foundry-public-buildpack_support_statement).

The SDK for Node.js buildpack includes the Dynatrace hook. Dynatrace enables app monitoring of Node.js apps. Learn more about using the Dynatrace hook in the buildpack in the [Dynatrace documentation](https://www.dynatrace.com/support/help/technology-support/cloud-platforms/cloud-foundry/other-deployments-and-configurations/deploy-oneagent-on-pivotal-web-services-for-application-only-monitoring/).

When following instructions in third-party documentation, remember to use the ibmcloud cf command instead of cf to run commands for your IBM Cloud buildpack.
Refer to the [alternatives to the VS Code extension](https://github.com/IBM-Blockchain/blockchain-vscode-extension/issues/3159).

While a smart contract can be packaged using the peer CLI, the VS Code extension for developing smart contracts is a highly useful tool and can be downloaded to your local system.

For more information, see [Developing smart contracts with IBM Blockchain Platform Developer Tools](https://cloud.ibm.com/docs/blockchain?topic=blockchain-develop-vscode).





 Installing a package and proposing a definition 

For information about how to use the console to install smart contract packages and propose and commit smart contract definitions on a channel, see [Deploy a smart contract using Fabric v2.x](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-smart-contracts-v2).