vania-janet/multiturn-rag-retrieval-data huggingface dataset:
./ManualRegisterConnector.ps1 -ADDomainName {ADDomainName} -ADServerName {ADServerName} -ActiveDirectoryUserName {ActiveDirectoryUserName} -ActiveDirectoryPassword {ActiveDirectoryPassword} -PreferredDnsServer {PreferredDnsServer}

Replace the contents of the {} with the values for your system.

If you need to use a different APIClientID and APIClientSecret enter:

./ManualRegisterConnector.ps1 -APIClientID {APIClientID} -APIClientSecret {APIClientSecret} -ADDomainName {ADDomainName} -ADServerName {ADServerName} -ActiveDirectoryUserName {ActiveDirectoryUserName} -ActiveDirectoryPassword {ActiveDirectoryPassword} -PreferredDnsServer {PreferredDnsServer}

Replace the contents of the {} with the values for your system.









 Extended (Site-to-Site) 

Domain controller latency issues

The Extended (Site-to-Site) option does not have a domain controller (DC) on IBM Cloud. Sites that do not have domain controllers are less efficient because of slow AD authentication and GPO processing. If you have sites with no DCs, you can limit the latency issues if you:



* Create the AD subnets for these sites and link them to the closest site with a DC. The sites reach the on-premises side for AD authentication and GPO processing.
* Enable GPO processing over [slow links detection](https://technet.microsoft.com/en-us/library/cc781031%28v=ws.10%29.aspx?f=255&MSPPError=-2147217396).



Other Active Directory Best practices include:



* Establish as a site every geographic area that requires fast access to the most recent directory information. Establishing areas that require immediate access to up-to-date Active Directory information as separate sites provide the resources that are required to meet your needs.
If you have issues, uninstall any Array programs by using the Windows Control Panel, restart, and then reconnect.

MotionPro does not work on Windows 8 RT. To download the MotionPro version compatible with Windows 11, click [here](https://support.arraynetworks.net/prx/000/http/supportportal.arraynetworks.net/downloads/motionpro/Windows/Win11/MotionProSetup_win11.zip).





 Linux stand-alone client 



* To install and set up MotionPro on Linux, follow these steps:



1. Download: wget --no-check-certificate [latest MotionPro link]
2. Make the file executable. For example: chmod +x MotionPro_Linux_Ubuntu_x64_build-9.sh
3. Run as a superuser. For example: sudo ./MotionPro_Linux_Ubuntu_x64_build-9.sh



* To launch the GUI:



$ MotionPro -- This launches the GUI for the VPN client. Proceed to set up the VPN profile.



* To launch MotionPro using a command line:



cd /opt/MotionProsudo ./vpn_cmdline -h [hostname] -u [username] -p [password] -- The 'hostname' argument is the SSL VPN endpoint. For example: 'vpn.dal.softlayer.com'



* To stop MotionPro:



sudo ./vpn_cmdline -s

The preceding steps do not work with Linux installed on Windows. MotionPro will authenticate, but will not establish a connection.





 MotionPro stand-alone clients for Mac OS X 



 If you start from the Web browser and use the automatically downloaded MotionPro client 

If you have ever [logged on to SSL VPN](https://cloud.ibm.com/docs/iaas-vpn?topic=iaas-vpn-getting-startedlogin-to-the-vpn) using a Web browser, the compatible version of MotionPro client is downloaded for you to install.



1.
6. Copy the webhook URL that is generated. The URL format looks similar to the following:

https://hooks.slack.com/services/A1AA11A1A/AAA1AAA1A/a1aaaaAAAaAaAAAaaaaaAaAA
7. To verify that the Slack webhook is installed, send a test message to your webhook URL by running the following command:

curl -X POST -H 'Content-type: application/json' -d '{"text":"VPN test message"}' <webhook_URL>
8. Go to the Slack channel you chose to verify that the test message is successful.
9. In the config.yaml file for the Helm chart, configure the webhook to monitor your VPN connection.



1. Change monitoring.enable to true.
2. Add private IP addresses or HTTP endpoints in the remote subnet that you want ensure are reachable over the VPN connection to monitoring.privateIPs or monitoring.httpEndpoints. For example, you might add the IP from the remote.privateIPtoPing setting to monitoring.privateIPs.
3. Add the webhook URL to monitoring.slackWebhook.
4. Change other optional monitoring settings as needed.









 Step 7: Deploy the Helm chart 

Deploy the strongSwan Helm chart in your cluster with the configurations that you chose earlier.



1. If you need to configure more advanced settings, follow the documentation provided for each setting in the Helm chart.
2. Save the updated config.yaml file.
3. Install the Helm chart to your cluster with the updated config.yaml file.

If you have multiple VPN deployments in a single cluster, you can avoid naming conflicts and differentiate between your deployments by choosing more descriptive release names than vpn. To avoid the truncation of the release name, limit the release name to 35 characters or less.

helm install vpn iks-charts/strongswan -f config.yaml
4. Check the chart deployment status.
The repositories section of the file must contain the maven URL for jitpack, for example:

repositories {
...
maven {
url 'https://jitpack.io'
}
}



Init functions

If the smart contract was written using the low-level APIs provided by the Fabric Chaincode Shim API, your smart contract needs to contain an Init function that is used to initialize the chaincode. This function is required by the smart contract interface, but does not necessarily need to be invoked by your applications. Because you cannot use the console to deploy a smart contract that contains an Init function, you need to move that initialization logic into the smart contract itself and call it separately. For example, the smart contract can use a reserved key to check whether the smart contract has already been initialized or not. If not, then call the initialization logic, otherwise proceed as usual. If your smart contract needs to include the Init function, the only way to deploy it is by using the Fabric [peer lifecycle chaincode install](https://hyperledger-fabric.readthedocs.io/en/release-2.2/commands/peerlifecycle.htmlpeer-lifecycle-chaincode-install) command or the [IBM Blockchain Platform collection for Ansible](https://ibm-blockchain.github.io/ansible-collection/). You can also refer to the [Fabric documentation](https://hyperledger-fabric.readthedocs.io/en/release-2.2/chaincode_lifecycle.htmlstep-three-approve-a-chaincode-definition-for-your-organization) for more details on how to use an Init function with the Fabric chaincode lifecycle.

Repackage smart contract

Attention! The IBM Blockchain Platform Extension for VS Code (VS Code extension) referenced throughout the documentation is an open-source project which is no longer active, and therefore not officially supported by IBM.
rm -rf /Library/helm/plugins/helm-ibmc for macOS
2. Follow the [documentation](https://cloud.ibm.com/docs/openshift?topic=openshift-storage_cos_install) to re-install the ibmc Helm plug-in and the IBM Cloud Object Storage plug-in.



For permission errors:



1. Change the permissions for the ibmc plug-in. Linux

chmod 755 /.helm/plugins/helm-ibmc/ibmc.sh

Mac OS

chmod 755 /Library/helm/plugins/helm-ibmc/ibmc.sh
2. Try out the ibm Helm plug-in.

helm ibmc --help
3. [Continue installing the IBM Cloud Object Storage plug-in](https://cloud.ibm.com/docs/openshift?topic=openshift-storage_cos_install).
rm -rf /Library/helm/plugins/helm-ibmc for macOS
2. Follow the [documentation](https://cloud.ibm.com/docs/containers?topic=containers-storage_cos_install) to re-install the ibmc Helm plug-in and the IBM Cloud Object Storage plug-in.



For permission errors:



1. Change the permissions for the ibmc plug-in. Linux

chmod 755 /.helm/plugins/helm-ibmc/ibmc.sh

Mac OS

chmod 755 /Library/helm/plugins/helm-ibmc/ibmc.sh
2. Try out the ibm Helm plug-in.

helm ibmc --help
3. [Continue installing the IBM Cloud Object Storage plug-in](https://cloud.ibm.com/docs/containers?topic=containers-storage_cos_install).
To see an example extension, check out [the sample](https://github.com/ibm-cloud-security/appid-sample-code-snippets/blob/master/premfa-extension-point/index.js).
3. Register your extension with your instance of App ID by making a PUT request to config/cloud_directory/mfa/extensions/premfa. The configuration includes your extension's URL and any authorization information that is needed to access the endpoint. For development purposes, isActive is set to false. Be sure to test your configuration before you enable it.

curl -X PUT https://<region>.appid.cloud.ibm.com/management/v4/<tenantID>/config/cloud_directory/mfa/extensions/premfa' --header 'Content-Type: application/json' --header 'Accept: application/json' --header 'Authorization: Bearer <IAMToken>' -d '{
"isActive": false,
"config": {
"url": "<extensionsURL>",
"headers": {
"Authorization": "<customExtensionAuthorizationHeader>"
}
}
}'

It is highly recommended that you always use HTTPS instead of HTTP for the extensions_URL to ensure that your connection is encrypted.
4. After the extension is successfully configured, verify that your endpoint works correctly by using the test API. App ID makes a POST request to your configured extension with the example values.

curl -X POST https://<region>.appid.cloud.ibm.com/management/v4/<tenantID>/config/cloud_directory/mfa/extensions/premfa/test --header 'Content-Type: application/json' --header 'Accept: application/json' --header 'Authorization: Bearer <IAMToken>'
5. Enable your extension by making a PUT request that sets isActive to true.
Run the following command for your public or private endpoint.

Private endpoints

curl -sL https://ibm.biz/install-sysdig-k8s-agent | bash -s -- -a <MONITORING_ACCESS_KEY> -c ingest.private.us-south.monitoring.cloud.ibm.com -ac 'sysdig_capture_enabled: false' --openshift

Public endpoints

curl -sL https://ibm.biz/install-sysdig-k8s-agent | bash -s -- -a <MONITORING_ACCESS_KEY> -c ingest.us-south.monitoring.cloud.ibm.com -ac 'sysdig_capture_enabled: false' --openshift

Where MONITORING_ACCESS_KEY is the ingestion key for the instance.

By default the slim agent is installed. The slim agent reduces the possible are of attack for potential vulnerabilities and, as a result, is more secure. If installing the full agent is desired, add the -af option to the curl command.
2. Verify that the monitoring agent is created successfully and its status. Run the following command:

oc get pods -n ibm-observe

The deployment is successful when you see one or more sysdig-agent pods. The number of sysdig-agent pods equals the number of worker nodes in your cluster. All pods must be in a Running state.









 Step 3: Step 3. Launch the monitoring UI 

To launch the monitoring UI through the IBM Cloud console, complete the following steps.



1. [Log in to your IBM Cloud account](https://cloud.ibm.com/login).

After you log in with your user ID and password, the IBM Cloud Dashboard opens.
2. From the menu ![Menu icon](https://cloud.ibm.com/docs-content/v1/content/icons/icon_hamburger.svg), select Observability.
3. Select Monitoring. The list of instances that are available on IBM Cloud is displayed.
4. Find your instance and click Open dashboard.
Optional for version 2.2.0 and later strongSwan Helm charts: Remap remote network subnets by using the remoteSubnetNAT setting. Network Address Translation (NAT) for subnets provides a workaround for subnet conflicts between the cluster network and on-premises remote network. You can use NAT to remap the remote network's IP subnets to a different private subnet. Remapping happens before the packets are sent over the VPN tunnel. Pods in the cluster see the remapped IP subnets instead of the original subnets. Before the pods send data back through the VPN tunnel, the remapped IP subnet is switched back to the actual subnet that is being used by the remote network. You can expose both remapped and non-remapped subnets at the same time over the VPN.







 Step 6 (optional): Enable monitoring with the Slack webhook integration 

To monitor the status of the strongSwan VPN, you can set up a webhook to automatically post VPN connectivity messages to a Slack channel.



1. Sign in to your Slack workspace.
2. Go to the [Incoming WebHooks app page](https://slack.com/apps/A0F7XDUAZ-incoming-webhooks).
3. Click Request to Install. If this app is not listed in your Slack setup, contact your Slack workspace owner.
4. After your request to install is approved, click Add Configuration.
5. Choose a Slack channel or create a new channel to send the VPN messages to.
6. Copy the webhook URL that is generated. The URL format looks similar to the following:

https://hooks.slack.com/services/A1AA11A1A/AAA1AAA1A/a1aaaaAAAaAaAAAaaaaaAaAA
7. To verify that the Slack webhook is installed, send a test message to your webhook URL by running the following command:
./ManualRegisterConnector.ps1 -APIClientID {APIClientID} -APIClientSecret {APIClientSecret} -ADDomainName {ADDomainName} -ADServerName {ADServerName} -ActiveDirectoryUserName {ActiveDirectoryUserName} -ActiveDirectoryPassword {ActiveDirectoryPassword} -PreferredDnsServer {PreferredDnsServer}

Replace the contents of the {} with the values for your system.









 Extended (Site-to-Site) 

Domain controller latency issues

The Extended (Site-to-Site) option does not have a domain controller (DC) on IBM Cloud. Sites that do not have domain controllers are less efficient because of slow AD authentication and GPO processing. If you have sites with no DCs, you can limit the latency issues if you:



* Create the AD subnets for these sites and link them to the closest site with a DC. The sites reach the on-premises side for AD authentication and GPO processing.
* Enable GPO processing over [slow links detection](https://technet.microsoft.com/en-us/library/cc781031%28v=ws.10%29.aspx?f=255&MSPPError=-2147217396).



Other Active Directory Best practices include:



* Establish as a site every geographic area that requires fast access to the latest directory information. Establishing areas that require immediate access to up-to-date Active Directory information as separate sites provide the resources that are required to meet your needs.
* Place at least one domain controller in every site, and make at least one domain controller in each site a global catalog. Sites that do not have their own domain controllers and at least one global catalog depend on other sites for directory information and are less efficient. For more information, see [Active Directory Best Practices](https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2003/cc778219%28v=ws.10%29)



Network Connectivity



1.
* Their loyalty program needs a boost in the arm with a modern take on the printed coupons at check out. So Developers must constantly evolve the related apps, but traditional tools slow their ability to deploy updates and features frequently.
* Certain high-value inventory isn’t moving as well as expected, but yet the “foodie” movement seems to be growing in major metropolitan markets.





 Solution 

The grocer needs an app to increase conversion and store traffic to generate new sales and build customer loyalty in a reusable cloud analytics platform. The in-store targeted experience can be an event along with a services or product vendor that attracts both loyalty and new customers based on affinity to the specific event. The store and business partner then offer incentives to come to the event as well as buying products from the store or business partner.

After the event, customers are guided to purchasing the necessary products, so they can repeat the demonstrated activity on their own in the future. The targeted customer experience is measured with incentive redemption and new loyalty customer sign-ups. The combination of a hyper-personalized marketing event and a tool to track in-store purchases can carry the targeted experience all the way through to product purchase. All these actions result in higher traffic and conversions.

As an example event, a local chef is brought into the store to show how to make a gourmet meal. The store provides an incentive to drive attendance. For example they provide a free appetizer at the chef's restaurant and an extra incentive to buy the ingredients for the demonstrated meal (for example, $20 off $150 cart).

The solution is made up of the following primary components.



1. INVENTORY ANALYSIS: the in-store events (recipes, ingredient lists, and product locations) are tailored to market the slow-moving inventory.
2. LOYALTY MOBILE APP provides targeted marketing with digital coupons, shopping lists, product inventory (prices, availability) on a store map, and social sharing.
3. SOCIAL MEDIA ANALYTICS provides personalization by detecting customers’ preferences in terms of trends: cuisines, chefs, and ingredients. The analytics connect regional trends with an individual’s Twitter, Pinterest, and Instagram activity.
4. DEVELOPER-FRIENDLY TOOLS accelerate roll-out of features and bug fixes.
Java extensions are not supported. Maximo Manage [Automation Scripting](https://ibm-maximo-dev.github.io/maximo-autoscript-documentation/introduction/whatisautoscript) capability should instead be used. Existing Maximo customers who have Java extensions will need to migrate / convert these functions into automation scripts within the application.





 3rd Party Applications 

Maximo Application Suite SaaS will not host or support 3rd party applications. 3rd Party applications hosted outside the of the MAS-SaaS environment can be integrated to applications with the Suite provided they follow standard MAS integration protocols.





 Access 

Clients will not have access to the operating system, file system, database or overall system administration of the Suite. Database Administrator access or direct updating of the MAS-SaaS database(s) is not allowed.





 MAS Administrator Functions 

Direct access to the clusters is not available. Changes required must be submitted using an [IBM support case](https://www.ibm.com/mysupport) and the IBM SRE team will execute.





 Self-Service Portal 

A self service portal (SSP) for MAS-SaaS is not available at this time and is under construction.
* Error: When you check the status by submitting the oc get WatsonDiscovery command, the ready status of the resources toggles between showing 23/23 and 20/23 components as being ready for use.
* Cause: The readiness state of the resources is not reported consistently after a migration.
* Solution: Typically, the instance is ready for use despite the ready state instability. To manually refresh the status information, run the following commands in a terminal that is logged in to the cluster:

oc proxy &
curl -ksS -X PATCH -H "Accept: application/json, /" -H "Content-Type: application/merge-patch+json" http://127.0.0.1:8001/apis/discovery.watson.ibm.com/v1/namespaces/<namespace>/watsondiscoveries/wd/status --data '{"status": null}'



This issue is fixed with the 4.0.8 release.
* The wd-discovery-multi-tenant-migration job fails if anyone besides a system administrator performs the upgrade.



* Error: When you upgrade with a user ID other than admin, the migration job fails.
* Cause: The migration script assumes that the script is run by a user with the admin user ID.
* Solution: Apply a patch that allows the migration to be successful. Complete the following steps:



1. From the Cloud Pak for Data web client, get the user ID of the owner of the instance that you want to upgrade.
2. Download the wd-migration-uid-patch.zip patch file from the [Watson Developer Cloud GitHub](https://github.com/watson-developer-cloud/doc-tutorial-downloads/blob/master/discovery-data/latest/wd-migration-uid-patch.zip) repository.
3. Extract the wd-migration-uid-patch.yaml file from the archive file, and then open it in a text editor.
4. Replace the <user_id> variable with the user ID of the owner of the instance that you want to upgrade.
5.
(https://{cpd_cluster_host}:{port}/discovery/{release}/instances/{instance_id}/api)
-t --token The authorization token of your Cloud Pak instance
-u --user The user name of your Cloud Pak instance
-p --password The user password of your Cloud Pak instance
If the password is not specified, the command line prompts to input
-n --name The name of the custom crawler to upload (deploy only)
-f --file The path of the custom crawler package to upload (deploy only)
-i --id The crawler_resource_id value to delete the custom crawler (undeploy only)
--help Show this message.





 4.0.5 and earlier releases only 



 Installing a connector in 4.0.5 and earlier releases 

You can install your custom connector to your Discovery instance by performing the following steps.



1. Ensure that you have completed all steps to create a custom connector up to and including the steps listed in [Compiling and packaging the example connector](https://cloud.ibm.com/docs/discovery-data?topic=discovery-data-assemblecompile-package-connector).
2. Run the following command from the directory on your local machine where you created and compiled your custom connector:

bash scripts/manage_custom_crawler.sh deploy -z {built_connector_zip_file}

where {built_connector_zip_file} is the name of the file you packaged in [Compiling and packaging the example connector](https://cloud.ibm.com/docs/discovery-data?topic=discovery-data-assemblecompile-package-connector).

If your Discovery instance is running on Red Hat OpenShift, specify the -o or --openshift parameter with the script.

For example:

bash scripts/manage_custom_crawler.sh deploy -z myCrawler.zip -o true







 Uninstalling a connector in 4.0.5 and earlier releases
Configuring the V3 Logging agent for Windows 

The logging agent is responsible for collecting and forwarding logs to your IBM Log Analysis instance. After you provision an instance of IBM® Log Analysis, you must configure a logging agent for each log source that you want to monitor.

To configure your Windows server to send logs to your IBM Log Analysis instance, you must install the logdna-agent. The logging agent reads log files from a directory defined in your Windows system and forwards the log data to your logging instance.



 Before you begin 

Currently, you cannot collect Windows Event server logs with this agent. [Configure NXlog](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-windows_serv) to send Event logs to the logging instance.





 Step 1. Install the agent 

You can install the agent by using MSI or Chocolatey.



 Option 1: Install by using Chocolatey 

Run the following command to deploy the agent:

choco install mezmo-agent





 Option 2: Install by using MSI 

Complete the following steps to deploy the agent:



1. [Download the current Windows agent msi package.](https://github.com/logdna/logdna-agent-v2/blob/3.6/docs/WINDOWS.md)
2. Run the following from a Windows command prompt as an admin user in the directory where you downloaded the agent package:

msiexec /i "mezmo-agent.msi" /qn KEY=<INGESTION_KEY>

Where

INGESTION_KEY
: Is the ingestion key for your IBM Log Analysis instance.



After the agent is installed it is started and log entries are written to c:ProgramDatalogs.







 Step 2. Configure the agent 

After you install the agent, check that you have the following directories and files:

C:Program FilesMezmo
: This is the directory containing the installed files.

C:ProgramDatalogdnalogdna.conf