vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Optional: Click Add if you want to provide more diagrams.
7. Click Update.
8. Review what you added, and click Next.





 Adding highlights 

You can add details that highlight the processes, abilities, and results of the version, or if applicable, the architecture variation. If you have multiple architecture variations, each variation should use the same highlight and then a unique description of how it does or doesn't meet each. Customers can use the highlights to evaluate the differences between variations. For example, you might want to list number of VPCs, network connectivity type, high availability capability, or other important factors that might be used to differentiate each variation.

If you included feature and highlight information in your catalog manifest file, it was automatically imported during onboarding. If not, complete the following steps to add highlights:



1. Click Add highlights.
2. Click Add.
3. Enter the name of the highlight that you want to feature. For example, Number of VPCs.
4. Enter a description. For example, if you chose Number of VPCs as the name of the highlight and, you can enter 2 as the description.
5. Click Update > Next.







 Adding prerequisites 

You can choose to list your deployable architecture as a full stack product or as an extension with prerequisites. If your product is an extenstion, you must list prerequisite products that users are required to deploy before this deployable architecture. These prerequisite products are listed on the deployable architecture's catalog page.

If you included a dependency section in your catalog manifest file, prerequisite information was automatically imported during onboarding. If not, complete the following steps:



1. From the Add prerequisites section, choose whether your product is a full stack or an extension. If your architecture is a full stack product, no further action is required.
2. If your product is an extension, click Add.
3. Enter or select the product that you want to add as a prerequisite.
4. Enter the required version or range of versions by using SemVer formatting.
$tempdbserial = "<SerialNumber>"
Get-Disk | Where SerialNumber -eq $tempdbserial | Initialize-Disk -PartitionStyle GPT -PassThru | New-Partition -DriveLetter "F" -UseMaximumSize | Format-Volume -FileSystem NTFS -NewFileSystemLabel "TEMPDB" -AllocationUnitSize 65536 -Confirm:$false -UseLargeFRS







 Install SQL Server 

The SQL Server installer has already been used to download the media and extracted the files onto the bastion host. Copy the required files from the SMB shared to the SQL server's local disk using the following PowerShell command Copy-Item "Z:SQL2019Extracted" -Destination "C:UsersAdministratorDownloadsSQL2019Extracted" -Recurse so that the install runs from local disk.

At this stage there are three options:



1. Run the installer interactively to install SQL Server.
2. Run the installer interactively to capture a ConfigurationFile.ini for a latter installation.
3. Use an existing ConfigurationFile.ini, i.e one form this set of documentation and install SQL Server.



This documentation assumes that you are using option 3, have created a ConfigurationFile.ini, and are using the following command to install the SQL Server:

C:UsersAdministratorDownloadsSQL2019ExtractedSETUP.exe /ConfigurationFile=C:UsersAdministratorDownloadsConfigurationFile.ini /TCPENABLED="1" /SQLSVCPASSWORD="<svc_password>" /AGTSVCPASSWORD="<agt_password>"

<svc_password> is the password for the domain service account used for SQL Server service and <agt_password> is the password for the domain service account used for SQL Agent.

By default, SQL Server is installed with TCP protocol disabled and /TCPENABLED="1" enables TCP.

Verify that TCP/IP has been enabled on the server's interface and the loopback address (127.0.0.1):
Provisioning 



 Process 

Important:

Customers must purchase (or own) App Points for MAS prior to (or in conjunction with) ordering the Maximo Application Suite as a Service (MAS-SaaS). The service provides AWS Cloud based hosting, product installation, operation, maintenance and support for MAS.

The provisioning process is invoked when a client has placed an order using MAS-SaaS part numbers.

Each client is provisioned in an environment that is separate and distinct from other clients. The provisioning is done to meet the specific customer requirements for a specific order. This means there is no pre-provisioning done and client environment provisioning begins when an order is placed.

The provisioning process has several steps, most of them automated, but some that require a manual update(s) to complete. The time frame to complete provisioning will depend on several factors including:



* the size of the order
* the order complexity
* the number of orders in the queue ahead of the order



In general, allow for at least 4 weeks for provisioning to be completed.

The provisioning itself can be broken down into a number of steps:



* Order validation
* Information gathering
* Initial provisioning of MAS base environment
* Provisioning of the individual MAS products the clients has requested
* Internal IBM verification of the provisioned environments
* Welcome letter sent to the client / designated contacts indicating provisioning is complete







 Order Validation 

Once an order has been placed, the initial step is to validate the order and the information submitted. This includes checking the part numbers, ensuring the provisioning form has been completed, performing IBM internal financial checks and setting up the order to be provisioned. In general this can take 1 to 2 days to complete.

Once this is complete, the order is sent to the IBM MAS-SaaS SRE Provisioning Team to begin the provisioning of the order.





 Information Gathering 

Once the order has been placed into the provisioning queue, additional information needs to be validated and gathered.
Deployment models for Caveonix RiskForesight 

Review the deployment models for Caveonix RiskForesight™ along with the installation process.

When you select the IBM Cloud® for VMware Solutions RiskForesight option, you do not have to follow all the steps in the deployment as the initial ones are automated. However, if you want to scale out the solution after the initial deployment, a detailed understanding of the complete deployment and architecture is required.

The RiskForesight installation consists of the following high-level steps:



1. [Initial planning and prerequisites](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-caveonix-step1) – Understanding and selecting a deployment option, configuring DNS to provide FQDN/IP resolution for the application components.
2. [Virtual machine deployment](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-caveonix-step2) – Deploying the VMs from an OVF template. All application components are installed on the VM.
3. [Application configuration](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-caveonix-step3) – Running the Caveonix configuration script that configures the application component on each of the VMs.
4. [Application setup](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-caveonix-step4) – Setting up the Service Provider and a Tenant or Organization so that the application becomes accessible for the users.



The automated installation provisions one VM and configures all the application components on that VM.



 Deployment sizing 

The sizing of the deployment is calculated by using the following volumes.



Table 1. Volumes

 Data type Volume 

 Scans per day 1 
 Scan data (MB) 20 
 Log data (MB) 500 
 Flow data (MB) 200 
 Asset data (MB) 46
* If you choose to take a backup as part of the promotion, the completion of that backup also needs to finish before the task completes. Again, this depends on the size of the database.



Remember that there is no High-Availability member until the promotion task completes. Likewise, if you have selected to have an initial backup, no backup exists until the second point completes or a manual backup is created.





 Upgrading while Promoting 

If you need to upgrade to a new major version of the database, you can do so when promoting a read-only replica to a stand-alone deployment. Full documentation on your upgrading options, is on the [Upgrading to a New Major Version](https://cloud.ibm.com/docs/databases-for-postgresql?topic=databases-for-postgresql-upgrading) page.
Provisioning with a cloud-init enabled image 

When you order a virtual server, many operating systems now use a cloud-init enabled image to optimize provisioning time. You can also import a customized image that you enabled for cloud-init.

The following operating systems now default to a cloud-init enabled image when you order a virtual server without add-ons. (Add-ons include extra software, post-provisioning scripts, and advanced monitoring.)



* CentOS 6, 7
* Debian 8, 9
* Red Hat Enterprise Linux 6.x, 7.x
* Ubuntu 16.04, 18.04
* Windows Server 2012, 2012 R2, 2016, 2019



When you order a virtual server with a cloud-init enabled operating system, you can add user data or metadata with custom provisioning scripts. In the User Data field on the order form, enter optional cloud-init user data or optional metadata for the server.



 Before you begin 

First, go to the device menu and make sure that you have the correct account permissions to complete the tasks.



* Go to your console's device menu. For more information, see [Navigating to devices](https://cloud.ibm.com/docs/image-templates?topic=virtual-servers-navigating-devices).
* Make sure that you have any necessary account permissions and device access. Only the account owner, or a user with the Manage Users classic infrastructure permission, can adjust the permissions.



For more information about permissions, see [Classic infrastructure permissions](https://cloud.ibm.com/docs/account?topic=account-infrapermissioninfrapermission) and [Managing device access](https://cloud.ibm.com/docs/virtual-servers?topic=virtual-servers-managing-device-access).





 Import a customized cloud-init enabled image 

If you created a customized image that’s cloud-init enabled, you can designate it as a cloud-init image on the Import Image page of the IBM Cloud® infrastructure customer portal.
Instance provisioning fails if the instance cannot be placed on a different power supply than all other instances in the placement group.

If a placement group is not specified when the instance is provisioned, the default placement strategy is to distribute customer instances among as many different physical hosts as possible. This approach is a best effort basis and does not guarantee the instances are placed on different physical hosts. To guarantee different physical hosts, specify a placement group during instance provisioning.







 Using placement groups with instance groups 

Instance groups (also known as autoscale groups) support instances that are provisioned with a placement group specification. Instance templates (used by instance groups) inherit the new placement group attribute. Any instances that are started within an autoscale group with a specified placement group are placed according to the placement group strategy. The instance group size is limited to the maximum size of the placement group.

Since placement groups for high availability strategies can use instances from multiple zones, you can use instance groups to support instances with subnets that span zones. For more information about instance groups, see [Creating an instance group for auto scaling](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-auto-scale-instance-group).





 Placement groups when an instance is resized 

When an instance is resized, the instance is stopped, the profile is updated, and the instance is restarted. When the instance is stopped, it is removed from its assigned node. When the instance is started again, the instance is then placed according to its defined placement group strategy, if a placement strategy exists for that instance. For more information, see [Resizing a virtual server instance](https://cloud.ibm.com/docs/vpc?topic=vpc-resizing-an-instance).





 Common use cases 



* Workload needs highest availability for critical application instances.



* Issue: Distributed application or database experiences an outage if any one of the application parts experience a failure.
* Solution: Use power spread placement group policy for independent power and network.



* Workload needs to optimize topology-aware applications.
More limitations and considerations 

Review the following considerations and limitations when you work with IBM Cloud® for VMware Solutions.



  Automatic installation of updates from Windows Update 

The Microsoft® Active Directory™ (AD) Domain Services server is automatically set up to download the updates only. It does not install these updates or restart automatically. You must install the updates manually and restart at a scheduled time that avoids any interruptions of the ongoing AD server configuration and other backup jobs. To apply Windows® updates, install the updates manually.
[root@sap-app-vsi ]# ls -als /dev/disk/by-id/ | grep 07a7-184b4a2f-d768-4 0 lrwxrwxrwx 1 root root 11 May 3 08:30 virtio-07a7-184b4a2f-d786-4 -> ../../vdb

In our example, it's virtio-07a7-184b4a2f-d786-4, which is linked to /dev/vdb.

1. Create a file system on this path:

[root@sap-app-vsi ] mkfs.xfs /dev/vdb



1. Find the related UUID in /dev/disk/by-uuid:



[root@sap-app-vsi ]# ls -als /dev/disk/by-uuid/ | grep vdb 0 lrwxrwxrwx 1 root root 11 May 10 08:31 1350230e-8058-4fe5-bbc0-cc27253ff778 -> ../../vdb

1. Add the UUID to /etc/fstab, in our example:

UUID=1350230e-8058-4fe5-bbc0-cc27253ff778 /db2 xfs defaults 0 0



1. Create a file system to use for the greater part of your installation, since we are using IBM Db2, we choose:



[root@sap-app-vsi ]# mkdir /db2 [root@sap-app-vsi ]# mount /db2

1. Add swap space for SWPM. We are adding a minimum swap space to the system.

[root@sap-app-vsi ] dd if=/dev/zero of=/swapfile bs=1M count=8192
8192+0 records in
8192+0 records out
8589934592 bytes (8.6 GB) copied, 24.701 s, 348 MB/s
FAQs 



  How is Windows patching handled? 

All of the Windows servers, like Active Directory and Cloud Connectors, can be configured to install updates automatically by using Windows update. Log in to the server manager to change your configuration and active hours as needed. You should have the most recent Windows security fixes and updates on these servers.
Creating an SQL Server configuration file 

To create a configuration file, use the SQL Server interactive installer wizard. Follow the wizard through to the Ready to Install page. The path to the configuration file is specified in the Ready to Install page in the configuration file path section.

For more information, see [Install SQL Server from the Installation Wizard (Setup)](https://docs.microsoft.com/en-us/sql/database-engine/install-windows/install-sql-server-from-the-installation-wizard-setup?view=sql-server-ver15).

To run the interactive installer, enter the following command:

C:UsersAdministratorDownloadsSQL2019ExtractedSETUP.exe /UIMODE=Normal /ACTION=INSTALL

The following key areas are applicable for the deployment patterns:



* SQL Server Instance Name - This option is left as the Default Instance. The name of the instance is MSSQLSERVER.
* Configuring SQL Server Service Settings - A domain account is used and the Startup Type is set to Automatic for the SQL Server Agent.
* Authentication Mode - Windows Authentication is used.
* Data root directory: D:
* System database directory: D:MSSQL15.MSSQLSERVERMSSQLData
* User database directory: D:MSSQL15.MSSQLSERVERMSSQLData
* User database log directory: D:MSSQL15.MSSQLSERVERMSSQLData
* Backup directory: D:MSSQL15.MSSQLSERVERMSSQLBackup
* TempDB Data Directories: F:



The following parameters were added or modified in the ConfigurationFile.ini:



* Change QUIET=”False” to QUIET=”True”.
* Change UIMODE=”Normal” to ;UIMODE=”Normal”.
* Change UpdateEnabled=”True” to UpdateEnabled=”False”.
* Add the line; IACCEPTSQLSERVERLICENSETERMS=”True”.





 SQL Server configuration file example
If a file is added in one statement and deleted in a second one, then the resulting image still contains the file in the layer for the first statement and then marks it as deleted in the second layer.

To save disk space, specify a single RUN statement to create a single layer for this set of commands,

FROM ubuntu

RUN apt update && apt upgrade -y && apt install -y nodejs && apt clean && rm -rf /var/lib/apt/lists/*

To maintain a readable Dockerfile with one line per command, add line breaks to your code,

FROM ubuntu

RUN 
apt update && 
apt upgrade -y && 
apt install -y nodejs && 
apt clean && 
rm -rf /var/lib/apt/lists/*

By using this type of statement, you can reduce the container image size from about 174 MB to approximately 147 MB. Note that your example sizes might differ as the Ubuntu base image and the Node.js package can change.

This type of best practice applies not only to package installations, but also to similar tasks. In the next example, the download and extraction of a software package, again Node.js, can look similar to the following example,

FROM ubuntu

RUN apt update
RUN apt upgrade -y
RUN apt install -y curl
RUN curl https://nodejs.org/dist/v16.14.2/node-v16.14.2-linux-x64.tar.gz -o /tmp/nodejs.tar.gz
RUN mkdir /opt/node
RUN tar -xzf /tmp/nodejs.tar.gz -C /opt/node --strip 1
RUN rm /tmp/nodejs.tar.gz
RUN apt remove -y curl
RUN apt clean
RUN rm -rf /var/lib/apt/lists/*

The rm command removes the downloaded nodejs package, but the multiple RUN statements again create separate layers. In addition, to download the nodejs package, the curl package is temporarily installed.
To verify that the CLI was installed successfully, run the help command:

ibmcloud help

The output lists the usage instructions, the current version, and the supported commands.





 Step 3: Install CLI plug-ins and tools 

To manually install the CLI plug-ins and tools, see [Extending IBM Cloud CLI with plug-ins](https://cloud.ibm.com/docs/cli?topic=cli-plug-ins).





 Step 4: Configure your environment 

Log in to IBM Cloud with your IBMid. If you have multiple accounts, you are prompted to select which account to use. If you do not specify a region with the -r flag, you must also select a region.

ibmcloud login

If your credentials are rejected, you might be using a federated ID. To log in with a federated ID, use the --sso flag. See [Logging in with a federated ID](https://cloud.ibm.com/docs/account?topic=account-federated_id) for more details.





 Next steps 

If you installed the CLI plug-ins and tools, you can start using IBM Cloud resources and services on the CLI. For more information, see [General IBM Cloud CLI (ibmcloud) commands](https://cloud.ibm.com/docs/cli?topic=cli-ibmcloud_cli). Also, keep in mind the [Getting help and support](https://cloud.ibm.com/docs/cli?topic=cli-getting-help) page if you have questions or problems.

Stay up to date with the IBM Cloud CLI by subscribing to the [IBM Cloud CLI releases repository](https://github.com/IBM-Cloud/ibm-cloud-cli-release/releases/). You'll receive notifications about new IBM Cloud CLI releases.

IBM Cloud CLI supports a plug-in framework to extend its capability. [Discover and install new CLI plug-ins](https://cloud.ibm.com/docs/cli?topic=cli-plug-ins)!
; Setup will display progress only, without any user interaction.

QUIETSIMPLE="False"

; Parameter that controls the user interface behavior. Valid values are Normal for the full UI,AutoAdvance for a simplied UI, and EnableUIOnServerCore for bypassing Server Core setup GUI block.

;UIMODE="Normal"

; Specify whether SQL Server Setup should discover and include product updates. The valid values are True and False or 1 and 0. By default SQL Server Setup will include updates that are found.

UpdateEnabled="False"

; If this parameter is provided, then this computer will use Microsoft Update to check for updates.

USEMICROSOFTUPDATE="True"

; Specifies that SQL Server Setup should not display the paid edition notice when ran from the command line.

SUPPRESSPAIDEDITIONNOTICE="False"

; Specify the location where SQL Server Setup will obtain product updates. The valid values are "MU" to search Microsoft Update, a valid folder path, a relative path such as .MyUpdates or a UNC share. By default SQL Server Setup will search Microsoft Update or a Windows Update service through the Window Server Update Services.

UpdateSource="MU"

; Specifies features to install, uninstall, or upgrade. The list of top-level features include SQL, AS, IS, MDS, and Tools. The SQL feature will install the Database Engine, Replication, Full-Text, and Data Quality Services (DQS) server. The Tools feature will install shared components.

FEATURES=SQLENGINE,REPLICATION

; Displays the command line parameters usage.

HELP="False"

; Specifies that the detailed Setup log should be piped to the console.

INDICATEPROGRESS="False"

; Specifies that Setup should install into WOW64. This command line argument is not supported on an IA64 or a 32-bit system.

X86="False"

; Specify a default or named instance. MSSQLSERVER is the default instance for non-Express editions and SQLExpress for Express editions. This parameter is required when installing the SQL Server Database Engine (SQL), or Analysis Services (AS).
This includes checking the part numbers, ensuring the provisioning form has been completed, performing IBM internal financial checks and setting up the order to be provisioned. In general this can take 1 to 2 days to complete.

Once this is complete, the order is sent to the IBM MAS-SaaS SRE Provisioning Team to begin the provisioning of the order.





 Information Gathering 

Once the order has been placed into the provisioning queue, additional information needs to be validated and gathered. This includes preparing the final architecture for the order; specifying the infrastructure needed to meet the order requirements; ensuring requested URL(s) are valid and available; detailed review of the order to ensure completeness; meeting or clarifying specific items with the sales person or client as required and setting up the provisioning parameters.

This step can take a few hours to several days depending on the initial quality and completeness of the information. Critical information that is needed includes:



* products that to be deployed (not all products will be deployed by default).
* anticipated sizing information for each product - this can be based on users, I/O or other metrics specific to each product URL being requested
* Languages required
* Add On and/or Industry Solutions required
* location of the majority of users to determine optimal placement of the Suite in the proper AWS data center



If this information is missing or incorrect it can cause delays in the provisioning process while this information is being confirmed.





 Initial Provisioning 

The initial provisioning covers several key aspects of the Maximo Application Suite deployment.

The base architecture is finalized regarding the size and number of OpenShift clusters needed. The provisioning of all based components and configuration is performed and the initial DNS registration for the Maximo Application Suite done. A temporary license file is installed. The client will need to supply the final license file.





 Provisioning of the Individual Products 

At this point, the products the client has selected is provisioned based on the sizing parameters that were specified. This includes deploying the appropriate containers within OpenShift and configuring the products to be available to the client. This includes the application, database, any network configuration required, DNS registrations and set up of client administration users.