Connection Use and Reuse

Modules in OL Hub can either create their own connection or reuse an existing one. This ensures consistency across environments while avoiding duplicate setup.

Creating a New Module

When creating a new module, you can:

1. Create a New Connection

   • The new connection is automatically named after the module.
   • A Default Profile is created for it (empty properties, to be filled later).

2. Select an Existing Connection

   • Instead of creating a new one, choose from the list of existing connections.
   • Reuse their profiles (e.g., dev, qa, prod) without redefining backend details.

Working with Existing Modules

For an existing module, you can:

• Display and Test Connection Profiles Quickly check which profiles are linked and validate connectivity.

• Navigate to the Connection for Editing

  From there, you can:

  • Update descriptions or attachments
  • Add, edit, or delete profiles

• Change the Connection (Same Backend) A module can switch to another connection of the same backend type if required. This allows smooth migration (e.g., from a QA connection to a Production one).

Benefits of Reusing Connections

• Efficiency – no need to redefine backend details for every module.
• Consistency – shared settings across modules ensure reliability.
• Flexibility – easily switch environments by applying different profiles.
• Traceability – always know which modules depend on which connection.

Best Practices

• Use the Default Profile for initial setup, then extend with environment-specific profiles.
• Prefer reusing connections over creating new ones unless a different backend is required.
• Periodically review the Connections List to monitor dependencies.
• Clearly label profiles (dev, qa, prod) to avoid mistakes when reusing.