vania-janet/multiturn-rag-retrieval-data huggingface dataset:
The full URL will then resemble "https://(project-name)-navigator-pn.(cluster-name).(region).containers.appdomain.cloud".

The Platform Navigator home page offers the ability to create instances of the various components.

See the full documentation in [IBM Documentation](https://www.ibm.com/support/knowledgecenter/SSGT7J_20.3/welcome.html). See Capability deployment.





 Known limitations 

The IBM Cloud software catalog installer for Cloud Pak for Integration does not support;



* Multi-zone region (MZR) clusters in IBM Cloud Classic infrastructure
* Clusters deployed in IBM Cloud VPC, in either single zone or multi-zone topologies



This restriction is because those environments do not natively provide the replicated File storage that is required to deploy Cloud Pak for Integration in a resilient fashion.

Installation into MZR Classic clusters and IBM Cloud VPC is supported by manual installation of Cloud Pak for Integration (i.e. not using the software catalog installer) which enables the user to specify your choice of replicated storage provider that has been separately made available for use in the cluster, such as Portworx. Customers wishing to manually install Cloud Pak for Integration in this way can find instructions in [IBM Documentation here](https://www.ibm.com/docs/en/cloud-paks/cp-integration/2021.1?topic=installing).
<service android:name="com.ibm.cloud.eventnotifications.destination.android.ENPushIntentService" android:exported="true">
<intent-filter>
<action android:name="com.google.firebase.MESSAGING_EVENT" />
</intent-filter>
</service>

<service android:name="com.ibm.cloud.eventnotifications.destination.android.ENPush" android:exported="true" >
<intent-filter>
<action android:name="com.google.firebase.INSTANCE_ID_EVENT" />
</intent-filter>
</service>
Show more
* Change the <activity> section to point to the new class

// Replace the below section

<activity android:name="com.ibm.mobilefirstplatform.clientsdk.android.push.api. MFPPushNotificationHandler" android:theme="@android:style/Theme.NoDisplay"/>

// with this

<activity android:name="com.ibm.cloud.eventnotifications.destination.android. ENPushNotificationHandler" android:theme="@android:style/Theme.NoDisplay"/>



2. Change the import statements in the code. The new package name is com.ibm.cloud.eventnotifications.destination.android.. Replace the old push import as shown:

// Replace the below section

import com.ibm.mobilefirstplatform.clientsdk.android.push.api.MFPPush;

// with this

import com.ibm.cloud.eventnotifications.destination.android.ENPush;
3. Initialize the new SDK

// Replace the below section

BMSClient.getInstance().initialize(this, "ibmCloudRegionSuffix");
MFPPush push = MFPPush.getInstance();
What's new 

Stay up to date with the new features that are available for App Configuration service.



 May 2023 



* Support for ServiceNow integration

Manage feature flags enablement by adding additional workflow with ServiceNow® integration. For more information, see [Workflow Integration](https://cloud.ibm.com/docs/app-configuration?topic=app-configuration-ac-manage-workflow).







 March 2023 



* Support for context-based restrictions (CBR)

Manage user and service access to your IBM Cloud App Configuration resources by using context-based restrictions, based on defined criteria. For more information, see [Managing access with context-based restrictions](https://cloud.ibm.com/docs/app-configuration?topic=app-configuration-ac-access-control-cbr).







 January 2023 



* Support for integration with Event Notifications to enable lifecycle event notifications for your App Configuration service instance. For more information, see [Integrating with Event Notifications service](https://cloud.ibm.com/docs/app-configuration?topic=app-configuration-ac-int-en).







 November 2022 



* Allowlisting of domains for Cross-Origin Resource Sharing (CORS) requests from client SDK. For more information, see [Settings](https://cloud.ibm.com/docs/app-configuration?topic=app-configuration-ac-settings).
* Restoring a Snapshot configuration from GitHub. For more information, see [Restore a GitHub snapshot](https://cloud.ibm.com/docs/app-configuration?topic=app-configuration-ac-snapshotsac-restore-a-snapshot).







 October 2022 

Support for high level encryption using IBM® Key Protect for IBM Cloud® (Bring Your Own Key - BYOK) and Hyper Protect Crypto Services (Keep Your Own Key - KYOK). For more information, see [Integrations](https://cloud.ibm.com/docs/app-configuration?topic=app-configuration-ac-integrations).





 September 2022 

Support for Private endpoints.
Use the ENPush.registerDevice() API to register the device with iOS destination in Event Notifications service.

The following options are supported:



* Register without userId:

/Register iOS devices/
enPush.registerWithDeviceToken(deviceToken: "<apns-device-token>") { response, statusCode, error in
print(response?.id ?? "")
}
* Register with UserId. For userId based notification, the register method accepts one more parameter - userId.

/Register iOS devices/
enPush.registerWithDeviceToken(deviceToken: "<apns-device-token>", withUserId: "userId") { response, statusCode, error in

print(response?.id ?? "")

}

The userId is used to pass the unique userId value for registering for Event Notifications.





 Unregistering from notifications 

Use the following code snippets to unregister from Event Notifications.

enPush.unregisterDevice { response, statusCode, error in
/...../
}

To unregister from the UserId based registration, you must call the registration method. See the Register without userId option in [Register for notifications](https://cloud.ibm.com/docs/event-notifications?topic=event-notifications-en-push-apnsregister-for-notifications).







 Event Notifications destination tags subscriptions 



 Subscribe to tags 

The subscribe API subscribes the device for a given tag. After the device is subscribed to a particular tag, the device can receive notifications that are sent for that tag.

Add the following code snippet to your iOS mobile application to subscribe to a list of tags.

// Subscribe to the given tag
enPush.subscribeToTags(tagName: "<tag_name>") { response, statusCode, error in
/...../
});





 Retrieve subscribed tags
Before you begin, [review the packages that are included with the php runtime](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-runtimesopenwhisk_ref_php) to see whether a dependency of your app is already included with the runtime. If your dependency is not included, you must package it with your app. The following steps assume that you are running the commands on a Linux-based distribution on a processor with AMD64-based architecture.



1. In the root directory, create a index.php and composer.json file.

index.php

<?php
use MpociotChuckNorrisJokesJokeFactory;

function main(array $args) : array
{
$jokes = new JokeFactory();
$joke = $jokes->getRandomJoke();
return ["joke" => $joke];
}
?>

composer.json

{
"require": {
"mpociot/chuck-norris-jokes": "^1.0"
}
}
2. Install all dependencies locally.

composer install

While most php packages install PHP sources on composer install, some packages also install and compile platform-dependent binary file artifacts. Because this environment is Linux AMD64-based, the php install must be executed on a similar platform. Otherwise the action invocations might not succeed.
3. Create an archive that contains all files, including all dependencies.

zip -r action.zip 

Windows users Using the Windows Explorer action for creating the compressed file results in an incorrect file structure. Cloud Functions archive actions must have index.php and composer.json at the root of the archive, but Windows Explorer places it inside a nested folder. Use the zip command instead.
4. Create the Function

ibmcloud fn action create chuckJoke action.zip --kind=php:7.4









 Preparing Java apps 

Before you create an action, get your Java code ready.



 Structuring Java code
Unsupported: Beta version of the CSIStorageCapacity API Migrate manifests and API clients to use the storage.k8s.io/v1 API version, available since Kubernetes version 1.24. For more information, see [Deprecated API Migration Guide - v1.27](https://kubernetes.io/docs/reference/using-api/deprecation-guide/v1-27). 
 Unsupported: Pod seccomp.security.alpha.kubernetes.io/pod and container.seccomp.security.alpha.kubernetes.io annotations Kubernetes no longer supports the pod seccomp.security.alpha.kubernetes.io/pod and container.seccomp.security.alpha.kubernetes.io annotations. These annotations have been deprecated since Kubernetes version 1.19 and has been replaced by the securityContext.seccompProfile field for pods and containers. If your pods rely on these unsupported annotations, update them to use the securityContext.seccompProfile field instead. For more information, see [Create Pod that uses the container runtime default seccomp profile](https://kubernetes.io/docs/tutorials/security/seccomp/create-pod-that-uses-the-container-runtime-default-seccomp-profile). 
 k8s.gcr.io redirect to registry.k8s.io Kubernetes version 1.27 release artifacts are not published to the k8s.gcr.io registry. Furthermore, k8s.gcr.io registry traffic will be redirected to registry.k8s.io. For more information, see [k8s.gcr.io Redirect to registry.k8s.io - What You Need to Know](https://kubernetes.io/blog/2023/03/10/image-registry-redirect/). Note that IBM Cloud Kubernetes Service has already handled this migration action for all resources provided by IBM.
: It helps eliminate issues including skill shortage and acceleration of deployment and go-live when delivering applications to various global sites. Applications can be deployed and run on-premises, addressing security and latency concerns. With unified management, the same applications can be easily rolled out and operated.





 Using cloud for cost and speed when starting new services during development phase and move on-premises once established 

Using Satellite enables applications to be deployed in accordance with which phase the server or application is in. For example, platform applications can be easily deployed on-premises, following a growth in business or in response to heightened security risks.

Pain points:
: Many businesses want to start small on cloud and move to on-premises after the business has grown to a certain scale. They do not want to be locked into a single vendor, as cloud applications cannot be moved on-premises. They need the flexibility to deploy to distributed environments including on-premises in response to the scale of business.

Satellite enables:
: Applications initially developed and delivered on cloud can be moved as-is on-premises. This enables distributed deployment in accordance with the scale of business and acceleration in business speed and mitigation of various risks.





 Deploying applications on-premises, only scaling out to cloud during peak times 

Using Satellite enables applications to be deployed anywhere, on-premises or on cloud. This capability can be used to scale-out (autoscale) to cloud during peak times such as new product releases to optimize cost.

Pain points:
: Clients prefer to run on-premises from cost reduction perspective and only distribute resources to cloud during peak times. The application deployment experience is inconsistent between cloud and on-premises. Clients also want to use scalable containers on-premises.

Satellite enables:
: It enables delivery of container platforms that support DevOps and can be distributed anywhere. Same applications can be instantly moved to cloud only during peak times, optimizing costs.







 Distribution use cases for Satellite 

This use case is applicable to the distribution industry.



 Delivering and integrating store or warehouse digitization solutions for the distribution or retail sectors 

Use Satellite to deliver digitization solutions and integrate with store systems such as store computers and POS, warehouse systems. Leverage AI where applicable.

Pain points:
random-route: true

Now is the point where you might need to set up SSH keys to interactively push code to your remote origin. If you set a passphrase for your SSH key, you're required to enter this code each time you push your changes to the remote origin for your repository.



1. Remove and replace the contents of your webapplication directory with the contents of the directory you modified, COS-WebGalleryStart. Using your finely tuned Git skills, add the files that were deleted and added to the repository with either the CLI or GitHub Desktop. Then, push the changes to the repository origin. In the future, you can make changes to your cloud-based web application just by pushing changes to Git. The CD toolchain will auto-magically restart the server process after cloning your changes and stashing them on the server.



In essence, we've recoded our application, so let's repeat the build process. But this time we use the new Image Gallery code.



 Deploy the app to IBM Cloud Platform. 

To get the starter app with your changes to IBM Cloud Platform, deploy it using the Developer Tools by repeating the same steps that we performed earlier.



1. If you haven't already, or if you restarted or logged out, log in to IBM Cloud Platform by using the login command.

ibmcloud login
2. Set the API Endpoint for your region by using the api command.

ibmcloud api cloud.ibm.com
3. Target the Cloud Foundry aspect of IBM Cloud Platform by using the target command and the --cf option.

ibmcloud target --cf
4. Build the app for delivery that application with the build command (as in the example).

ibmcloud dev build



1. Let's go ahead and test the application locally. This allows you to run the same code locally with the run command.



ibmcloud dev run
5. Deploy the app to IBM Cloud Platform with the deploy command.

ibmcloud dev deploy
In your browser, refresh your login page to verify your changes.







 Displaying the Login Widget with the Android SDK 

You can call preconfigured screens with the [Android client SDK](https://github.com/ibm-cloud-security/appid-clientsdk-android).

Place the following command in your code.

LoginWidget loginWidget = AppID.getInstance().getLoginWidget();
loginWidget.launch(this, new AuthorizationListener() {
@Override
public void onAuthorizationFailure (AuthorizationException exception) {
//Exception occurred
}

@Override
public void onAuthorizationCanceled () {
//Authentication canceled by the user
}

@Override
public void onAuthorizationSuccess (AccessToken accessToken, IdentityToken identityToken, refreshToken: RefreshToken) {
//User authenticated
}
});
Show more



 Sign up 



1. Configure your Cloud Directory [settings](https://cloud.ibm.com/docs/appid?topic=appid-cloud-directorycd-settings) in the GUI. Both Allow users to sign up to your app and Allow users to manage their account from your app must be set to On.
2. Add the following code to your app. When a user signs up for your app from your custom screen, the sign-up flow is started. The following call not only registers the user, but can also send a verification email to complete the registration, depending on your Cloud Directory configurations.

LoginWidget loginWidget = AppID.getInstance().getLoginWidget();
loginWidget.launchSignUp(this, new AuthorizationListener() {
@Override
public void onAuthorizationFailure (AuthorizationException exception) {
//Exception occurred
}

@Override
public void onAuthorizationCanceled () {
To adopt newer versions of those commands, use a newer image version.<br><br>Repository tool integration instance: Name of the repository tool integration instance to use with this build job.<br><br>Repository tool integration type: Type of tool integration to get Gradle information from.<br><br>SonarQube integration instance: Name of the SonarQube integration instance to use with this build job.<br><br>Build command: Build command to run whenever the job runs. In the script field, enter a script or reference scripts that are stored in your project’s source control.<br><br>Working directory: Specifies the directory where the script is run.<br><br>Build archive directory: Specifies the directory that contains the job's output to archive for use by a subsequent stage. 
 npm (Artifactory or Nexus) Builds by using npm with a Nexus or Artifactory repository. Pipeline image version: Runs in a container by using a built-in docker image, which provides various built-in commands. To adopt newer versions of those commands, use a newer image version.<br><br>Repository tool integration instance: The name of the repository tool integration instance to use with this build job.<br><br>Repository tool integration type: The type of tool integration to get Gradle information from.<br><br>SonarQube integration instance: The name of the SonarQube integration instance to use with this build job.<br><br>Build command: The build command to run whenever the job runs. In the Script field, enter a script or reference scripts that are stored in your project’s source control.<br><br>Increment snapshot module version: Supports continuous delivery by incrementing the module version locally based on the contents of the package.json file and the current reported snapshot in the npm registry at the publish step.<br><br>Working directory: Specifies the directory where the script is run.<br><br>Build archive directory: Specifies the directory that contains the job's output to archive for use by a subsequent stage. 







 Deploy stage 

The deploy stage specifies input from a Build stage. The jobs in the deploy stage specify a Deployer type. The following Deployer types are available:



Table 2.
Built-in container image streams, builds, and tooling ([read more](https://blog.cloudowski.com/articles/why-managing-container-images-on-openshift-is-better-than-on-kubernetes/)) Yes 
 Integrated CI/CD with Jenkins Yes 
 Stricter app security context set up by default Yes 
 Simplified Kubernetes developer experience, with an app console that is suited for beginners Yes 
 Supported operating system Ubuntu 18.04 x86_64, 16.04 x86_64 (deprecated) Red Hat Enterprise Linux 7 
 Preferred external traffic networking Ingress Router 
 Secured routes encrypted with Hyper Protect Crypto Services Yes
* For more information about the next-generation models to which you can migrate from each of the deprecated models, see [Previous-generation languages and models](https://cloud.ibm.com/docs/speech-to-text?topic=speech-to-text-models)
* For more information about migrating from previous-generation to next-generation models, see [Migrating to next-generation models](https://cloud.ibm.com/docs/speech-to-text?topic=speech-to-text-models-migrate).
* For more information about all next-generation models, see [Next-generation languages and models](https://cloud.ibm.com/docs/speech-to-text?topic=speech-to-text-models-ng)



Note: When the previous-generation en-US_BroadbandModel is removed from service, the next-generation en-US_Multimedia model will become the default model for speech recognition requests.

Known issue: You cannot change the installed models and voices with the advanced installation options
: Known issue: You currently cannot specify different models or voices with the advanced installation options. The service always installs the default models and voices. For information about changing the models after installation, see Updating models and voices for your Watson Speech services in the Administration topic of [Watson Speech services on IBM Cloud Pak for Data](https://www.ibm.com/docs/en/cloud-paks/cp-data/4.6.x?topic=services-watson-speech).

Known issue: Upgrade to version 4.6.3 can fail to complete
: Known issue: When upgrading to version 4.6.3, the MinIO backup job can fail to be deleted upon completion. If this happens, the solution is to delete the job, after which the upgrade proceeds normally. Perform the following steps to resolve the problem.



1. To determine whether the MinIO backup job remains undeleted, issue the following command:

oc get job --namespace {${PROJECT_CPD_INSTANCE} | grep speech-cr-ibm-minio-backup

The MinIO job that is not deleted is identified by an entry of the following form:
: See [Configuring a highly available application](https://cloud.ibm.com/docs/codeengine?topic=codeengine-deploy-multiple-regions).

Updated versions for buildpacks
: See [Choosing a build strategy](https://cloud.ibm.com/docs/codeengine?topic=codeengine-plan-buildbuild-strategy).





 14 April 2023 

CLI version 1.43.3 released
: See [CLI version history](https://cloud.ibm.com/docs/codeengine?topic=codeengine-cli_versions).





 12 April 2023 

Added information about troubleshooting custom domain mappings
: See [Why isn't my custom domain mapping ready](https://cloud.ibm.com/docs/codeengine?topic=codeengine-ts-app-domain-notready)?

CLI version 1.43.1 released
: See [CLI version history](https://cloud.ibm.com/docs/codeengine?topic=codeengine-cli_versions).

Updated versions for buildpacks
: See [Choosing a build strategy](https://cloud.ibm.com/docs/codeengine?topic=codeengine-plan-buildbuild-strategy).





 05 April 2023 

Updated versions for buildpacks
: See [Choosing a build strategy](https://cloud.ibm.com/docs/codeengine?topic=codeengine-plan-buildbuild-strategy).







 March 2023 

Review the release notes for March 2023.



 30 March 2023 

Added information about troubleshooting images
: 

* See [Debugging images](https://cloud.ibm.com/docs/codeengine?topic=codeengine-troubleshoot-images).



: 

* See [Why can't Code Engine pull an image](https://cloud.ibm.com/docs/codeengine?topic=codeengine-image-cannot-pull)?
Keycloak is packaged as software, which means that you, as the developer, are responsible for maintaining functionality of the product after you download it. You're responsible for hosting, high-availability, compliance, backups, DDoS protection, load balancing, web firewalls, databases, and more.

App ID is a fully managed offering that is provided "as-a-service". This means that IBM takes care of the operation of the service, handles compliancy, availability in multiple zones, SLA, and more. App ID also has an integrated experience with the IBM Cloud Platform that includes native runtimes and services such as the Kubernetes Service, Cloud Functions, and Activity Tracker.





 Can I use the same client ID in more than one application? 

While you technically _can_ use the same credentials in more than one application, it is highly recommended that you do not for several reasons. Foremost, because when you're sharing your ID across applications any type of attack or compromise then affects your entire environment rather than one application. For example, if you're using your ID across three applications and one of them becomes compromised, all three are then compromised. An attacker is able to impersonate any of your apps. The second reason is that when you're using the same client ID in multiple apps, there is no way to differentiate between applications. For example, you're unable to tell which app was used to generate a token.





 How can I update my application to use a new service instance without losing any data 

You can migrate the information in one instance of App ID to another.



1. Create an instance of the service.
2. Duplicate your identity provider configuration by using the GUI.
3. [Migrate your user profiles](https://cloud.ibm.com/docs/appid?topic=appid-user-admin). Known users are exported as a JSON object. Anonymous user's cannot be migrated. You can choose to import the entire object into the new instance or break it up and divide the users as you see fit if you have more than one instance.