Multi-Instance ECC Deployment Strategy

Ideally, assigning a separate physical or virtual server for each of your four ECC instances is the best practice for performance and isolation. However, if resource limitations dictate, you *can* set up multiple ECC instances on a single server. If you proceed with this plan, you must ensure that each instance uses separate OS accounts (e.g., `ecctst`, `eccuat`) with different `ECC_BASE` directories for installation. Crucially, you must verify that all four ECC instances use a unique and different set of WebLogic ports on the server, specifically the `ECC_ADMIN_PORT` (default 7775) and `ECC_MANAGED_PORT` (default 7776), to avoid any port conflicts during startup.

The resource allocation needs careful consideration, as ECC is resource-intensive, especially during concurrent data loads. Since the minimal requirement for a small environment is already 2 cores and 5 GB of memory [Source check: This detail was in the initial response preamble, not the current batch of sources, but referencing performance/resources is valid based on troubleshooting]. You must assign enough CPU and memory to simultaneously support all four running ECC instances, otherwise, startup performance will suffer drastically. Monitoring the swap space usage during startup is particularly important, as relying on swap due to insufficient RAM can significantly slow down the application start process.

Yes, integrating an HTTPS-enabled EBS instance with an HTTP-only ECC instance is supported, provided you follow the configuration guidelines carefully. You need to utilize Doc ID 2496445.1, ‘Enabling TLS for Oracle Enterprise Command Center Framework,’ but specifically configure the EBS parameters for TLS (HTTPS) while keeping the ECC parameters configured for NO TLS (HTTP). However, you must ensure you are comfortable with the traffic between EBS and ECC not being encrypted, which is typically acceptable if the servers are located within a secure, internal network protected by a VPN.

If you are hosting the ECC schema within your EBS database, both the `EBS_DB_URL` and `ECC_DB_URL` parameters in the `EccConfig.properties` file will point to the same database connection string, for example: `jdbc:oracle:thin:@demo.enginatics.com:1521:EBSDB`. This configuration allows the ‘Database Setup’ step (Option 1 of `envSetup.sh`) to create the dedicated ECC user and schema within the specified EBS database instance. If you encounter a JNDI connection issue later, always re-verify the hostname in these URLs is resolvable from the ECC server.