BO 4.0 SP8 APS Config Question (Clustered Environm...

Former Member · ‎12-15-2013

All, I have a clustered environment that is running two active CMS's and two Tomcat servers. I just upgraded from SP4 (which seemed to go fine), and configured the APS's according to sizing recommendations and assigned them to Node 1. Everything worked correctly, but when I attempted to set up the APS's on Node 2 (excluding LCM and Auditing) it keeps throwing an error at me (the argument has an invalid value 3194). It happens whether I try to clone the existing APS or set up a new one, and I am unable to even select/assign the node from the drop down. May be completed unrelated, but even starting/stopping servers on Node 2 through the CMC is problematic....

In an active/active clustered CMS environment, should I be able to replicate APS's across the two environments? I've been trying to read through every piece of documentation that I can find (APS Best Practices and Platform Admin Guide among them) but haven't made any progress. Sure there is something I am missing, so if there is more info that I can provide please let me know...

Thanks in advance,

Jeff

Former Member · ‎12-19-2013

Figured out what the issue was. According to the latest Companion Guide (page 25) there are groups of services that are what I guess you would call cluster-specific, meaning they can only reside once on the cluster. Then there are server-specific services that you can (and should) replicate across each of the nodes in your cluster.

My issue was being caused by my trying to add cluster-specific services to each node - so it was throwing my error. If you look at this image, you can see what I mean. The groups/services listed on the left (in blue) should be configured once within the cluster, whereas the groups/services on the right (in red) can/should be configured on each node for redundancy/failover purposes.

Following these guidelines I was able to create my APS's on each node without issue...

.

Former Member · ‎12-17-2013

I would agree - it made no difference that I can tell. I ran some traces and noticed the following:

This is node 2 of the cluster that is not working correctly. Note that I just pasted in one example - the other services on this node also threw the same message:

---------------------------------------------------

trc file: "jobserver_ALNPBIAPP02.AdaptiveJobServer_ncs.trc", trc level: 1, release: "720"

---------------------------------------------------

M

M [Thr 2840] Mon Dec 16 21:33:56 2013

M [Thr 2840] ***LOG Q0I=> NiPGetHostByName: '$SMDAgentHost' not found: getaddrinfo [ninti.c 895]

M [Thr 2840] *** ERROR => Main agent failed to be initilized due to incorrect host setting! [ncsmtdatasen 20]

M [Thr 2840] NCS trace timer is disabled since the interval is set to 0

M [Thr 2840] NCS data timer is disabled since the interval is set to 0

M [Thr 2840] NCS library version 2.3.9 (unicode) loaded

M [Thr 2840] NCS_ProcInit API invoked

M

M [Thr 2840] Mon Dec 16 21:41:30 2013

M [Thr 2840] NCS_ProcExit API started

M [Thr 2840] Timer threads are successfully finished

M [Thr 2840] Data sending threads are successfully finished

M

M [Thr 2840] Mon Dec 16 21:41:31 2013

M [Thr 2840] NCS_ProcExit API invoked

Here is the log for the ALNPBIAPP02.APS-All Other APS that I was trying to create. Note that the original APS wasn't saved in it's original form so I either need to clone the modified version or try to create them from scratch....

---------------------------------------------------

FILE_TYPE:DAAA96DE-B0FB-4c6e-AF7B-A445F5BF9BE2

ENCODING:UTF-8

RECORD_SEPARATOR:30

COLUMN_SEPARATOR:124

ESC_CHARACTER:27

SEVERITY_MAP: |None|S|Information|W|Warning|E|Error|A|Assertion|F|Fatal

HEADER_END

|317BA8EFC4134AC8A3470CD296D5E7100|2013 12 16 21:34:15.709|-0600|Error| |>>| | |aps_ALNPBIAPP02.APS-All Other| 3916| 21|Component Resolve Thread (Bundle 42)| ||||||||||||||||||||com.businessobjects.framework.servers.util.ModuleToBundle||Bundle D:\SAP BOBI\SAP BusinessObjects Enterprise XI 4.0\java\pjs\container\work\ALNPBIAPP02.AdaptiveProcessingServer4\modules\cdsframework.jar cannot be started

org.osgi.framework.BundleException: The bundle 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:1313)

at org.eclipse.osgi.framework.internal.core.AbstractBundle.getResolutionFailureException(AbstractBundle.java:1297)

at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:309)

at org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:280)

at com.businessobjects.framework.servers.util.ModuleToBundle.installAndStartBundle(ModuleToBundle.java:161)

at com.businessobjects.framework.servers.util.ModuleToBundle.modulesToBundles(ModuleToBundle.java:124)

at com.businessobjects.framework.servers.util.ModuleToBundle.activate(ModuleToBundle.java:41)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

at java.lang.reflect.Method.invoke(Method.java:597)

at org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:230)

at org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:140)

at org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:330)

at org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:560)

at org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:182)

at org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:292)

at org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:226)

at org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:124)

at org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:930)

at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:220)

at org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:149)

at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:757)

at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:712)

at org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:129)

at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:206)

at org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:506)

at org.eclipse.equinox.internal.ds.InstanceProcess.registerService(InstanceProcess.java:476)

at org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:198)