Configuring BMC Remedy Mid Tier to access BMC Remedy Smart Reporting
For latest version of this topic, go to the
Remedy Smart Reporting documentation
.
For configuration information, see
BMC Remedy IT Service Management deployment
.
By configuring the BMC Remedy Mid Tier settings, you can enable navigation from BMC Remedy Mid Tier to BMC Remedy Smart Reporting. After you complete the user onboarding and content import processes, you must manually update the BMC Remedy Mid Tier configuration to add the BMC Remedy Smart Reporting server details. If you do not complete this configuration, an error will be displayed when you try to access the BMC Remedy Smart Reporting console from the BMC Remedy Mid Tier.
To configure the BMC Remedy Mid Tier
- In the BMC Remedy Mid Tier configuration tool, click Report Settings.
Enter the BMC Remedy Smart Reporting information:
Field name Description Example Reporting URL (For a bundled Tomcat server) BMC Remedy Smart Reporting server host name and port number.
Note: This entry must end with a forward slash (/).
http://reporting-srv:8181/ (For an external Tomcat server) BMC Remedy Smart Reporting server host name, port number, and Smart Reporting context.
Note: This entry must end with a forward slash (/).
http://reporting-srv:8181/SmartReporting/ Admin User BMC Remedy Smart Reporting super administrator, as defined during the installation process siadmin Admin Password Password for the BMC Remedy Smart Reporting super administrator
Note: This password must be updated if the siadmin password for BMC Remedy with Smart Reporting is changed.
For more information about updating the siadmin password, see Changing the BMC Remedy Smart Reporting super admin password.siadmin Customer name Customer name provided in the onboarding wizard bmc Save your changes.
Note
If you get a validation error message, your changes are not saved. You must fix the errors for the changes to be saved. You can find detailed error messages in the BMC Remedy Mid Tier configuration log files.
Comments
Hello,
what is the procedure to configure Mid Tier to access to Smart Reporting's load balancer?
After onboarding, we need to configure SR link on Midtier configuration Page --> Report Settings --> Remedy Smart Reporting Information :
it works only for onboarded node, but if i set link of load balancer i get some errors.
Thanks
Best regards
Hi,
I will check with the SMEs and get back to you.
Regards,
Sirisha
Hi Paolo Quaranta,
Reporting URL in the Reporting Settings section can be used as Smart Reporting Load Balancer URL.
Please let me know if you used Reporting URL or something else for the load balancer? Also share the snapshot of the error.
Regards,
Sirisha
Hello Sirisha, i can't add screenshot here. When i try yo connect directly to Smart Reporting Load Balancer connection is successful. Editing Reportig Settings section, if i try to change the SR node with load balancer (onboarding was performed on single node) i can't save configuration (midtier is able to see LB). If I uncheck “Validate Smart Reporting Information” i can save the configuration, but when i open link with a valid SR user (on ITSM Applications Links [Applications --> Smart Reporting --> Smart Reporting Console). Regards Paolo
Environment Details :
Version : 9.1.03 , Patch 1
Issue Summary :
We have successfully configured and integrated Smart Reporting with MidTier with Tomcat.
But when we are trying to do the same with Midtier with Weblogic, we are getting “Internal Server Error” while validating Report Setting.
Error 500--Internal Server Error From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1: 10.5.1 500 Internal Server Error The server encountered an unexpected condition which prevented it from fulfilling the request.
When we check the mid tier log we found below entry.
<TID: 0000000063> <CATEGORY:com.remedy.log.DVMODULE > /* Wed Nov 08 2017 14:21:00.525 */ <LEVEL: SEVERE > <TENANT: null > <USER: amol.ratna > Exception while processing request java.io.IOException: Error during processing : java.util.ServiceConfigurationError: javax.xml.ws.spi.Provider: Provider weblogic.wsee.jaxws.spi.WLSProvider not a subtype at com.remedy.arsys.reporting.ReportFactory.processRequest(ReportFactory.java:87) at com.remedy.arsys.plugincontainer.impl.PluginServlet.postPluginInfo(PluginServlet.java:44) at com.remedy.arsys.plugincontainer.impl.PluginContainer.processRequestInfo(PluginContainer.java:86) at com.remedy.arsys.stubs.AuthenticationHelperServlet.doRequest(AuthenticationHelperServlet.java:82) at com.remedy.arsys.stubs.GoatHttpServlet.postInternal(GoatHttpServlet.java:98) at com.remedy.arsys.stubs.GoatHttpServlet.doPost(GoatHttpServlet.java:62) at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
Please let me know if there are any other configuration required for weblogic
Hi Amol,
Sorry for delayed response. I will check with the SMEs and get back to you on this.
Regards,
Vrishali
Hi Amol,
This issue needs further investigation. Please raise a ticket with BMC Support.
Thanks & Regards,
Vrishali
I have the same problem.
Hi Raphael,
Sorry for delayed response. I will check with the SMEs and get back to you on this.
Regards,
Vrishali
Hi Raphael,
This issue needs further investigation. Please raise a ticket with BMC Support.
Thanks & Regards,
Vrishali
Log in or register to comment.