Share:|

Where is New CMDB UI hosted?

CMDB New UI is NOT hosted in mid-tier.

It is hosted on AR contained Jetty server.

 

Can I access the new CMDB UI from mid-tier?

Yes, From the home page fly-out menu, Atrium Core – Click on Configuration Manager Dashboard.

 

If I want to access new CMDB UI without mid-tier, can I do that?

Yes, below are typical urls for accessing new CMDB UI :

http://<ARServer>:<Jetty Port>/cmdb/index.html or https://<ARServer>:<Jetty Port>/cmdb/index.html

http://localhost:8008/cmdb/index.html or https://localhost:8008/cmdb/index.html

 

Are there any explicit configurations required for accessing new CMDB UI from Mid-Tier?

If there are no load balancers configured on AR Server, CMDB installs the configurations out-of-box and no explicit action is required, including in server group environments.

If you require any modifications due to jetty port change, https configuration change or server name modification or load balancer configurations then only you need to modify these

parameters.

 

Where can I find the configurations for accessing new CMDB UI from Mid-Tier?

Home Page Flyout menu – AR System Administration Console – System – General – Centralized Configuration – com.bmc.arsys.server.sahred – shared

Make sure that Jetty Port is correct. The out-of-box value is 8008. If you have modified the Jetty port, please reflect in Jetty Port parameter here.

Redirect-URL parameter will typically have following values :

cmdb.<ARServer>::http://<ARServer>:<Jetty Port>/cmdb/index.html;

 

How to configure for accessing new CMDB UI from Mid-Tier in server group environment?

If there are 2 servers in server group, ARServer1 and ARServer2,

then in such cases, Redirect-URL parameter will typically have following values :

cmdb.<ARServer1>:http:// <ARServer1>:<Jetty Port>/cmdb/index.html;<ARServer2>:http:// <ARServer2>:<Jetty Port>/cmdb/index.html;

Again, when you install server group, these values are populated by CMDB installer. If you require any modifications due to jetty port change, https configuration change or server name modification or load balancer configurations then only you need to modify these parameters.

 

How to configure for accessing new CMDB UI from Mid-Tier in server group load balancer environment?

If there are 2 servers in server group, ARServer1 and ARServer2 , with AR load balancer as remedy.bmc Redirect-URL parameter will need to change as follows

cmdb.<ARServer1>:http://remedy.bmc:/cmdb/index.html;<ARServer2>:http://remedy.bmc:/cmdb/index.html;

 

How does mid-tier access the new CMDB UI?

Mid-Tier looks for Redirect-URL parameter values. It looks for the same server from which context url is launched :

http://<MidTier Host>:<Mid Tier Web Server Port>/arsys/forms/<ARServer>AR+System+Customizable+Home+Page/Default+Administrator+View

Make sure the ARServer value here matches the one in Redirect-URL parameter i.e.

cmdb.<ARServer>:http://<ARServer>:<Jetty Port>/cmdb/index.html;

 

Are there any changes in Mid-Tier to access the new CMDB UI?

There is new servlet - ExternxalLaunchPointServlet released in SP4, so midtier version must be SP4 only.

This servlet (ExternalLaunchPointServlet) and its mapping configured under web.xml of midtier, please check if entry for same is present in midtier’s deployment descriptor i.e. midtier/WEB-INF/web.xml file.

 

How do we know if mid-tier servlet is getting called while accessing new CMDB  UI?

You can check the logs to find out if the servlet is being hit by setting the mid-tiers log level to Fine.

Once you set the log level hit the servlet and check midtier logs, you should see “Entering ExternalLaunchPointServlet” getting printed in the logs.

 

What if the customer has customized web.xml?

If web.xml is customized then after upgrade, you should add following :

 

<servlet-mapping>
<servlet-name>ExternalLaunchPointServlet</servlet-name>
<url-pattern>/launch/*</url-pattern>
</servlet-mapping>

 

If customer does not use /arsys context for Mid-Tier?

In such scenario, as Active link CMDB:LaunchCMDBConsole has a hard coded URL that includes

/arsys PERFORM-ACTION-OPEN-URL /arsys/launch/cmdb

you don’t use the default of arsys for your midtier context, then you need to customize this active link accordingly.

 

How does new CMDB UI handle requests?

With RSSO Configured :

  • Login credentials are accepted by RSSO and sent to AR server
  • AR server sends back the token to RSSO
  • RSSO stores the token ID in browser cache
  • CMDB New UI picks the token ID and attached to each request sent to AR server.

Without RSSO :

  • Login credentials are accepted by CMDB new UI and sent to AR Server
  • AR server sends back the token to CMDB new UI
  • CMDB New UI stores the token in browser cache
  • CMDB New UI send this token with each request sent to AR server.

 

Customer’s REST APIs stopped working after SP4 in RSSO environment. What do I do?

When you enable RSSO for AR, as Jetty is embedded in AR and the REST API is also running on Jetty and Jetty is enabled with RSSO, so making all the REST calls fail due to redirection to RSSO.

In such case, in server’s 'rsso-agent.properties' file’s exclude url should contain /api/jwt/login* so that existing REST APIs are not redirected to RSSO.

 

excluded-url-pattern=.*\\.xml|.*\\.gif|.*\\.css|.*\\.ico|/shared/config/.*|/WSDL/.*|/shared/error.jsp|/shared/timer/.*|/shared/login_commn.jsp|/shared/view_form.jsp|/shared/ar_url_encoder.jsp|/ThirdPartyJars/.*|/shared/logout.jsp|/shared/doc/.*|/shared/images/.*|/shared/login.jsp|/services/.*|/shared/file_not_found.jsp|/plugins/.*|/shared/wait.jsp|/servlet/GoatConfigServlet|/servlet/ConfigServlet|/shared/HTTPPost.class|/shared/FileUpload.jar|/BackChannel.*|/servlet/LicenseReleaseServlet.* |/api/jwt/login*

 

Any other useful links? Go on Docs pages

 

 

-Raj

handle