Have you upgraded to CABI 3.3 and applied SP1 and applied the hotfix (hotfix1)?
When you upgraded did you:
1. Disable Tomcat6 (CABI 3.3SP1 installs Tomcat7 but doesn't disable the previous version)
2. Run the post install steps regarding the CA_NVM_EXE directory? (I'm running everything on Windows so those steps may not be appropriate for Solaris - I can't even find the doc that mentions theses steps - it may be on the community somewhere - there is mention of it here in reference to CABI 3.2 but it still stands for CABI 3.3 https://communities.ca.com/message/98576473#98576473)
3. After installation of CABI 3.3 SP1 build on any base version of CABI (3.3, 3.2 + SP4 and 3.2 + SP5) CAF content (and any other custom content) will not work because of application server has been changed to Tomcat 7 from prior versions of Tomcat. So we have to redeploy those content manually using wdeploy commands.
Prior to trying the integration are you able to login to the Central Config Manager to see that Tomcat and SIA are running and you able to login to CABI Central Management Console ?
Your error mentions "dependencies" and you mentioned that the CMS was not started previously.
There is this note in the CABI release notes:
Central Management Server (CMS) Not Starting
Symptom:
After I start the BusinessObjects Enterprise server, I use the Central Configuration Manager to verify that all servers have successfully started. I notice that the Central Management Server (CMS) is stopped.
Solution:
Your CMS database is located on the same server, and the database service had not yet started.
To start the CMS
1. On the CMS properties Dependency tab, add the database service according to the database you are using (for example, MS SQLServer if you are using SQL 2005).
2. In the Central Configuration Manager, right-click Central Management Server, then click Start.
The CMS starts.
My biggest beef with this product is that the documentation is scattered to the four corners of the Universe and it's really easy to miss important notes.
The next biggest beef is that CA dismiss any comments about the product because it is a 3rd party product...But it's a 3rd party product that is purchased from CA to work with CA products!
Lesley