cancel
Showing results for 
Search instead for 
Did you mean: 

Lumira BI Addon openDoc Url / CMC App issue

NTruhan
Participant
0 Kudos

Hello,

First, sorry for the long message.

I have a few setups containing Lumira 1.29 with BI 4.1 SP4 Patch 5 of various sizes and one of 4.2 SP3 with Lumira 1.31.1 as a test install.

The newest one is a single server install to test functions and after the install I nocied I had an option in the CMC -> Applications for SAP Lumira which had a few empty entries for cloud, bi server, etc...   In comparing to my other environments which have the web and application seperated onto two or more servers, the SAP Lumira option is missing from the CMC Applications, but Lumira still works and I am able to run reports from within Launchpad.

What brought this up though is that when generating openDocument links for Lumira reports, it is using the default openDoc URL based on the server that lumira is installed on and not what is in the openDocument application properties in the CMC.  What we are running into with this, is it works internally since users can see the other server, but they need to be able to connect to the server hosting openDocument that others are connecting to.  I was trying to find the setting in Lumira BI Server that defines this when I realized the integration pieces are missing.

So I guess my question is two fold.  How can I force Lumira server to generate openDocument url's from a specific server and not itself (like what is defined in the openDocument App settings) and secondly, how can I get the SAP Lumira application to integrate into the CMC applications?

I did check the logs on the web-only server where the CMC is and lumira web components were installed and I did get this:

12:59:11.347 2016/06/16, 12:59:11: GetBOBJCADServices found BOEXI40SIAAWSSRV001, adding in as a service to start/stop.

12:59:11.347 2016/06/16, 12:59:11: GetRunningSIAServices: Service BOEXI40SIAAWSSRV001 is running. Adding to list of running services...

12:59:11.347 2016/06/16, 12:59:11: StopSIAService: Running SetSIAStateWithRetry with args: BOEXI40SIAAWSSRV001, false

12:59:11.347 2016/06/16, 12:59:11: SetSIAStateWithRetry: Running with args: |BOEXI40SIAAWSSRV001| |stopping|

12:59:11.347 2016/06/16, 12:59:11: SetSIAStateWithRetry: stopping service BOEXI40SIAAWSSRV001

12:59:11.347 2016/06/16, 12:59:11: Attempting to stop Service BOEXI40SIAAWSSRV001, current status is 4, existing error code: 0

12:59:11.363 2016/06/16, 12:59:11: Expecting SERVICE_STOPPED

12:59:11.363 2016/06/16, 12:59:11: QueryServiceStatus: Service: BOEXI40SIAAWSSRV001: CheckPoint: 2, State: SERVICE_STOP_PENDING, Hint: 3000

...

12:59:17.634 2016/06/16, 12:59:17: ChangeService: Service: BOEXI40SIAAWSSRV001: check point was not updated for 6 seconds

12:59:17.634 2016/06/16, 12:59:17: ControlService function exiting (0)

...

12:59:27.648 2016/06/16, 12:59:27: SetSIAStateWithRetry: ControlNTService failed stopping service BOEXI40SIAAWSSRV001. Retrying 2 of 5...

12:59:37.663 2016/06/16, 12:59:37: SetSIAStateWithRetry: stopping service BOEXI40SIAAWSSRV001

12:59:37.663 2016/06/16, 12:59:37: Service BOEXI40SIAAWSSRV001 already stopped, ignoring request...

12:59:37.663 2016/06/16, 12:59:37: SetSIAStateWithRetry: ControlNTService succeeded in stopping service BOEXI40SIAAWSSRV001.

12:59:37.663 2016/06/16, 12:59:37: StopSIAService: List of services stopped to set as property: BOEXI40SIAAWSSRV001;

12:59:37.663 NativeActionExecutor: restoring path.

12:59:37.663 NativeActionExecutor: entry point returned successfully.

I also see a couple of these errors

Committing DFO file(s) for PolestarExplorationServiceContainer...

ERROR: Cannot commit ServerIntelligence_ServiceContainer_PolestarExplorationServiceContainer_To_Install_dfo_frag.xml. The DFO data is older than the DFO in the repository. The following properties are causing the problem: SI_RELATIONSHIPS.SI_ADM_SET_CONTAINER_INSTALL.1.SI_EXEC.SI_ARGS.

But they don't seem related.

Thank you,

Nathan

Accepted Solutions (1)

Accepted Solutions (1)

former_member183750
Active Contributor
0 Kudos

I agree with Mani. This is the statement that is of import in this case:

The DFO data is older than the DFO in the repository.

So, I suppose the next question is; now what? Answer; use a clean system and see if that helps.

If the server you are using has had previous installs of Lumira, uninstall those (you will see them in Add | Remove). Then do a brand new install of Lumira 1.31.1.

- Ludek

Senior Support Engineer Product Support

Follow us on Twitter (#SAPLumira)

Got Enhancement ideas? Use the SAP Idea Place

Answers (2)

Answers (2)

NTruhan
Participant
0 Kudos

Thank you for the help.

I am sorry I didn't reply earlier on this, what I noticed afterwards is that some of the dfo's were not getting deployed and I had to either re-deploy the dfo's or copy them in place per a couple sap notes I found about moving those after the fact.

I have been monitoring the system and so far it seems to be working without any issues.

former_member182521
Active Contributor
0 Kudos

Look like there is an issue with your earlier Explorer add on installation. (PolestarExplorationServiceContainer).

Thanks

Mani