vania-janet/multiturn-rag-retrieval-data huggingface dataset:
The following Powershell commands create a new AD group called SQL Admins, and a new user sqluser1 with a password of <Password> added to the SQL Admins group. The suffix is the suffix of your domain name e.g. com or local:

$password = "<Password>"
$domainnb = "<NB_Domain>"
$dnssuffix = "<suffix>"
$path = "CN=Users,DC=" + $domainnb + ",DC=" + $dnssuffix
New-ADGroup -Name "SQL Admins" -SamAccountName SQLAdmins -GroupCategory Security -GroupScope Global -DisplayName "SQL Administrators" -Path $path -Description "Members of this group are SQL Administrators"
$secpassword = ConvertTo-SecureString $password -AsPlainText -Force
New-ADUser -Name "sqluser1" -AccountPassword $secpassword -Enabled $true
Add-ADGroupMember -Identity SQLAdmins -Members sqluser1

The following Powershell commands create a new AD group called SQL Service, and a new user sqlsvc with a password of <Password> added to the SQL Service group. The suffix is the suffix of your domain name e.g. com or local:

$password = "<Password>"
$domainnb = "<NB_Domain>"
$dnssuffix = "<suffix>"
$path = "CN=Users,DC=" + $domainnb + ",DC=" + $dnssuffix
New-ADGroup -Name "SQL Service" -SamAccountName SQLService -GroupCategory Security -GroupScope Global -DisplayName "SQL Service" -Path $path -Description "Members of this group are services accounts for SQL"
$secpassword = ConvertTo-SecureString $password -AsPlainText -Force
New-ADUser -Name "sqlsvc" -AccountPassword $secpassword -Enabled $true
Add-ADGroupMember -Identity SQLService -Members sqlsvc
Your deployment's Overview shows all the relevant connection information.

To connect, Kibana needs the username, password, url, and port for your deployment. It also needs the CA certificate to access the database. To get this, copy the certificate information from Endpoints. Then, save the certificate to a file. You can use the name that is provided in the download, or your own file name.

Remember where you save the certificate on your file system. If you are running Kibana locally, not in Docker, then the certificate goes in $KIBANA_HOME/config/<filename>.





 Step 2: Set up Kibana 

Before running the Docker container that includes Kibana, create a configuration file that contains some basic Kibana settings.

Create a YAML file called kibana.yml. Inside the file, you need the following Kibana configuration settings:

elasticsearch.ssl.certificateAuthorities: "/usr/share/kibana/config/cacert"
elasticsearch.username: "admin"
elasticsearch.password: "<password>"
elasticsearch.hosts: ["https://<hostname:port>"]
server.name: "kibana"
server.host: "0.0.0.0"

The first setting, elasticsearch.ssl.certificateAuthorities, is the location where the deployment's certificate lives in the Docker container. It gets placed in this location when you first run Docker. You can change this to a location of your choice, but the example path is the Kibana’s config directory.

Next, is elasticsearch.username and elasticsearch.password. Use the deployment's admin username and password. Be sure that you set the admin password before trying to connect. For elasticsearch.url, enter the deployment's hostname and port, which is separated by a :.

Lastly, server.name is a machine-readable name for the Kibana instance and server.host is the host of the backend server where you can connect to Kibana in your web browser.
Action Name Legacy Action name Description 

 <service_id>.deployment-backup.create <service_id>.backup-ondemand.create An on-demand backup of your deployment was created. If the backup failed, a "-failure" flag is included in the message. 
 <service_id>.deployment-backup-scheduled.create <service_id>.backup-scheduled.create A scheduled backup of your deployment was created. If the backup failed, a "-failure" flag is included in the message. 
 <service_id>.deployment-user.update <service_id>.user-password.update A user's password was updated. A "-failure" flag is included in the message if the attempt to update a user's password failed. 
 <service_id>.deployment-user.create <service_id>.user.create A user was created. A "-failure" flag is included in the message if the attempt to create a user failed. 
 <service_id>.deployment-user.delete <service_id>.user.delete A user was deleted. A "-failure" flag is included in the message if the attempt to delete a user failed. 
 No Longer Sent (see below for more information) <service_id>.backup.restore A restore from backup was created. If the attempted restore failed, a "-failure" flag is included in the message. 
 <service_id>.deployment-group.update <service_id>.resources.scale A scaling operation was performed. If the scaling operation failed, a "-failure" flag is included in the message. 
 <service_id>.deployment-allowlist-ip-addresses.update <service_id>.whitelisted-ips-list.update The allowlist was modified. A "-failure" flag is included in the message if the attempt to modify the allowlist failed. 
 <service_id>.deployment.update <service_id>.serviceendpoints.update A change was made to the service endpoints configuration. If the operation failed, a "-failure" flag is included in the message.
Getting Started 

This tutorial is a short introduction to using an IBM Cloud® Databases for EnterpriseDB deployment. [pgAdmin](https://www.pgadmin.org/) is an open source administration platform for PostgreSQL, and provides many tools for managing your data and databases. [Download and install](https://www.pgadmin.org/download/) the version that is appropriate to your environment, and then follow the steps to connect it to your Databases for EnterpriseDB deployment.



 Before you begin 



* You need to have an [IBM Cloud account](https://cloud.ibm.com/registration).
* You also need a Databases for EnterpriseDB deployment. You can provision one from the [IBM Cloud catalog](https://cloud.ibm.com/catalog/services/databases-for-enterprisedb). Give your deployment a memorable name that appears in your account's Resource List.
* [Set the Admin Password](https://cloud.ibm.com/docs/databases-for-enterprisedb?topic=databases-for-enterprisedb-admin-password) for your deployment.
* Install [pgAdmin4](https://www.pgadmin.org/download/).
* Review [Getting to production](https://cloud.ibm.com/docs/cloud-databases?topic=cloud-databases-best-practices) for general guidance on setting up a basic IBM Cloud® Databases for EnterpriseDB deployment.







 Step 1: Connect with pgAdmin 

pgAdmin runs as a server and you connect to it through a browser. When the server is started, it runs on localhost at default http://127.0.0.1:53113/browser/.

When you first open pgAdmin, you are prompted to set a primary password. This password differs from your deployment's password and is used specifically by pgAdmin to store passwords to your Databases for EnterpriseDB servers or deployments.

From the Dashboard on the Welcome screen, click Add New Server.

Provide pgAdmin with the information needed to connect to your deployment.

First, complete the Connection information,
where <alias> is a DSN alias that you created by using the db2cli writecfg command, <user_id> is your Db2 Warehouse on Cloud user ID, and <password> is your Db2 Warehouse on Cloud database password.



* To create a connection without SSL, complete the following steps:

a. Catalog the Db2 Warehouse on Cloud node so that client applications can connect to it. Issue the following command:

db2 catalog tcpip node <node_name> remote <Db2_Warehouse_IP_address> server <port_number>

where:

<node_name> is your name for the node.

<Db2_Warehouse_IP_address> is the IP address of the Db2 Warehouse on Cloud server.

<port_number> is the port that is used to connect to Db2 Warehouse on Cloud without using an SSL connection. If you are using the default port, specify 50000.

b. Catalog the remote Db2 Warehouse on Cloud database so that client applications can connect to it. Issue the following command:

db2 catalog database bludb as <db_alias> at node <node_name>

where <db_alias> is your name for the Db2 Warehouse on Cloud database.

c. Test the non-SSL connection in one of the following ways:



* Test the connection by using CLP by issuing the following command to connect to the Db2 Warehouse on Cloud database:

db2 connect to <db_alias> user <user_id>

where <user_id> is your Db2 Warehouse on Cloud user ID. You are prompted to enter your password.
* Test the connection by using CLI by issuing the following command to connect to the Db2 Warehouse on Cloud database:

db2cli validate -dsn <alias> -connect -user <user_id> -passwd <password>

where <alias> is a DSN alias that you created by using the db2cli writecfg command, <user_id> is your Db2 Warehouse on Cloud user ID, and <password> is your Db2 Warehouse on Cloud password.





2. Launch the InfoSphere Data Replication configuration tool and perform the following steps.
The passwords for the root user and the admin user are the same.
* You can change the passwords for admin user and root user for management services NSX ESG. The admin credentials are displayed in the VMware Solutions console, but the root credentials are not displayed. The passwords for the root user and the admin user are the same.







 Considerations when you change passwords for NSX-V components 



* You can change the NSX Manager password. This password is displayed on the Summary page of the instance in the VMware Solutions console.
* You can change the NSX Controller password. This password is not displayed in the VMware Solutions console, but you can set a new password without the old password. For more information, see [Change Controller password](https://docs.vmware.com/en/VMware-NSX-Data-Center-for-vSphere/6.2/com.vmware.nsx.admin.doc/GUID-2667DD9E-E2F5-4403-BAC2-C7D1BBC23228.html).
* You can change the password and the SSH settings for the customer-managed NSX ESG. This password is not displayed in the VMware Solutions console, but you can set a new password without the old password. For more information, see [Change CLI credentials](https://docs.vmware.com/en/VMware-NSX-Data-Center-for-vSphere/6.4/com.vmware.nsx.admin.doc/GUID-1DB9DE43-6B54-4FD1-903A-2DFFB87CD7FA.html?hWord=N4IghgNiBcIKYBMDmcAEAHMBnLB3A9gE4IgC+QA).
* Do not change the passwords for the management VMware NSX ESG and the related Distributed Logical Router.









 Related links
Both Allow users to sign up to your app and Allow users to manage their account from your app must be set to On.
2. Place the following code in your app to start the change password flow.

class delegate : AuthorizationDelegate {
public func onAuthorizationSuccess(accessToken: AccessToken?, identityToken: IdentityToken?, refreshToken: RefreshToken?, response:Response?) {
//User authenticated, and fresh tokens received
}

public func onAuthorizationCanceled() {
//change password canceled by the user
}

public func onAuthorizationFailure(error: AuthorizationError) {
//Exception occurred
}
}

AppID.sharedInstance.loginWidget?.launchChangePassword(delegate: delegate())
Show more









 Displaying the Login Widget with the Node.js SDK 

You can call preconfigured screens with the [Node.js server SDK](https://github.com/ibm-cloud-security/appid-serversdk-nodejs).

Add a post route to your app that can be called with the username and password parameters and log in by using the resource owner password.

app.post("/form/submit", bodyParser.urlencoded({extended: false}), passport.authenticate(WebAppStrategy.STRATEGY_NAME, {
successRedirect: LANDING_PAGE_URL,
failureRedirect: ROP_LOGIN_PAGE_URL,
failureFlash : true // allow flash messages
}));

WebAppStrategy allows users to sign in to your web apps with a username and password. After a successful login, a user's access token is stored in the HTTP session and is available during the session. After the HTTP session is destroyed or expired, the token is invalid.



 Sign up 



1.
Environment A list of key/values you set as environment variables. 
 Arguments 0... The information that is passed as arguments to the command shown in the Bin field. 
 Certificate Base64 A self-signed certificate that is used to confirm that an application is connecting to the appropriate server. It is base64 encoded. 
 Certificate Name The allocated name for the self-signed certificate. 
 Type The type of package that uses this connection information; in this case cli. 





* 0... indicates that there might be one or more of these entries in an array.







 Creating a command-line client connection 

Before creating a command-line client connection, ensure that you have [set the Admin password](https://cloud.ibm.com/docs/databases-for-postgresql?topic=databases-for-postgresql-admin-password) for your deployment.

The ibmcloud cdb deployment-connections command handles everything that is involved in creating a command-line client connection. For example, to connect to a deployment named "example-postgres", use the following command:

ibmcloud cdb deployment-connections example-postgres --start

or

ibmcloud cdb cxn example-postgres -s

The command prompts for the admin password and then runs the psql command-line client to connect to the database.

If you have not installed the cloud databases plug-in, connect to your PostgreSQL databases using psql by giving it the "composed" connection string. It provides environment variables PGPASSWORD and PGSSLROOTCERT. Set PGPASSWORD to the admin's password and PGSSLROOTCERT to the path or file name for the self-signed certificate.
For example, it has established a strong modeling pipeline for direct acoustic-to-word models ([Audhkhasi and others, 2017](https://cloud.ibm.com/docs/speech-to-text?topic=speech-to-text-referencesaudhkhasi2017), and [Audhkhasi and others, 2018](https://cloud.ibm.com/docs/speech-to-text?topic=speech-to-text-referencesaudhkhasi2018)) that it is now further improving ([Saon and others, 2019](https://cloud.ibm.com/docs/speech-to-text?topic=speech-to-text-referencessaon2019)). It is also making efforts to create compact end-to-end models for future deployment on the cloud ([Kurata and Audhkhasi, 2019](https://cloud.ibm.com/docs/speech-to-text?topic=speech-to-text-referenceskurata2019)).

For more information about the scientific research behind the service, see the documents that are listed in [Research references](https://cloud.ibm.com/docs/speech-to-text?topic=speech-to-text-references).
Path Path for a URI - for IBM Cloud® Databases for EnterpriseDB, it is the database name. The default is ibmclouddb. 
 Authentication Username The username that you use to connect. 
 Authentication Password A password for the user - might be shown as $PASSWORD 
 Authentication Method How authentication takes place; "direct" authentication is handled by the driver. 
 Hosts 0... A hostname and port to connect to 
 Composed 0... A URI combining Scheme, Authentication, Host, and Path 
 Certificate Name The allocated name for the self-signed certificate for database deployment 
 Certificate Base64 A base64 encoded version of the certificate. 





* 0... Indicates that there might be one or more of these entries in an array.



Many PostgreSQL drivers are able to make a connection to your deployment when given the URI-formatted connection string found in the "composed" field of the connection information. For example,

postgres://ibm_cloud_30399dec_4835_4967_a23d_30587a08d9a8:$PASSWORD@981ac415-5a35-4ac7-b6bb-fb609326dc42.8f7bfd8f3faa4218aec56e069eb46187.databases.appdomain.cloud:32704/ibmclouddb?sslmode=verify-full

This following example uses the information from your connection string and the Java driver [jdbc](https://jdbc.postgresql.org/documentation/head/index.html) to connect to your database.

import java.sql.Connection;
import java.sql.DriverManager;
import java.sql.ResultSet;
import java.sql.SQLException;
import java.sql.Statement;
import java.util.Properties;
import java.util.logging.;

public class PGConnect {

private final static Logger LOGGER = Logger.getLogger(Logger.GLOBAL_LOGGER_NAME);

private Connection connect() {
* To specify a maximum amount of time that the backup job can run, click Minutes or Hours in the Deferring list. In the adjacent box, type the maximum number of minutes or hours that the job can run.



When you use the deferring option, the backup job doesn't back up any new data after the specified amount of time, even if some data is not backed up. Changes to data that was previously backed up are still backed up, regardless of the amount of time specified.
8. To run the job on the specified schedule, select the Enable checkbox near the end of the row.
9. Click Save.







 Advanced Settings 



 Log file options 

When you create or edit a backup job, you can specify the level of detail for job logging. Select one of the following levels from the list.



* Files - this setting provides the most detailed information, and is typically used for troubleshooting. Provides information about files that are backed up.
* Directory - This setting provides less detail than the Files logging level. Provides information about folders that are backed up.
* Summary - This setting provides high-level information, including the vault and IBM Cloud Backup for Classic Agent version, and backup sizes.
* Minimal - This setting provides high-level information, including the vault and IBM Cloud Backup for Classic Agent version.



Changing the logging level affects only the log files that are created at that point and after. It does not affect previously created log files.





 Encryption settings and password 

Encryption settings specify the encryption type for backup data at rest on the vault. AES 256-bit encryption is the default encryption type that is available for new backup jobs. When you create a backup job, you must enter a password for the encrypted data. The password is case-sensitive. To recover the data, you must provide the encryption password that was entered when the files were backed up.

You can also enter a password hint. When you want to restore data, you can view the password hint to remind you of the encryption password for this job.

If you forget the encryption password, you lose access to the data. You cannot retrieve the password from the system.





 Performance Options
* Where <PATH_TO_SAMPLE_BIN_DIR> is the path to the sample applications bin directory you made note of in the Prerequisites section above.



2. Enter the application API key when prompted for a password.
3. Type in a test message.
4. Press Enter twice to exit the amqsputc sample.







 Get a message using amqsgetc 

In the same shell used in the previous step:



1. Run <PATH_TO_SAMPLE_BIN_DIR>/amqsgetc DEV.QUEUE.1 <your QMGR name>



* Where <PATH_TO_SAMPLE_BIN_DIR> is the path to the sample applications bin directory you made note of in the Prerequisites section above.



2. Enter the application API key when prompted for a password.



Your test message is displayed.

After a short period, the amqsgetc sample program should end after finding no more messages.





 Conclusion 

You have successfully:



* Connected to a queue manager using a sample application from your own machine.
* Put a test message onto a queue.
* Obtained the test message from the queue.
If you want to have spaces in the alias, surround the alias with double quotation marks.



2. Test connecting by issuing the db2cli validate command from the command prompt:

db2cli validate -dsn <alias> -connect -user <userid> -passwd <password>

where:



* <alias> is an alias that you created with the db2cli writecfg command.
* <userid> is your Db2 user ID.
* <password> is your Db2 password.



3. (Optional): To be able to connect local ODBC applications and tools to your database, register the DSN with the ODBC driver manager:

Run the following command from a command line:

db2cli registerdsn -add -dsn <alias>

where:



* <alias> is an alias that you created with the db2cli writecfg command.



By default, the DSN is created as a user DSN.
where <db_alias> is your name for the Db2 Warehouse on Cloud database and <user_id> is your Db2 Warehouse on Cloud user ID. You are prompted to enter your password.

db2 list tables

- Test the connection by using CLI. Issue the following command to connect to the Db2 Warehouse on Cloud database:

db2cli validate -dsn <alias> -connect -user <user_id> -passwd <password>

where <alias> is an alias that you created by using the db2cli writecfg command, <user_id> is your Db2 Warehouse on Cloud user ID, and <password> is your Db2 Warehouse on Cloud password.
Show more



4. Use the [connection information](https://cloud.ibm.com/docs/Db2whc/connecting?topic=Db2whc-db_details_cxn_credsdb_details_cxn_creds) that you collected beforehand to define a connection in the DataStage client. On the Parameters tab, you must select the DB2 Connector for the Connect using Staging Type field.



For details about defining a connection in DataStage, see the following DataStage documentation topics:



* [Creating a data connection object manually](https://www.ibm.com/support/knowledgecenter/SSZJPZ_11.3.0/com.ibm.swg.im.iis.ds.design.doc/topics/t_ddesref_Creating_a_Data_Connection_Object_Manually.html)
* [Configuring access to Db2 databases](https://www.ibm.com/support/knowledgecenter/en/SSZJPZ_11.7.0/com.ibm.swg.im.iis.conn.common.usage.doc/topics/t_configuring_db2conn.html)











 Lift 

Use Lift to migrate your data into Db2 Warehouse on Cloud.

[Lift](https://www.lift-cli.cloud.ibm.com/docs)





 InfoSphere Data Replication
The following table lists requestData fields that you can find in events that are generated when the IAM account settings are modified from the Access (IAM) > Settings dashboard:



Table 20. Account IAM settings requestData fields

 Field Type Description 

 team_directory_enabled Boolean Defines the status of the User list visibility restriction IAM account setting. <br>When it is set to true, users in your account can view other users from the Users page. 
 mfa String Defines the MFA method that is required for users to log in to the account. <br>Valid values are TOTP, and TOTP4ALL <br>This field is set to TOTP when the account requires MFA for non-federated users only. Users are required an ID, password, and a time-based one-time passcode to log in. <br>This field is set to TOTP4ALL when the account requires MFA for all users. <br>All users by requiring an ID, password, and a time-based one-time passcode. <br>When this field is empty, MFA is not enabled in the account, and all users log in by using a standard ID and password.