How to get ready to install Unica Director?
Overview: Enterprise applications like Unica Campaign are usually deployed across complex architecture. For example – If the Campaign web application is installed on one machine (or storage), then the Campaign Analytical server (listener) is installed on a separate machine. The Campaign web application is deployed in standalone application server instance or in a clustered application server deployment. This is also possible for the Campaign Analytical server which can be deployed in the clustered environment. Now many of you would be asking; why we are talking about this deployment structure while planning to Install Unica Director. Let me try to explain this. For reference, we will be taking an example of the deployment architecture below to explain the Unica Director Server and Agent installation requirements. This reference deployment architecture includes a Load Balancer (or webserver), a clustered deployment of the Campaign web application and a clustered installation of the Campaign Analytical Server (listener) components. Unica Director – Server and Agent: Unica Director communicates in a server and client topology, the Server and Agent are two different components. The Server can be installed on any machine, this machine should not be a dedicated system but needs to be in the same subnet as Campaign components are deployed. The Server application provides capabilities like user interface, authentication, job queues, environment management, etc. The Agent should be installed on the system running the Campaign components, for example, the Agent needs to be installed on the system running Campaign Analytical Server. If the Campaign Analytical server is installed in a cluster, then the Agent needs to be installed on all machines. Also, the agent needs to be installed on a machine running the web application server where Campaign is deployed. If the web application is clustered, then the agent needs to be installed on all...