Quantcast
Channel: SCN : Unanswered Discussions - Data Services and Data Quality
Viewing all articles
Browse latest Browse all 3719

Splitting of BOE and DS on AIX

$
0
0

Hi,

Please guide me to the correct place if I ask this question in the wrong place.

 

My customer has an installation of BOE 4.1 SP4 PL3 on AIX. On same server is Data Services 4.2 SP3 PL1 installed. Database is installed on separate server.

 

Now they want to have DS installed on another (clean) AIX server. I face error:

"No SIA Node Found

 

No valid local SIA nodes exist for the given CMS connection information.

You will not be able to install the following services: RFC Server, Administrator, Metadata exchange, and View Data)."

 

As far as I can understand from note 1837296, I should have a working SIA node. Thus, I have to fix this problem.

 

Correct? Or do I simply have to set up a SIA since I'm splitting the installation? (And should this SIA be on central server or local server or both?)

 

I have tried to look in Master Guide, Installation Guide and Administration Guide, without getting any wiser so far.

 

I have access to CMC, but I'm not able to identify if there is a "rouge SIA node" there. (Looks like there is no "SIA node" at all...)

From note 1891022 I find that a new SIA is created in CCM (Central Configuration Manager). But I have not been able to find out anything about CCM. How to start it, or from where. I'm accessing AIX via putty, so if it's an X utility, I have a problem... Can it be that svrcfg is the same tool, but in a "command prompt version"? (Except I find nothing about Server Intelligent Agent there...)


And I also wonder when and why a SIA is installed? When and for what it is needed? Knowing that would make it easier to figure out which problem I have...


I really hope someone out there find it in their heart to guide me in the right direction here.


Kind regards,

Gørril




Viewing all articles
Browse latest Browse all 3719

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>