DB2 LUW

What’s a Rich Text element?

The rich text element allows you to create and format headings, paragraphs, blockquotes, images, and video all in one place instead of having to add and format them individually. Just double-click and easily create content.

Static and dynamic content editing

A rich text element can be used with static or dynamic content. For static content, just drop it into any page and begin editing. For dynamic content, add a rich text field to any collection and then connect a rich text element to that field in the settings panel. Voila!

How to customize formatting for each rich text

Headings, paragraphs, blockquotes, figures, images, and figure captions can all be styled after a class is added to the rich text element using the "When inside of" nested selector system.

Omni Loader supports the following authentication schemes:
  • SQL Server
    This is the standard username/password combination stored in and verified by the SQL Server.
  • AAD password
    This is Azure Active Directory password authentication.
  • AAD multi-factor
    Azure Active Directory multi-factor authentication will show a pop-up authenticating you as a separate step.
  • AAD integrated
    Azure Active Directory integrated authentication is an equivalent of what was used to be called Windows authentication for SQL Server.

Connection Details

Server

Enter the hostname or IP address for the DB2 LUW server. If the database is hosted on the same machine as the migration tool, use localhost.

Port

Specify the port number that the DB2 LUW service is listening on. The default is typically 50000, but it may be different based on your specific configuration.

Username

Type in the username that has the appropriate level of access to the database. For instance, db2admin is commonly used for administrative access.

Password

Enter the password corresponding to the username provided.

Database

Enter the name of the DB2 LUW database you wish to connect to.

Encryption

Select between Not encrypted and Encrypted to indicate whether the connection should use SSL encryption. For secure data transactions, especially when connecting over a network, Encrypted is advised to prevent unauthorized data interception.

Ensure that the users have the correct permissions to access the database and that the server information is accurate to prevent connection issues. Remind users to handle credentials securely and to use encryption whenever sensitive data is being transferred.

Data handling defines the way Omni Loader will generate the files and clean up:
  • Clear before run
    Everything in the container folder will be deleted before the data copying starts.
  • Clear after run
    Everything in the container folder will be deleted after the data copying completes.
  • Timestamped
    Nothing is deleted. On each run, Omni Loader creates a new folder named as the current time, then place the files inside the folder. This allows for a complete history, but may generate a large amount of data after many runs.
We support three modes of storage authentication:
  • Connection string
    This is the least secure mode which should not be used in production. It requires account key and grants full access to the whole storage account.
  • Managed identity
    A secure authentication mode, leveraging AAD to grant access to the resource.
  • Shared access signature
    A good middle-ground where one can easily grant access to either a whole account or a specific container only.