We have a (dev) server running two AOS instances on it. (Both instances connect to the same SQL instance, but using their own unique databases)
I have been developing some new features on the second instance of AOS that require the use of the Real-Time services between the AOS and POS. When I build out the Real-Time service profile I match what's populated in the IIS app pool. (ports, app name...ect). Set the POS profile to use the Real-Time profile then sent the data to the POS. When I try the feature it fails to connect to the head office. Now if I send the Real-Time profile setup on the first AOS instance, the POS can connect just fine. The issue is it's pulling data from the AOS 1 database, not the AOS 2 database.
When I look over Microsofts Real-Time service setup documents, there is a step to choose which AOS instance you want to install the component on. Since the Real-Time component was originally installed when the first instance of AOS was installed, I thought my issue could get resolved by reinstalling the Real-time component, but this time point it to the AOS 2 instance. During the reinstall, I'm never asked to choose any instance of AOS...
First, am I even chasing the correct rabbit with this theory? (Installing the Real-Time service to AOS instance 2)
Second, how can I get the DAX installer to allow me to choose an AOS instance the component will use?
Things to know:
DAX 2012 R2 CU7
