vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Connectivity options on IBM Cloud 

IBM® Db2® Warehouse on Cloud offers multiple secure connectivity options for your application connection requirements.



 Connecting to a public endpoint (default option) 

As with any public cloud service, you can connect your application by way of a public host name that is provided to you at the time that your service is provisioned. Access to your data is protected by strong authentication, vast Db2 authorization options and access controls, encryption over the wire and at rest, and IBM security and compliance practices for development and operations. Optional IP allowlisting is offered. Create an IBM Support case if you want to enable IP allowlisting.

For application connections, do not use IP addresses to connect to the Db2 Warehouse on Cloud instance, as the IP addresses resolved from the hostname may change.



 How to connect to a public endpoint: 

You can also obtain your host name and credentials in the following way:



1. Log in to IBM Cloud and click your service instance.
2. Click Service credentials.
3. Click New credential, then click Add.
4. After the credentials are created, under the Actions column, click View credentials.
5. In the following JSON document example, note the contents of the hostname, password, and username fields. You use these three components to make the public endpoint connection:




{
"apikey": "abcdefghijklmnopqrstuvwxyz0123456789",
"db": "BLUDB",
"host": "db2w-abcdefg.eu-de.db2w.cloud.ibm.com",
"hostname": "db2w-abcdefg.eu-de.db2w.cloud.ibm.com",
"https_url": "https://db2w-abcdefg.eu-de.db2w.cloud.ibm.com",
For security considerations, the signature key owners can be different people from the master key part owners. The signature key owner needs to be the only person who knows the password that is associated with the signature key file.



* To display the existing signature keys on the workstation, use the following command:

ibmcloud tke sigkeys
* To create and save a new signature key on the workstation, use the following command:

ibmcloud tke sigkey-add

When prompted, enter an administrator name and a password to protect the signature key file. You must remember the password. If the password is lost, the signature key can't be used.

Repeat the command to create multiple signature keys if needed.
* To select the administrators to sign future commands, use the command:

ibmcloud tke sigkey-sel

A list of signature keys that are found on the workstation is displayed. When prompted, enter the key numbers of the signature key files to select for signing future administrative commands. When prompted, enter the passwords for the signature key files.

This command determines what signature keys are allowed to sign future commands. There is no limit to the number of signature key files that you can select. If you select more signature keys than required to sign a command, the actual signature keys that are used will be determined at the time the command is executed.

You can also use a third-party signing service to provide signature keys. For more information, see [Using a signing service to manage signature keys for instance initialization](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-signing-service-signature-key).







 Step 2: Add one or more administrators in the target crypto unit 



* To display the existing administrators for a crypto unit, use the following command:

ibmcloud tke cryptounit-admins
* To add an administrator, use the following command:

ibmcloud tke cryptounit-admin-add

A list of the signature key files that are found on the workstation is displayed.

When prompted, select the signature key file that is associated with the crypto unit administrator to be added.
A final review of the install is done to ensure what has been deployed meets the order and the additional information gathered. At this point, the order is marked complete.





 Welcome Letter sent to the client 

A welcome letter is then sent to the client which will include the URL's to access each environments, usernames and instructions on how to supply the license file the customer would have received when they purchased the TRIRIGA Application Suite product.

The letter will contain similar instructions to below:



* Some IBM products require license keys to use them. The [IBM License Key Center](https://licensing.subscribenet.com/control/ibmr/login) is an online software license key delivery tool that provides easy access to your license keys 24 hours a day, 7 days a week.







 How to log in 



* To access your license keys:



* Please click [here](https://urldefense.proofpoint.com/v2/url?u=https-3A__licensing.subscribenet.com_service_ibmr_passwordfindertoken-3Ftoken-3DiBQqgLdNUxyuxE8Ik8PMKSMDo79ubDnPVuLzb6G50e8V6us7ubXZDYizfshmUft4n9qHifp1xZluaMEBCauDmw-253D-253D&d=DwMDaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=bSeOIO3coRE67_IGnJbSkmdGrML0r3fDG4JKYOYSpt4&m=vXEs4tQw0jGZbxoe8CB4_ay45BzQckFiKIIZfFXQ8oI&s=sUdq8LY1rpYBZyrgdqQXnmvo4BePM0scOTmmhvZXUzE&e=) to create your Password
* Once you have created your password click on the Attempt to Login link.
* Select the link to log in to the License Key Center.
* Select Continue to navigate to the IBM Rational License Key Center.
* Log in to the License Key Center using your email address as your ID and your password.
Use jsonpath to specify the path to an element of the JSON output. This value is optional.

--password, -p
: The password to access the registry server. This value is optional.

--password-from-file, --pf
: The path to a file containing the password to access the registry server. The first line of the file is used for the password. This value is optional.

--password-from-json-file, --pfj
: The path to a JSON file containing the password to access the registry server. The apikey field is used for the password. This value is optional.

--quiet, -q
: Specify this option to reduce the output of the command. This value is optional. The default value is false.

--server, -s
: The URL of the registry server. This value is optional.

--username, -u
: The username to access the registry server. This value is optional.





 Example 

The following example updates a password for the image registry access that is called myregistry.

ibmcloud ce registry update --name myregistry --password NEW_API_KEY





 Example output 

Getting image registry access secret 'myregistry'...
Updating image registry access secret 'myregistry'...

OK









 Repo commands 

A code repository, such as GitHub or GitLab, stores source code. With Code Engine, you can add access to a private code repository and then reference that repository from your build.

You must be within the context of a [project](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-project) before you use repo commands.

For more information about accessing repositories, see [Accessing private code repositories](https://cloud.ibm.com/docs/codeengine?topic=codeengine-code-repositories).
Creating IBM Cloud HSM partitions 

Within an IBM Cloud® Hardware Security Module (HSM), separate cryptographic workspaces must be initialized and designated for clients. A workspace, or partition, and all its contents are protected by encryption that is derived from its authentication. Only a client that presents the proper authentication is allowed to see the partition and work with its contents.

When you create your partitions, be aware that partition names, also known as labels, must be unique in the HSM. You cannot create two partitions with the same label on one HSM. What you name your partition is the label that is seen by Public-Key Cryptographic Standards (PKCS) #11 applications.



1.  Log in as the HSM Administrator with the password that is used for initializing the HSM.

[myLuna] lunash:>hsm login
Please enter HSM Administrators' password:
>
hsm login successful.
Command Result : 0 (Success)
2.  Create the partition.

[myLuna] Lunash:>partition create - partition customerPartionProd
Please ensure that you have purchased licenses for at least this number of partitions: 1
If you are sure to continue then type proceed, otherwise type quit.
> proceed
Processing...
Please enter a password for the partition
>
Please re-enter password to confirm:
>
Please enter the cloning domain to use when creating this partition (press enter to use the default domain):
> MyDomain
partition create successful
Command Result : 0 (Success)
Why does my backup fail with a message about a missing value for Server0 Password? 

  What’s happening 

A backup fails immediately after startup with the following message in the log files: PARS-E-05152 A value is required for Server0.Password.

  Why it’s happening 

A configuration file (global.vvc) is missing the hash value for the vault password. Without this entry, the agent cannot authenticate to the vault system.

  How to fix it 

Store the Vault password in the Backup Portal again. To do so, go to "Vault Settings" and edit the existing configuration.



1.  In the Backup Portal, click Computers, and click the server name to display its information.
2.  Click Vault Settings and from the Action menu, select Edit.
3.  Enter the Vault Name.
4.  Enter credentials. "Account" is the same as the "Account Name" in the [IBM Cloud console](https://cloud.ibm.com/cloud-storage/backup). Typically, it looks like "SLE[account ID]" or "IBME[account ID]". For more information about finding the username or changing the backup password, see [Managing username and password for the Cloud Backup service](https://cloud.ibm.com/docs/Backup?topic=Backup-changePassword).
5.  Click Save.



If this action does not fix the issue, remove the Backup agent from the server and install the newest version. Follow the instructions appropriate for your OS,



*  [Installing the backup client in Linux®](https://cloud.ibm.com/docs/Backup?topic=Backup-InstallinLinux),
*  [Installing the backup client in Windows®](https://cloud.ibm.com/docs/Backup?topic=Backup-InstallinWindows).
rule-9e16b8a4-1255-474e-a8a3-afed67de2627 - Check whether all network interfaces of a virtual server instance have at least one Virtual Private Cloud (VPC) security group attached
rule-9ecf7e84-aa51-42ad-875e-58e9522a5e65 - Check whether VPN for VPC has Internet Key Exchange (IKE) policy encryption that is not set to "triple_des"
rule-b4c58eff-4d19-4d33-840e-56b2ac76585a - Check whether VPN for VPC has Internet Key Exchange (IKE) policy authentication that is set to minimum "sha256"
rule-a8a69cd6-a902-4144-b652-8be68600a029 - Check whether VPN for VPC has a Diffie-Hellman group set to at least group 
rule-f98453ba-ebb9-4d96-aa13-09ef808fb4ba - Check whether VPN for VPC has IPsec policy encryption that is not set to "triple_des"
rule-09298b01-e2c5-43f1-a1b4-0b413fe4f998 - Check whether VPN for VPC has IPsec policy authentication that is set to minimum "sha256"
rule-115eb377-e256-459d-9e17-a868e128bd0c - Check whether VPN for VPC has an IPsec policy that does not have Perfect Forward Secrecy (PFS) disabled
rule-d8d13c3e-5ca0-46c5-a055-2475852c4ec6 - Check whether VPN for VPC authentication is configured with a strong pre-shared key with at least characters
rule-53895d42-9190-47d8-9a70-0c1ebea5f7c7 - Check whether VPN for VPC has a Dead Peer Detection policy that is set to "restart"
rule-d8d13c3e-5ca0-46c5-a055-2475852c4ec6 - Check whether VPN for VPC authentication is configured with a strong pre-shared key with at least characters
rule-53895d42-9190-47d8-9a70-0c1ebea5f7c7 - Check whether VPN for VPC has a Dead Peer Detection policy that is set to "restart"
rule-200dc6e7-96f1-49a9-9999-7e4645dc7ea6 - Check whether Application Load Balancer for VPC has public access disabled
rule-0e5151b1-9caf-433c-b4e5-be3d505e458e - Check whether Application Load Balancer for VPC is configured with multiple members in the pool
rule-bfc9d304-a086-43c0-b3ba-d0f101f616df - Check whether Application Load Balancer for VPC listener is configured with default pool
rule-8c923215-afdc-41b1-886c-64ce78741f8c - Check whether Application Load Balancer for VPC has health check configured when created
rule-d491a44c-e7bc-46bc-af07-231da0bb6501 - Check whether Application Load Balancer for VPC has a health check protocol that is either HTTP or HTTPS
rule-cb1180b7-2f8c-40ba-b2dd-207bee6bc17f - Check whether Application Load Balancer for VPC pool uses the HTTPS protocol for HTTPS listeners
rule-65b61a0f-ffdb-41ba-873d-ad329e7fc0ee - Check whether Application Load Balancer for VPC is configured to convert HTTP client requests to HTTPS
rule-d544f217-3723-4376-b3aa-037c5f201e8d - Check whether Application Load Balancer for VPC uses HTTPS (SSL & TLS) instead of HTTP
Paste the Public key, that you created according to [the guidelines mentioned in Securing Access](https://cloud.ibm.com/docs/sap?topic=sap-quickstudy-vs-gen2-netweaver-winsquickstudy-vs-gen2-netweaver-wins-secure-access).
7. Click Add SSH key.
8. Optional: User data. Leave blank.







 Attaching a block storage volume 

To have file system space available beyond what is required by the operating system, you need to attach a block storage volume to your VSI. This storage volume is used by the application that you're installing. In this example, the application is the Relational Database Management System (RDBMS) required for an SAP NetWeaver stack.



1. Click New volume.
2. Enter sap-db-vol for Name.
3. Select Custom for Profile.
4. Enter 500 for Size.
5. Enter 10000 for IOPS. Throughput defaults to 156.25 MiBps.
6. Keep the Encryption and Auto Delete defaults.
7. Click Attach.
8. Keep the Networking default.
9. Keep the Network interfaces default.
10. Click Create virtual server instance. After the Windows instance is provisioned and ready, you need to retrieve the Administrator password and connect to it.









 Step 4: Connecting to your Windows VSI 

To be able to connect to the Windows VSI from your client, you need the Administrator password and a public IP address. The password is retrieved by the IBM Cloud command-line interface (CLI) whereas the public IP address - it is called Floating IP - can be created with the IBM Cloud console.



 Install CLI
SQL Server jdbc:sqlserver://{serverName}[{instanceName}]:{port}[;property=value] jdbc:sqlserver://localhost:1433;DatabaseName=sample 
 Postgresql jdbc:postgresql://{host}:{port}/{database} jdbc:postgresql://localhost/sample 



User
: The username that you obtain from the database you selected. You use this username to crawl the source. Your username is different from database to database.

Password
: The password that is associated with your username. Your password is different from database to database.
8. Complete the following fields in the Connection settings section:

JDBC driver type
: Choose the database.

Db2 is selected by default. If you want to crawl from a database type that is not listed, select OTHER. To crawl data that is managed by Data Virtualization on IBM Cloud Pak for Data, keep Db2 selected.

JDBC driver classname
: The JDBC driver class name that is associated with the database you selected. This field is autofilled, unless you select OTHER.

JDBC driver classpath
: Upload a JDBC driver file, which can have a .jar or .zip file extension. Alternatively, you can reuse a .jar or .zip file that you uploaded previously.
9. Complete the following fields in the Specify what you want to crawl section, and then click Add:

Schema Name
: The schema that you want to crawl.

Table Name
: The table within a schema that you want to crawl.

Click the edit icon to specify more table crawl settings, including:

Primary key
: The primary key of the target database table. If the primary key is not configured in the target database table, you must specify the key in this field. The JDBC database crawler appends this primary key value to the URL of each crawled row to keep its uniqueness.
Interfaces in a VRRP synchronization group (“sync group”) are synchronized such that, if one of the interfaces in the group fails over to backup, all interfaces in the group fail over to backup. For example, if one interface on a master router fails, the whole router fails over to a backup router.

This value is different than the VRRP group, as it defines what interfaces on a device fail over when an interface in that group registers a fault. It is recommended that all interfaces belong to the same sync-group; otherwise, some interfaces are master and have gateway IPs, and others are backup, and traffic does not forward properly anymore. Active/active configurations are not supported.





 VRRP rfc-compatibility 

rfc-compatibility enables or disables RFC 3768 MAC addresses for VRRP on an interface. This should be enabled on the native interfaces, but not enabled on any configured VIFs. Some virtual switches (mostly vmware) have problems with this being enabled, and cause traffic to be dropped and not sent to the gateway IP from the hypervisor host machine. Leave this setting alone, and do not configure the setting for any VIFs.





 VRRP authentication 

If a password is set for VRRP authentication, the authentication type must also be defined. If the password is set and the authentication type is not defined, the system generates an error when you try to commit the configuration.

Similarly, you cannot delete the VRRP password without also deleting the VRRP authentication type. If you do, the system generates an error when you try to commit the configuration. If you delete both the VRRP authentication password and authentication type, VRRP authentication is disabled.

The IETF decided that authentication is not to be used for VRRP version 3. For more information, see RFC 5798 VRRP.





 Version 2/3 support 

The VRA supports both VRRP version 2 (default) and version 3 protocols. In version 2, you cannot have IPv4 and IPv6 together; however, in Version 3, you can have IPv4 and IPv6 at the same time.





 High availability VPN with VRRP
This is available in the Event Notifications UI in the "Sources" section.



 Example 

ibmensourceid: 121313123:api









 Event Notifications extension optional attributes 

These are optional attributes.



 ibmenseverity(String) 

Some sources can have the concept of an Event severity. Hence a handy way is provided to specify a severity of the event.



 Example 

ibmenseverity:LOW







 ibmendefaultshort(String) 

This message is used in case the event that is routed to a destination that needs a human readable text, but a destination-specific attribute is not specified.

For example, if ibmenfcmbody is not specified and the event is routed to Android FCM type destination, ibmendefaultshort is used as the notification title (android_title).



 Example 

ibmendefaultshort: "Change password"







 ibmendefaultlong(String) 

This message is used in case the event that is routed to a destination that needs a human readable text, but a destination-specific attribute is not specified.

For example, if ibmenfcmbody is not specified and the event is routed to Android FCM type destination, ibmendefaultlong is used as the notification body (alert).



 Example 

ibmendefaultlong: "Password will expire in 10 Days. Please log in to the Bank home page and click on Change Password link to change your password."







 ibmenfcmbody(string/json) 

This attribute is needed if you want to send push notification to an Android device. This is the body that you want to send to FCM server, this must be JSON in string format. For more information regarding FCM body, see [here](https://firebase.google.com/docs/cloud-messaging/concept-options).

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



 Example: Deprecated Push notification service compatible format: 

"ibmenfcmbody": "{"en_data":{"alert":" Password will expire in 10 Days.
If you use your personal private SSH key, then this file is usually located at $HOME/.ssh/id_rsa (Mac OS or Linux) or at %HOMEPATH%.sshid_rsa (Windows). This value is required for ssh secrets. This value is optional.

--known-hosts-path, --khp
: The path to your known hosts file for an SSH secret. This value is a security feature to ensure that the private key is only used to authenticate at hosts that you previously accessed, specifically, the GitHub or GitLab hosts. This file is usually located at $HOME/.ssh/known_hosts (Mac OS or Linux) or at %HOMEPATH%.sshknown_hosts (Windows). This value applies only for ssh secrets. This value is optional.

-n, --name
: The name of the secret. Use a name that is unique within the project.



* The name must begin and end with a lowercase alphanumeric character.
* The name must be 253 characters or fewer and can contain lowercase letters, numbers, periods (.), and hyphens (-).



This value is optional.

--output, -o
: Specifies the format of the command output. Valid values are json, yaml, jsonpath=JSONPATH_EXPRESSION, and jsonpath-as-json=JSONPATH_EXPRESSION. Use jsonpath to specify the path to an element of the JSON output. This value is optional.

--password, --pw
: The password for a basic auth or registry secret. If neither --password, nor --password-from-file, nor --password-from-json-file option is specified, then you are prompted for the password. This value is required for basic_auth and registry secrets. This value is optional.

--password-from-file, --spf
: The path to a file containing the password for a basic auth or registry secret. The first line of the file is used for the password.
If you want to use ECMP and have redundancy, you need two Direct Link connections on each XCR so that you can have 2 ECMP sessions running simultaneously.

Alternatively, some of our customers set up two links into different XCR in the same data center, for example WDC02, then failover as needed by using BGP configurations. This configuration is less redundant (less safe) than having Direct Link connections into two separate data centers, such as WDC02 and WDC05.
* Is there an SLA on the Direct Link XCR connections up to the account’s BCR connection?

There is no SLA on Direct Link today. Customers can achieve 99.99% effectively with two or more Direct Links that are properly configured for failover by using BGP, but IBM cannot control that or provide an SLA on it.
* Where can I get help setting up a Direct Link?

For connecting to Direct Link, see [Configuring IBM Cloud Direct Link](https://cloud.ibm.com/docs/direct-link?topic=direct-link-configure-ibm-cloud-direct-link). If you need more help, you can request engineering support in the case that was opened for the new service. Even if it is an API service with Equinix, opening a case enables an engineer to look at it. Or you can contact your IBM Sales representative.
* On Direct Link Exchange, does IBM set a BGP password?

BGP passwords for Direct Link Exchange aren't set up, by default. There is an option to specify BGP ASN and we assign BGP IP addresses. Also, it's possible to set up a BGP password for authentication purposes, we just need to let the engineers know.



FortiGate Security Appliance (FSA) 1 Gbps



* What is a firewall?

A firewall is a network device that is connected upstream from a server. The firewall blocks unwanted traffic from a server before the server is reached.
* Why should I use a firewall?

The primary advantage of having a firewall is that your server handles “good” traffic exclusively.