vania-janet/multiturn-rag-retrieval-data huggingface dataset:
DB-PROFILE = "bx2-4x16"
DB-IMAGE = "ibm-redhat-8-4-amd64-sap-applications-4" For any manual change in the Terraform code, you have to make sure that you use a certified image based on the SAP NOTE: 2927211.

 SAP APPs VSI variables:
APP-HOSTNAME = "sapnwapp"
APP-PROFILE = "bx2-4x16"
APP-IMAGE = "ibm-redhat-8-4-amd64-sap-applications-4" For any manual change in the Terraform code, you have to make sure that you use a certified image based on the SAP NOTE: 2927211.
4. Customize your SAP system configuration. In the same file, input.auto.tfvars, edit the SAP system configuration variables that are passed to the Ansible automated deployment.

For descriptions of the variables, see the [README file](https://github.com/IBM-Cloud/sap-netweaver-abap-db2-distributed/blob/main/README.md).

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

 Kits paths
kit_sapcar_file = "/storage/NW75DB2/SAPCAR_1010-70006178.EXE"
kit_swpm_file = "/storage/NW75DB2/SWPM10SP37_2-20009701.SAR"
kit_saphotagent_file = "/storage/NW75DB2/SAPHOSTAGENT51_51-20009394.SAR"
kit_sapexe_file = "/storage/NW75DB2/SAPEXE_800-80002573.SAR"
kit_sapexedb_file = "/storage/NW75DB2/SAPEXEDB_800-80002603.SAR"
You can restart squid by using the sudo systemctl restart squid command.







 Step 5: Customizing the VMs by using the cloud-init script (RHEL and SLES) 

You can customize your RHEL and SLES VMs by running the cloud-init script.



1. Log in to your RHEL or SLES VM, by using the ssh root@<External IP”> command.
2. A readme file is generated in the /usr/share/powervs-fls/powervs-fls-readme.md location. For relevant information about variables that are required to run the cloud-init script, see the readme file.
3. Run the cloud-init script that is located in the /usr/local/bin/ location. Run the script as root. You can switch the user to root by using the sudo su root command.

a. For RHEL, run the following command:

. /usr/local/bin/rhel-cloud-init.sh -a Activation_Key -u Capsule_server_url -p Proxy_IP_and_port -o Org -t Deployment type

For information about the cloud-init script options and values, refer to the readme file that is generated in step 2 (/usr/share/powervs-fls/powervs-fls-readme.md location).

-a = activation key

-u = the URL of the RHEL capsule server you are registering against

-p = "private_ip_of_powervs_vm":3128

-o = organization associated with the activation key

-t = deployment type of this VM (RHEL, RHEL-SAP, RHEL-SAP-NETWEAVER)

b. For SLES, run the following command:

. /usr/local/bin/sles-cloud-init.sh -s RMT_Server_address -p private_ip_of_proxy_vm:3128

-s = the URL of the SLES Repository Mirroring Tool (RMT) server that you are using for registration
From the Enrichments page of a collection, remove the enrichment from any fields where it is applied.
4. Click Apply changes and reprocess, and then wait for the system to process the documents in your collection without the enrichment.
5. Repeat the previous step for every collection in every project where the enrichment is used.

Remember, a custom enrichment can be used by any collection in any project within a single Discovery service instance.
6. From any of the collections that used the enrichment, open the Enrichments page, and then click the delete icon to delete the enrichment.



The custom enrichment is removed from the Enrichments list everywhere in this service instance.





 Using the API to manage enrichments 

To apply an enrichment to data by using the API, complete the following steps:



1. First, you must know the unique ID of the enrichment that you want to apply. For more information, see [Enrichment IDs](https://cloud.ibm.com/docs/discovery-data?topic=discovery-data-manage-enrichmentsenrichments-id).
2. Use the Create collection or Update collection methods to apply an enrichment to the documents in a collection. For more information, see [Apply enrichment by using the API](https://cloud.ibm.com/docs/discovery-data?topic=discovery-data-manage-enrichmentsenrichments-api-task)





 Enrichment IDs 

If you want to apply a custom enrichment that you created for one collection to another collection, you must know the unique ID that was generated for the enrichment when it was created. Use the API to [list enrichments](https://cloud.ibm.com/apidocs/discovery-datalistenrichments) from the project where the custom enrichment is in use. The list that is returned includes enrichment ID information.

For prebuilt enrichments, the unique IDs do not change. The following table lists the IDs that are associated with each prebuilt enrichment type and identifies the collection languages for which the enrichment is supported. An enrichment cannot be applied to a collection unless the collection language is supported by the enrichment.



Prebuilt enrichment IDs

 Name Enrichment ID Supported languages
Use that url to verify that the app is running.





 Pipeline customization 

Custom scripts are extension points in the pipeline where adopters, teams, and users can provide scripts to run custom tasks that are required by their continuous integration and continuous deployment strategies.

Custom scripts control the pipeline stages. You can use a configuration file (pipeline-config.yaml) to configure the behavior of stages, script content, and the base image that runs the scripts. The scripts and configuration for pipeline stages are loaded from a Git repository (repo) that can either be the application (app) repo (similar to .travis.yml or Jenkinsfile) or a custom repo.

More detailed information on customizing the CI pipelines can be found [here](https://cloud.ibm.com/docs/devsecops?topic=devsecops-custom-scripts).





 Wrapping up 

By completing the CI part of this tutorial, you:



* Created a DevSecOps CI toolchain
* Modified some code in the application repository
* Ran the ci-pr pipeline before you merge your changes
* Ran the ci-pipeline to build, test, and deploy your changes to your dev environment.









 Next steps 

Continue to [Part 3: Set up a Continuous Deployment (CD) toolchain](https://cloud.ibm.com/docs/devsecops?topic=devsecops-tutorial-cd-toolchain).
* [Customizing the service](https://cloud.ibm.com/docs/text-to-speech?topic=text-to-speech-service-featuresfeatures-customization) describes the more advanced topic of customization, which you can use to create custom models that contain dictionaries of words and their translations for specific languages.
* [Using Tune by Example](https://cloud.ibm.com/docs/text-to-speech?topic=text-to-speech-service-featuresfeatures-tune-by-example) introduces the Tune by Example feature that lets you create custom prompts. You can control the intonation, cadence, and stress of the synthesized text for your prompts.
* [Using software development kits](https://cloud.ibm.com/docs/text-to-speech?topic=text-to-speech-service-featuresfeatures-sdks) provide links to the SDKs that are available to simplify application development in many programming languages.
* [Learning more about application development](https://cloud.ibm.com/docs/text-to-speech?topic=text-to-speech-service-featuresfeatures-learn) provides links to help you get started with Watson services and understand authentication.
DB-PROFILE = ""bx2-4x16"
DB-IMAGE = "ibm-redhat-8-6-amd64-sap-applications-2"
APP-HOSTNAME = "sapnwapp"
APP-PROFILE = "bx2-4x16"
APP-IMAGE = "ibm-redhat-8-6-amd64-sap-applications-2"

SSH_KEYS		= [ "r010-57bfc315-f9e5-46bf-bf61-d87a24a9ce7a" , "r010-3fcd9fe7-d4a7-41ce-8bb3-d96e936b2c7e" ]
5. Customize your SAP system configuration, standard or distributed. In the same file, input.auto.tfvars, edit the SAP system configuration variables that are passed to the Ansible automated deployment. For descriptions of the variables, see the readme file.

For standard deplyoment:

SAP system configuration for standard deployment
sap_sid	= "NWD"
sap_ci_instance_number = "00"
sap_ascs_instance_number = "01"

Kits paths
kit_sapcar_file = "/storage/NW75SYB/SAPCAR_1010-70006178.EXE"
kit_swpm_file = "/storage/NW75SYB/SWPM10SP31_7-20009701.SAR"
kit_saphotagent_file = "/storage/NW75SYB/SAPHOSTAGENT51_51-20009394.SAR"
kit_sapexe_file = "/storage/NW75SYB/SAPEXE_900-80002573.SAR"
kit_sapexedb_file = "/storage/NW75SYB/SAPEXEDB_900-80002616.SAR"
kit_igsexe_file = "/storage/NW75SYB/igsexe_13-80003187.sar"
* -match is the matching zone or hostname.
* --dns-svcs is the upstream DNS servers to be forwarded to.
* -i, --instance is the instance name or ID. If this is not set, the context instance specified by dns instance-target INSTANCE is used instead.
* --output specifies output format. Currently, JSON is the only supported format.







 Updating custom resolver forwarding rules using the API 

To update a custom resolver forwarding rule using the API, follow these steps:



1. Set up your API environment with the correct variables.
2. Store the following values in variables to be used in the API command:



* instance_id, which is the unique identifier of a service instance.
* resolver_id, which is the unique identifier of a custom resolver.
* rule_id, which is the unique identifier of a forwarding rule.
* X-Correlation-ID, which is a string that uniquely identifies a request.



3. When all variables are initiated, update your custom resolver forwarding rule:

{
"description": "forwarding rule",
"match": "example.com",
"forward_to": [
"161.26.0.7"
]
}
Note: You can select Default for one Catalog.

d. Optional: Click Endpoints, and populate the following fields:



* Custom Gateway URL: In the Custom Gateway URL text field, enter a URL. You use the Custom Gateway URL if you want to achieve custom branding of URLs for APIs that are deployed to API Connect, rather than using the default URL that API Manager generates. By default, the API Connect gateway URL has the following format:

https://gateway_cluster_hostname/organization_name/Catalog_name

However, you can override the default by specifying a URL that is more appropriate for your enterprise; for example, https://api.mycompany.com. Any API endpoints that are displayed in the Developer Portal reflect the custom URL.

Notes:



* This option is not available for the Lite plan.
* To set up the URL redirect, contact API Connect Support.
* You must configure a DNS entry that maps your custom host name and domain to the default gateway URL.
* If you want the endpoints of an API to reflect your custom gateway URL, configure the API to be enforced by the API Connect gateway. For more information, see [Specifying an alternative host for an API](https://www.ibm.com/support/knowledgecenter/en/SSFS6T/com.ibm.apic.toolkit.doc/task_apionprem_creating_apis.htmltask_tq2_11r_xt__enforce_step).
* Ensure that the same custom gateway URL is not applied to multiple Catalogs as the behavior in that scenario is undefined. TIP: When you call the API, you can also set the HTTP host header on the API request to the value that you specified in the Custom Gateway URL field.



* Custom API URL In the Custom API URL text field, enter the URL. You use the Custom API URL to specify the URL for APIs that are deployed to a third-party gateway.

The Custom API URL represents the endpoint by which the API is known externally.
kit_sapexe_file = "/storage/NW75SYB/SAPEXE_900-80002573.SAR"
kit_sapexedb_file = "/storage/NW75SYB/SAPEXEDB_900-80002616.SAR"
kit_igsexe_file = "/storage/NW75SYB/igsexe_13-80003187.sar"
kit_igshelper_file = "/storage/NW75SYB/igshelper_17-10010245.sar"
kit_ase_file = "/storage/NW75SYB/51055443_1.ZIP"
kit_export_dir = "/storage/NW75SYB/EXP"

For distributed deployment

SAP system configuration for distributed deployment
sap_sid = "NWD"
sap_ci_instance_number = "00"
sap_ascs_instance_number = "01"

Kits paths
kit_sapcar_file = "/storage/NW75SYB/SAPCAR_1010-70006178.EXE"
kit_swpm_file = "/storage/NW75SYB/SWPM10SP31_7-20009701.SAR"
kit_saphotagent_file = "/storage/NW75SYB/SAPHOSTAGENT51_51-20009394.SAR"
kit_sapexe_file = "/storage/NW75SYB/SAPEXE_900-80002573.SAR"
kit_sapexedb_file = "/storage/NW75SYB/SAPEXEDB_900-80002616.SAR"
kit_igsexe_file = "/storage/NW75SYB/igsexe_13-80003187.sar"
kit_igshelper_file = "/storage/NW75SYB/igshelper_17-10010245.sar"
kit_ase_file = "/storage/NW75SYB/51055622_1.ZIP"
[DOI Toolchain ID](https://cloud.ibm.com/docs-content/v1/content/5eb88a2575e30e316dbb83829c7f4c8b1ddbc67c/devsecops/images/devsecops_set-up_devops_insight_orig.png)

Figure 18. DOI Toolchain ID

You can copy the Toolchain ID from the URL of your toolchain. A toolchain's URL follows this pattern: https://cloud.ibm.com/devops/toolchains/<toolchain-ID-comes-here>?env_id=ibm:yp:us-south

For example, if the URL is: https://cloud.ibm.com/devops/toolchains/aaaaaaa-bbbb-cccc-dddd-eeeeeeeeeeee?env_id=ibm:yp:us-south then the toolchain's ID is: aaaaaaa-bbbb-cccc-dddd-eeeeeeeeeeee.

Note: Include the ID only, not the full URL.

You can also set a target environment for the DOI interactions. This parameter is optional. If you provide this parameter, it is used instead of the target environment from the inventory.





 DevOps insights 

Use this option to create a new instance of DevOps Insights to be used for the toolchain. No configuration is required and the toolchain creates a new instance of DevOps Insight if this option is selected. The CI pipeline automatically uses the insights instance that is included in the toolchain.





 Delivery pipeline private worker 

The [Delivery Pipeline Private Worker](https://cloud.ibm.com/docs/ContinuousDelivery?topic=ContinuousDelivery-private-workers) tool integration connects with one or more private workers that can run Delivery Pipeline workloads in isolation.





 SonarQube 

Configure SonarQube as the static code analysis tool for the toolchain.
The audio file, audio1.wav, is passed as the body of the request, and the resource is given the name audio1.

IBM Cloud

curl -X POST -u "apikey:{apikey}" --header "Content-Type: audio/wav" --data-binary @audio1.wav "{url}/v1/acoustic_customizations/{customization_id}/audio/audio1"

IBM Cloud Pak for Data

curl -X POST --header "Authorization: Bearer {token}" --header "Content-Type: audio/wav" --data-binary @audio1.wav "{url}/v1/acoustic_customizations/{customization_id}/audio/audio1"
* This example adds an archive-type resource to the specified custom acoustic model. The Content-Type header identifies the type of the archive as application/zip. The Contained-Contented-Type header indicates that all files that are contained in the archive have the format audio/l16 and are sampled at a rate of 16 kHz. The archive file, audio2.zip, is passed as the body of the request, and the resource is given the name audio2.

IBM Cloud

curl -X POST -u "apikey:{apikey}" --header "Content-Type: application/zip" --header "Contained-Content-Type: audio/l16;rate=16000" --data-binary @audio2.zip "{url}/v1/acoustic_customizations/{customization_id}/audio/audio2"

IBM Cloud Pak for Data

curl -X POST --header "Authorization: Bearer {token}" --header "Content-Type: application/zip" --header "Contained-Content-Type: audio/l16;rate=16000" --data-binary @audio2.zip "{url}/v1/acoustic_customizations/{customization_id}/audio/audio2"



The method also accepts an optional allow_overwrite query parameter to overwrite an existing audio resource for a custom model. Use the parameter if you need to update an audio resource after you add it to a model.
primary-certificate-example-pem-format The certificate that is issued by your SAML identity provider. It is used for signing and validating SAML assertions. All providers are different, but you might be able to download the signing certificate from your identity provider. The certificate must be in .pem format. 
 DefaultRelayState The initial value for RelayState. This variable is configured in your identity provider's settings. This variable can be used for the redirect URL instead of idpRedirectUrl during SAML requests from your identity provider. If you set both variables, the value of DefaultRelayState takes precedence. IdP-initiated login fails if you don't set one of these variables. 
 idpInitEnabled A boolean to indicate whether you want to enable IdP initiated login. 
 idpRedirectUrl This field's value can be null, a string that is empty, or a valid http or https redirect URL. Note: If this field's value is null, then you must set the DefaultRelayState as the redirect URL. If you set both variables, the value of DefaultRelayState takes precedence. IdP-initiated login fails if you don't set one of these variables. 
 Optional: secondary-certificate-example-pem-format The backup certificate that is issued by your SAML identity provider. It is used if signature validation fails with the primary certificate. Note: If the signing key remains the same, App ID does not block authentication for expired certificates. 
 Optional: authnContext The authentication context is used to verify the quality of the authentication and SAML assertions. You can add an authentication context by adding a class array and comparison string to your code. BE sure to update both the class and comparison parameters with your values. For example, a class parameter might look similar to urn:oasis:names:tc:SAML:2.0:ac:classes:YourChosenClassValue. 
 Optional: signRequest The signRequest flag provides the capability to send a signed SAML request to an identity provider that is signed by using the tenant's SAML signing private key.
For more information, see [Customizing the default settings](https://cloud.ibm.com/docs/containers?topic=containers-vpc-blockvpc-customize-default).





 19 September 2019 

Sending custom Ingress certificates to legacy clients
: Added [steps](https://cloud.ibm.com/docs/containers?topic=containers-comm-ingress-annotations) for ensuring that your custom certificate, instead of the default IBM-provided certificate, is sent by the Ingress ALB to legacy clients that don't support SNI.





 16 September 2019 

CLI change log
: Updated the IBM Cloud Kubernetes Service CLI plug-in change log page for the release of version 0.4.23.

IBM Cloud Activity Tracker events
: Added information about [which Activity Tracker location your events are sent to](https://cloud.ibm.com/docs/containers?topic=containers-at_eventsat-ui) based on the IBM Cloud Kubernetes Service location where the cluster is located.

Version change logs
: Worker node patch updates are available for Kubernetes [1.15.3_1517](https://cloud.ibm.com/docs/containers?topic=containers-115_changelog1153_1517_worker), [1.14.6_1533](https://cloud.ibm.com/docs/containers?topic=containers-114_changelog1146_1533_worker), [1.13.10_1536](https://cloud.ibm.com/docs/containers?topic=containers-113_changelog11310_1536_worker), and [1.12.10_1567](https://cloud.ibm.com/docs/containers?topic=containers-112_changelog11210_1567_worker).





 13 September 2019 

Entitled software
"hf.Registrar.DelegateRoles": "",
"hf.Revoker": true,
"hf.IntermediateCA": true,
"hf.GenCRL": true,
"hf.Registrar.Attributes": "",
"hf.AffiliationMgr": true
}
}
}
},
"csr": {
"names":
{
"C": "US",
"ST": "New York",
"L": null,
"O": "Big business",
"OU": "Big department"
}
] ,
}
}
}"
Show more
For more information about deploying a customized CA, and which fields you can customize after a CA is created, see Customizing a CA configuration]] ! ! .<-- </section "id="section-example-creating-a-custom-certificate-authority" "> --><-- <section "id="section-create-a-high-availability-ca" "> --> Create a high availability CA You can use configuration override to deploy a CA with replica sets that share the same database, ensuring that the data is consistent between replicas. This configuration ensures that the CA will be available in the event of a Kubernetes worker node failure. To deploy an HA CA, you need to deploy a PostgreSQL database on IBM Cloud or in the environment of your choice. You then need to use the information about your database to create a connection file that will be used by your CA. For more information, see Building a high availability Certificate Authority]] .To use the APIs to deploy an HA CA, you need to provide the database connection file to the "db" section of the config override JSON string. For example, the API request below will deploy a CA with two replicas that connect to a database located on IBM Cloud. curl -X POST 
https://<API endpoint>/ak/api/v2/kubernetes/components/fabric-ca
documentationUrl optional, updatable String documentation_url The URL of this tool integration's documentation. 
 imageUrl optional, updatable String image_url The URL of the icon that is displayed on the tool integration card in the graphical UI. 
 lifecyclePhase required, updatable String lifecycle_phase The lifecycle phase of the IBM Cloud Garage Method that is the most closely associated with this tool integration. 
 name required, updatable String name The name of this tool integration. 
 type required, updatable String type The type of tool that this custom tool is integrating with. 







 Learn more about the custom tool (Other Tool) 

To learn more about the custom tool, take this tutorial:



* [Add a custom tool integration to a toolchain](https://www.ibm.com/cloud/architecture/tutorials/add-a-custom-tool-integration-to-a-toolchain)
Test Changes X 
 Go Live X 







 Post Live MAS-Dedicated Activities 

This is the support for customers after the go live. Any new issue is investigated and resolved and then the client moves to steady state.





 Roles and Responsibilities 

Both IBM and the client have critical roles in the successful transition to the Maximo Application Suite Dedicated offering. These responsibilities are summarized in the attached spreadsheet below (MAS-Dedicated Migration Swimlanes). At a high level, IBM is responsible for the technical components of the migration and the client would be responsible for ensuring business processes are working, custom and unique features of their implementation are identified, and updates to integration's and accounted for in the plan.

If the source database is being converted from another platform (for example Oracle or SQLServer) it is the customers responsibility to perform validation of the converted DB2 database and correct any issues identified before providing to the SRE team for import into the target MAS-Dedicated environment.

IBM and the customer share the responsibility to ensure the appropriate personnel are available to meet the agreed project plan.





 Additional Notes 





 Database Backup Image/Export 

The IBM SRE team would prefer a database backup image provided the image is from the same database version as you are running in MAS-Dedicated. We can accept/use an export done using (db2move/db2look). We would like you to send the export as well as backup image if possible. The database backup image and export files should be uploaded to the following IBM Cloud COS bucket. The bucket detail and its connection detail will be send via welcome letter.

Bucket name: masms-XX-X-XXX-XXXXX-"InstanceName"-XX-XXX-cust-files





 Doclink and Attachment Files 

Doclink and Attachment Files should be uploaded to the following IBM Cloud COS bucket. Please upload your doclinks directory with all required subfolders The structure of these files and directories will be maintained when copied to the Manage server location.

Bucket name: masms-XX-X-XXX-XXXXX-"InstanceName"-XX-XXX-cust-files

Note: