CMC and InfoView Refresh problem with WebSphere 6.1.0.15

server administration XI Server Discussion
1

Hi all

Everytime I make a change in the CMC (for example: I add a user to a group), BO won’t refresh the screens (example: each user’s group list will be the same. More obvious, I will schedule document1, look at the status in his history… ok… but then I look at document2 history and I see document1 history.

It’s kinda weird…

When using another CMC installed on Tomcat. Everything’s fine…

Anyone experienced this behavior with BO XI 3.0 installed on WebSphere?

Thanks!

jtrepanier :canada: (BOB member since 2008-09-01)

2

I don’t have the answer, but I have the same problem with WebSphere 6.1.0.7 - were you able to resolve the issue?

  • Penny

white-robie@lmco.com (BOB member since 2009-01-28)

3

Hello jtrepanier,

Penny and I have been working these same issues with Business Objects on our attempted installation on WebSphere 6.1.0.7. We are deploying XI 3.1, and we are on a clustered Solaris environment.

We were able to get past the User Group Authentication issue by following the steps listed below. We still have the problem with the history not updating properly. That issue is currently being analyzed by Business Objects so we don’t have that resolved yet. If we get an answer either Penny or I will post a separate response.

Let us know if this helps.

Scott

Applying security in CMC on Solaris
Users of Solaris UNIX may find that they cannot apply security rights properly
in the CMC. Administrators can use the following procedure to resolve the
problem.

  1. Launch the WebSphere admin console and stop the CmcApp web application.
  2. In the WebSphere console, go to Enterprise Applications > CmcApp > Manage Modules > CmcApp.war and select Classes loaded with application class loader first from the box.
  3. Repeat steps 1 and 2 for the CmcAppActions and PlatformServices web applications.
  4. Remove the xml-apis.jar from the CmcApp and CmcAppActions .war files.
  5. Restart the applications.

swswan (BOB member since 2009-01-28)

4

With the help of BOE support, we were able to resolve the history reporting problem by configuring the following application modules for the applications class loader order.

These are the steps we followed after deploying the BOE applications:

  1. Use the WebSphere Integrated Solutions Console to stop the BOE web application
  2. Select Enterprise Applications > CmcApp> Manage Modules then click the Module Link for the application - select Classes loaded with application class loader first from the Class loader order dropdown
  3. Click Apply and then Save
  4. Repeat steps 1 through 3 for the following applications:
    CmcAppActions
    PlatformServices
    CrystalReports
    AnalyticalReporting
    InfoViewApp
    InfoViewAppAction
  5. Stop and then start your BOE applications
  6. Test to see if History reports are now refreshing with correct details

Penny

white-robie@lmco.com (BOB member since 2009-01-28)

5

That’s exactly how we resolved the issue. I should have posted the steps like you did. Thanks for sharing the information.

jtrepanier :canada: (BOB member since 2008-09-01)