My client had installed the full BOXI 4.1 SP5, however the web application I proved runs in its own tomcat instance (locally installed not bundled).
So the aim was to use wdeploy to deploy all of the BO WAR files to the local tomcat instance. that worked fine.
We can connect to CMC ok but the application (ours) cannot connect to business Objects (using port 6405 for reporting)
Looking at the servers in CMC I noticed that the WACS was running with errors.
Stating that 'the following connector(s) failed to start HYYP.
Nothing has been configured on this.
To see if there was anything wrong with the method used, I took a VM with Business Objects installed and did the same as the Client did. installed tomcat and deployed the webapps to the tomcat\webapps.
Logged in through CMC and looked at the servers, I had no errors on WACS.
Never seen this before. has anyone got any ideas what this may be?
I’ve attached the log file for the WACs to see if that helps.
WACS runs on port 6405, tomcat by default installs on 8080. Are you trying to connect to the web services API ? the dswsbobje can run on Tomcat, but RESTful has to run on WACS at the moment.
The WACS doesn’t look very healthy, looks like you need to uninstall WACS and perhaps the ‘LifeCycle’ services and then re-install them.
2016 10 11 11:56:32.597|+0200|Error| |==|E| |wacs_apcss1t.WebApplicationContainerServer| 4782| 24|Component Resolve Thread (Bundle 69)| ||||||||||||||||||||com.businessobjects.framework.servers.util.ModuleToBundle||Bundle /Triad/BusinessObjects/sap_bobj/enterprise_xi40/java/pjs/container/work/apcss1t.WebApplicationContainerServer/modules/cdsframework.jar cannot be started
org.osgi.framework.BundleException: The bundle "cdsframework_0.0.0 [121]" could not be resolved. Reason: Missing Constraint: Require-Bundle: cdz_ext_lifecycle; bundle-version="0.0.0"
at org.eclipse.osgi.framework.internal.core.AbstractBundle.getResolverError(AbstractBundle.java:1327)
It then complains about the CMS being unavailable:
Unable to find servers in CMS ap-css1t.oneadr.net:6400 and cluster @ap-css1t.oneadr.net:6400 with kind cms and service null. All such servers could be down or disabled by the administrator
(BOB member since 2008-10-27)
(BOB member since 2002-08-15)