vania-janet/multiturn-rag-retrieval-data huggingface dataset:
* [Next steps](https://cloud.ibm.com/docs/codeengine?topic=codeengine-app-local-source-codenextsteps-app-localdeploysource)



[Accessing your app](https://cloud.ibm.com/docs/codeengine?topic=codeengine-access-serviceaccess-service)



* [Access details about your app](https://cloud.ibm.com/docs/codeengine?topic=codeengine-access-serviceaccess-app-details)



* [Accessing app details from the console](https://cloud.ibm.com/docs/codeengine?topic=codeengine-access-serviceaccess-appdetails-ui)
* [Accessing app details with the CLI](https://cloud.ibm.com/docs/codeengine?topic=codeengine-access-serviceaccess-appdetails-cli)



* [Application status](https://cloud.ibm.com/docs/codeengine?topic=codeengine-access-serviceapp-status)



[Updating your app](https://cloud.ibm.com/docs/codeengine?topic=codeengine-update-appupdate-app)



* [Updating your app from the console](https://cloud.ibm.com/docs/codeengine?topic=codeengine-update-appupdate-app-console)
* [Updating your app to use project-only endpoints from the console](https://cloud.ibm.com/docs/codeengine?topic=codeengine-update-appupdate-app-console-projendpt)
* [Updating your app to use private endpoints from the console](https://cloud.ibm.com/docs/codeengine?topic=codeengine-update-appupdate-app-console-privateendpt)
* [Next steps](https://cloud.ibm.com/docs/codeengine?topic=codeengine-migrate-cf-ce-getstartmigrate-cf-ce-next)



[Comparing Cloud Foundry and Code Engine terms](https://cloud.ibm.com/docs/codeengine?topic=codeengine-migrate-cf-ce-termsmigrate-cf-ce-terms)



* [Next steps](https://cloud.ibm.com/docs/codeengine?topic=codeengine-migrate-cf-ce-termsmigrate-cf-ce-next-terms)



[Deploying your application code from a local source](https://cloud.ibm.com/docs/codeengine?topic=codeengine-migrate-cf-ce-localmigrate-cf-ce-local)



* [Objectives](https://cloud.ibm.com/docs/codeengine?topic=codeengine-migrate-cf-ce-localcf-objectives)
* [Prerequisites](https://cloud.ibm.com/docs/codeengine?topic=codeengine-migrate-cf-ce-localcf-prereqs)
* [Log in to IBM Cloud](https://cloud.ibm.com/docs/codeengine?topic=codeengine-migrate-cf-ce-locallocal-log-cloud)
* [Creating a project](https://cloud.ibm.com/docs/codeengine?topic=codeengine-migrate-cf-ce-locallocal-create-project)
* [Creating a directory and source code](https://cloud.ibm.com/docs/codeengine?topic=codeengine-migrate-cf-ce-locallocal-create-dir)
* [Deploying your application](https://cloud.ibm.com/docs/codeengine?topic=codeengine-migrate-cf-ce-localbuild2-application)
2. Find the archive and the image that are associated with your application by searching for your application name.
3. Select the archive and image and delete.







 Next steps 



1. Just starting your migration? Check out [Getting started](https://cloud.ibm.com/docs/codeengine?topic=codeengine-migrate-cf-ce-getstart).
2. [Compare Cloud Foundry terminology with Code Engine](https://cloud.ibm.com/docs/codeengine?topic=codeengine-migrate-cf-ce-terms).
3. Deploying your application code from a local source (current page)
4. Does your application use service bindings? Check out [Migrating your service bindings](https://cloud.ibm.com/docs/codeengine?topic=codeengine-migrate-cf-ce-bind).
5. Learn about [scaling and traffic management](https://cloud.ibm.com/docs/codeengine?topic=codeengine-migrate-cf-ce-scale).
6. Find [Code Engine equivalents to Cloud Foundry commands](https://cloud.ibm.com/docs/codeengine?topic=codeengine-migrate-cf-ce-cmd).
7. Still have questions? Try the [Migrating Cloud Foundry applications to Code Engine FAQ](https://cloud.ibm.com/docs/codeengine?topic=codeengine-migrate-cf-ce-faq).



Other information



* Find out about [Code Engine pricing](https://cloud.ibm.com/docs/codeengine?topic=codeengine-pricing).
* Try other [Code Engine tutorials](https://cloud.ibm.com/docs?tab=tutorials&tags=codeengine&page=1&pageSize=20).
* Explore other [Code Engine topics](https://cloud.ibm.com/docs/codeengine?topic=codeengine-learning-paths).
For more information about how to connect devices, applications, and gateway clients to your Watson IoT Platform instance, see the corresponding topics in the Watson IoT Platform product documentation.



* [Application development ![External link icon](https://cloud.ibm.com/docs-content/v1/content/icons/launch-glyph.svg)](https://www.ibm.com/support/knowledgecenter/SSQP8H/iot/platform/applications/app_dev_index.html)
* [Device development ![External link icon](https://cloud.ibm.com/docs-content/v1/content/icons/launch-glyph.svg)](https://www.ibm.com/support/knowledgecenter/SSQP8H/iot/platform/devices/device_dev_index.html)
* [Gateway development ![External link icon](https://cloud.ibm.com/docs-content/v1/content/icons/launch-glyph.svg)](https://www.ibm.com/support/knowledgecenter/SSQP8H/iot/platform/gateways/gw_dev_index.html)
If you want to use [journal devices](https://docs.portworx.com/install-with-other/operate-and-maintain/performance-and-tuning/tuning/), choose from the following options. Journal devices allow Portworx to write logs directly to a local disk on your worker node.



* [Attach](https://cloud.ibm.com/docs/containers?topic=containers-utilitiesvpc_cli_attach) an additional 3 GB disk to at least 3 worker nodes in your cluster and find the device path. To find the device path after you attach the disk, log in to your worker node and run lsblk to list the devices on that node.
* Select a device on a worker node where you want Portworx to create the journal.



3. If you want to use a specific device for the internal Portworx KVDB, choose from the following options.



* Attach an additional disk to at least 3 worker nodes use for the KVDB. [Manually add](https://cloud.ibm.com/docs/containers?topic=containers-utilitiesmanual_block) a 3 GB block storage device to at least 3 worker nodes in your cluster and find the device path. To find the device path after attaching the disk, log in to your worker node and run lsblk to list the devices on that node.
* Select one of the block storage devices that you added earlier to use for the KVDB and find the device path. To find the device path after attaching the disk, log in to your worker node and run lsblk to list the devices on that node.



4. Continue with your Portworx setup by [Setting up a key-value store for Portworx metadata](https://cloud.ibm.com/docs/containers?topic=containers-storage_portworx_kv_store).







 Satellite clusters 

Satellite



1. [Create a Satellite location](https://cloud.ibm.com/docs/satellite?topic=satellite-locations).
2.
In the IBM Knowledge Center for Db2, the documentation links provided refer to specific pages on an IBM Db2 version. You can switch to the correct version by clicking the "Change version or product" in the upper left area of the IBM Knowledge Center.





 SAP on IBM Db2 using Intel Bare Metal 

See [SAP Note 2414097 - SAP Applications on IBM Cloud Classic Infrastructure environment](https://launchpad.support.sap.com//notes/2414097) for supported IBM Db2 database versions.

A sample configuration is shown in:



* [Quick Study Tutorial - SAP NetWeaver deployment to Bare Metal on Classic Infrastructure, using RHEL](https://cloud.ibm.com/docs/sap?topic=sap-quickstudy-bm-netweaver-rhel)
* [Quick Study Tutorial - SAP NetWeaver deployment to Bare Metal on Classic Infrastructure, using Windows Server](https://cloud.ibm.com/docs/sap?topic=sap-quickstudy-bm-netweaver-wins)







 SAP on IBM Db2 using Intel Virtual Servers 

See [SAP Note 2927211 - SAP Applications on IBM Cloud Virtual Private Cloud (VPC) Infrastructure environment](https://launchpad.support.sap.com//notes/2927211) for supported IBM Db2 database versions.

A sample configuration is shown in:



* [Quick Study Tutorial - SAP NetWeaver deployment to Intel Virtual Server on VPC Infrastructure, using RHEL](https://cloud.ibm.com/docs/sap?topic=sap-quickstudy-vs-gen2-netweaver-rhel)







 SAP on IBM Db2 using IBM Power Virtual Servers 

This is a complementary offering from IBM Power Systems, with low latency access to IBM Cloud services

See [SAP Note 2855850 - SAP Applications on IBM Power Virtual Servers](https://launchpad.support.sap.com//notes/2855850) for supported IBM Db2 database versions on AIX running on IBM Power Systems Virtual Servers.







 Infrastructure size considerations 

When you use IBM Db2 with SAP applications, follow the general SAP sizing rules as described in the SAP Quick Sizer documentation.
With the sink connector, you can transfer data from Kafka topics into Netezza Performance Serverby using the Kafka JDBC connector.



 Setting up the JDBC Kafka connector 

You must install the driver in Kafka's library by editing plugin.path.



1. Set up Java.

For Kafka to work, you need Java 8 or later; for the JDBC connectors, you need Java 11.

sudo yum install -y java-11-openjdk-headless
2. Copy the Netezza JDBC driver to Kafka libs

cp path/to/nzjdbc3.jar kafka/libs
3. Set up your connector.

In the example, the Aiven connector is used.

a) Download the connector.

curl -SLO https://github.com/aiven/jdbc-connector-for-apache-kafka/releases/download/v6.6.2/jdbc-connector-for-apache-kafka-6.6.2.tar

b) Unpack the package.

tar xvf jdbc-connector-for-apache-kafka-6.6.2.tar

c) Edit plugin.path in Kafka config/connect-[distributed/standalone].properties to point to the extracted folder. With this, Kafka can find and load the plugin and connector jars.
4. Start the distributed connect.

connect-distributed.sh config/connect-distributed.properties

Output:

[2022-06-29 02:29:43,356] INFO Started o.e.j.s.ServletContextHandler@5562c2c9{/,null,AVAILABLE} (org.eclipse.jetty.server.handler.ContextHandler:915)
[2022-06-29 02:29:43,356] INFO REST resources initialized; server is started and ready to handle requests (org.apache.kafka.connect.runtime.rest.RestServer:303)
For further information regarding SAP Landscapes, guidance has been released by IBM Power Systems which provide excellent detailed agnostic information and guidance regarding SAP Landscapes components and setup (which applies to running SAP on any infrastructure, on-premises data centers or Cloud IaaS):



* [SAP on IBM Power Systems Best Practices Guide](https://www-03.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/WP102618) (click the link in the middle of the page)
* [IBM Power Systems Virtualization Operation Management for SAP Applications](http://www.redbooks.ibm.com/abstracts/redp5579.html?Open)
* [SAP HANA on IBM Power Systems and IBM System Storage - Guides](http://www-03.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/WP102502)







 Reviewing any relevant SAP and IBM Cloud documentation 

Review the following documentation to help you determine any prerequisites for the SAP products that you plan to install.

If your organization is new to IBM Cloud, read the following SAP documentation to help with your planning phase and implementation:



* [SAP workloads on IBM Cloud®](https://www.ibm.com/cloud/sap/certified-infrastructure)
* [Get started with IBM Cloud®](https://www.ibm.com/cloud/get-started)
* [Creating an IBM Cloud® account](https://cloud.ibm.com/docs/account?topic=account-account-getting-started)
* [How to create an SAP S-user ID](https://www.youtube.com/watch?v=4wICiRTP8u0) Note that only super administrators or S-users with the required authorization are allowed to create S-user IDs for your company's SAP Customer Number (SCN)
* The [Guide Finder for SAP NetWeaver and ABAP Platform](https://help.sap.com/viewer/nwguidefinder) to search for SAP NetWeaver-related documentation, including installation guides.
: [Deploying Cloud Foundry applications in Code Engine: Getting started](https://cloud.ibm.com/docs/codeengine?topic=codeengine-migrate-cf-ce-tutorial)
: [Migrating your service binding](https://cloud.ibm.com/docs/codeengine?topic=codeengine-migrate-cf-ce-bind)

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







 March 2022 

Review the release notes for March 2022.



 31 March 2022 

Review the release notes for 31 March 2022.

New region!
: Code Engine is supported in a new region: Brazil Sao Paulo (br-sao). See [Regions for Code Engine](https://cloud.ibm.com/docs/codeengine?topic=codeengine-regions).





 23 March 2022 

Review the release notes for 23 March 2022.

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





 18 March 2022 

Review the release notes for 18 March 2022.

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

Added information about registry access secret types
: Types include Code Engine managed secrets and user managed secrets. If no credentials are needed to access the registry, then the access is None. See [Types of registry access secrets](https://cloud.ibm.com/docs/codeengine?topic=codeengine-add-registrytypes-registryaccesssecrets).

Added information about setting max-scale = 0
: Max scale is the maximum number of instances that can be used for an app.
ibmcloud target -g <resource-group>
5. Copy one of the following example command for the template version that you want to use. For more information about the command, see ibmcloud sat storage config create in the [command reference](https://cloud.ibm.com/docs/satellite?topic=satellite-satellite-cli-referencecli-storage-config-create).

Example command to create a version 4.9 configuration.

ibmcloud sat storage config create --location LOCATION --name NAME --template-name odf-local --template-version 4.9 --param "auto-discover-devices=AUTO-DISCOVER-DEVICES" [--param "osd-device-path=OSD-DEVICE-PATH"] --param "num-of-osd=NUM-OF-OSD" [--param "worker-nodes=WORKER-NODES"] --param "odf-upgrade=ODF-UPGRADE" --param "billing-type=BILLING-TYPE" [--param "ibm-cos-endpoint=IBM-COS-ENDPOINT"] [--param "ibm-cos-location=IBM-COS-LOCATION"] [--param "ibm-cos-access-key=IBM-COS-ACCESS-KEY"] [--param "ibm-cos-secret-key=IBM-COS-SECRET-KEY"] --param "cluster-encryption=CLUSTER-ENCRYPTION" --param "iam-api-key=IAM-API-KEY" --param "perform-cleanup=PERFORM-CLEANUP"

Example command to create a version 4.10 configuration.
Check out [Migrating your service bindings](https://cloud.ibm.com/docs/codeengine?topic=codeengine-migrate-cf-ce-bind).
5. Learn about [scaling and traffic management](https://cloud.ibm.com/docs/codeengine?topic=codeengine-migrate-cf-ce-scale).
6. Code Engine equivalents to Cloud Foundry commands (current page)
7. Still have questions? Try the [Migrating Cloud Foundry applications to Code Engine FAQ](https://cloud.ibm.com/docs/codeengine?topic=codeengine-migrate-cf-ce-faq).



Other information



* Find out about [Code Engine pricing](https://cloud.ibm.com/docs/codeengine?topic=codeengine-pricing).
* Try other [Code Engine tutorials](https://cloud.ibm.com/docs?tab=tutorials&tags=codeengine&page=1&pageSize=20).
* Explore other [Code Engine topics](https://cloud.ibm.com/docs/codeengine?topic=codeengine-learning-paths).
For JAVA:

SAP HANA DB configuration for JAVA stack
hana_sid = "HDB"
hana_sysno = "00"
hana_system_usage = "custom"
hana_components = "server"

SAP HANA Installation kit path
kit_saphana_file = "/storage/HANADB/51054623.ZIP"

SAP system configuration
sap_sid = "JV1"
sap_ascs_instance_number = "01"
sap_ci_instance_number = "00"

SAP S4HANA APP Installation kit path
kit_sapcar_file = "/storage/NW75HDB/SAPCAR_1010-70006178.EXE"
kit_swpm_file = "/storage/NW75HDB/SWPM10SP31_7-20009701.SAR"
kit_sapexe_file = "/storage/NW75HDB/SAPEXE_801-80002573.SAR"
kit_sapexedb_file = "/storage/NW75HDB/SAPEXEDB_801-80002572.SAR"
kit_igsexe_file = "/storage/NW75HDB/igsexe_13-80003187.sar"
kit_igshelper_file = "/storage/NW75HDB/igshelper_17-10010245.sar"
kit_saphotagent_file = "/storage/NW75HDB/SAPHOSTAGENT51_51-20009394.SAR"
kit_hdbclient_file = "/storage/NW75HDB/IMDB_CLIENT20_009_28-80002082.SAR"
kit_sapjvm_file = "/storage/NW75HDB/SAPJVM8_73-80000202.SAR"
kit_java_export = "/storage/NW75HDB/export"

For ABAP:

HANA DB configuration for ABAP stack
hana_sid = "HDB"
hana_sysno = "00"
The sample application is called enterprise-app, and is located [here](https://github.com/konveyor/move2kube-demos/tree/main/samples/enterprise-app/src) There are also a [number of other Tutorials and Examples you can explore.](https://move2kube.konveyor.io/tutorials)

The Enterprise-App consists of several microservices that work together to create a retail application that handles various customer transactions for the business. It is a non-trival application that shows how several components working together in an application can be migrated together.

Review the details of the application - including the components Inventory, Orders, Customers, Gateway, and Frontend:



* [Inventory](https://github.com/konveyor/move2kube-demos/tree/main/samples/enterprise-app/src/inventory)
* [Orders](https://github.com/konveyor/move2kube-demos/tree/main/samples/enterprise-app/src/orders)
* [Customers](https://github.com/konveyor/move2kube-demos/tree/main/samples/enterprise-app/src/customers)
* [Gateway](https://github.com/konveyor/move2kube-demos/tree/main/samples/enterprise-app/src/gateway)
* [Frontend](https://github.com/konveyor/move2kube-demos/tree/main/samples/enterprise-app/src/frontend)



You don't have to deploy all components if you don't want to. Inventory, Orders, and Customers are underlying microservices. They are connected to by Gateway and Frontend connects to Gateway. You can see the layout and connection information [here](https://github.com/konveyor/move2kube-demos/tree/main/samples/enterprise-app/src).
* OS configuration according to SAP guidance.
* OS package updates according to SAP guidance, which includes updates to specified OS kernel versions (for example, RHEL4SAP 7.6 ships with 3.10.0-957.el7.x86_64. However, SAP requires the 1.3 version 3.10.0-957.1.3.el7.x86_64).







 OS for Virtual Servers on VPC Infrastructure 

For a list of operating systems and databases available for SAP NetWeaver-based system deployments, see [SAP Note 2927211](https://launchpad.support.sap.com//notes/2927211).

An SAP S-user ID is required to access the SAP Note.





 OS for IBM Power Virtual Servers 

For the Linux® versions to deploy for SAP HANA, see [SAP Note 2947579 - SAP HANA on IBM Power Virtual Servers](https://launchpad.support.sap.com//notes/2947579). An SAP S-user ID is required to access the SAP Note. The OS image is provided by IBM Power Systems Virtual Servers, and the licensing for Linux is covered through a "bring your own license" (BYOL) model.

For the version of IBM AIX or Linux on Power to deploy for SAP NetWeaver-based systems, see [SAP Note 2855850 - SAP Applications on IBM Power Virtual Servers](https://launchpad.support.sap.com//notes/2855850). An SAP S-user ID is required to access the SAP Note. License fees for AIX are covered by your monthly billing rate.

OS Packages update server with IBM Power Power Virtual Servers:



* For SAP NetWeaver you can use publicly available AIX SUMA or SUSE update repositories, or use your own AIX NIM or SUSE RMT servers.
* For SAP HANA you can use publicly available SUSE update repositories, or use your own private SUSE RMT servers.





Table 1. Operating systems for IBM Power virtual servers on SAP HANA

 Operating system for SAP HANA Operating system image (Bring your own license) Operating system image (IBM subscription)
IBM Blockchain Platform SaaS PayGo customers can transition their license to IBM Support for Hyperledger Fabric during any month, without any existing long-term customer commitment, through coordination with their IBM Blockchain Support team or IBM Account Representative.

IBM Blockchain Platform SaaS subscription customers will be able to transition their license to IBM Support for Hyperledger Fabric at the end of their current subscription commitment, or before July 31, 2023 (whichever comes first), with assistance from their IBM Blockchain Support team or IBM Account Representative.





 Planning and Considerations 

IBM Support for Hyperledger Fabric supports the Hyperledger Fabric v2.x codebase (the v1.4 codebase goes out of support in April, 2023) so existing environments need to utilize v2.x component images.

Documentation for the IBM Support for Hyperledger Fabric is a current IBM product offering; the documentation is available at [https://www.ibm.com/docs/en/hlf-support/1.0.0](https://www.ibm.com/docs/en/hlf-support/1.0.0).

Please note that the migration to IBM Support for Hyperledger Fabric will update the ingress class used in the cluster hosting the components. Applications sharing or using these ingresses may need changes post-migration to use the updated ingresses.

Also note that the Fabric Operations Console that will be created in the cluster will use the default StorageClass assigned in the cluster.





 Next steps 

A tool will be provided that migrates your IBM Blockchain Platform console from an IBM-hosted environment to your Kubernetes cluster. Before running this tool, your Kubernetes cluster must be preconfigured with the required Hyperledger Fabric blockchain components, which are your peers, ordering nodes, and certificate authorities. As part of this process, the images used for these components will be switched to images provided for IBM Support for Hyperledger Fabric.

While IBM is testing this migration tool internally for production usage, there are steps you can take now to prepare for your migration to IBM Support for Hyperledger Fabric, as follows:



1. Upgrade any blockchain components that are using Hyperledger Fabric v1.4:
kubectl apply -f pvc.yaml
3. Verify that your PVC is created and bound to a persistent volume (PV). This process might take a few minutes.

kubectl get pvc









 Mounting the volume to your app 

To access the storage from your app, you must mount the PVC to your app.



1. Create a configuration file for a deployment that mounts the PVC.

For tips on how to deploy a stateful set with Portworx, see [StatefulSets](https://docs.portworx.com/portworx-install-with-kubernetes/application-install-with-kubernetes/cassandra/). The Portworx documentation also includes examples for how to deploy [Cassandra](https://docs.portworx.com/portworx-install-with-kubernetes/application-install-with-kubernetes/cassandra/), [Kafka](https://docs.portworx.com/portworx-install-with-kubernetes/application-install-with-kubernetes/kafka-with-zookeeper/), [ElasticSearch with Kibana](https://docs.portworx.com/operations/operate-kubernetes/application-install-with-kubernetes/elastic-search-and-kibana/), and [WordPress with MySQL](https://docs.portworx.com/portworx-install-with-kubernetes/application-install-with-kubernetes/wordpress/).

apiVersion: apps/v1
kind: Deployment
metadata:
name: <deployment_name>
labels:
app: <deployment_label>
spec:
selector:
matchLabels:
app: <app_name>
template:
metadata:
labels:
app: <app_name>
spec:
schedulerName: stork
containers:
- image: <image_name>