Listener integration
Prior to Unica 12.0 release, Campaign and Optimize were separate products. Users having both Campaign and Optimize had to run separate listeners. The Campaign listener unica_aclsnr to run flowcharts and Optimize listener unica_acolsnr to run the Optimize session.
Campaign-Optimize merged scenario
With text-based license for v12, the listener image expects a license file at mount point.
If both listener host name txt (listener-0.txt …) and
opt.instance file exist, it will create only the Optimize listener. If listener host name
TXT contains the first listener, it creates the listener as
LISTENER_TYPE 3, which means it is for both Campaign and Optimize, otherwise it creates the listener
as LISTENER_TYPE 2 indicating that it is only for Optimize.
If the listener host name txt, listener-0.txt and so on, exists
and the opt.instance file does not exist, it creates the
listener as LISTENER_TYPE 3, which indicates that it is for both
Campaign and Optimize.
Listener types
- CAMPAIGN_ONLY (TYPE 1) - This listener can handle commands for Campaign or flowchart only.
- OPTIMIZE_ONLY (TYPE 2) - This listener can handle commands for Optimize session only.
- ALL ((TYPE 3)- This listener can handle commands for Campaign or Flowchart or Optimize session.