Skip to end of metadata
Go to start of metadata

In this tutorial, I show you how to identify your Tomcat SSL certificate, export it to .CRT, then import it into the Adaptive Processing Server / Adaptive Job Server SAPJVM so that you can schedule HTTPS based probes against your Apache Tomcat

 

 

  • No labels

11 Comments

  1. Will this method work with .pfx format certificates?  When I try to run the commands it tells me that the format is incorrect.

  2. Hi John,

    In the past, I've just converted the .pfx to .crt format before importing the certificate and that worked ok.

    Thanks
    Toby

  3. What did you use to convert the certificate?  I haven't had much success trying to do any type of conversion.

    1. Try this and see if it works for you:

      keytool.exe -importkeystore -srckeystore filename.pfx -srcstoretype pkcs12 -srcstorepass SRC_PASSWORD -srcalias SRC_ALIAS -destkeystore ../jre/lib/security/cacerts -deststorepass changeit -deststoretype JKS

  4. I was finally able to get back to this.  I am able to get the probe to connect to the base url but it is failing with the following error:

    Probe Name: BI launch pad

    Result: Failed Duration: 671 msec

    Diagnostic Messages: Attempting to connect to https://BI40TOMCAT:8443/BOE/BI

    Connected successfully to https://BI40TOMCAT:8443/BOE/BI

    Attempting to connect to https://BI40TOMCAT:8443/BOE/portal/1502270906/InfoView/logon.faces

    Attempting to connect to https://BI40TOMCAT:8443/BOE/portal/1502270906/InfoView/logon.faces

    Logon failed: The Regular Expression pattern "name="bttoken" value="([^=&";>]*)" in the response body is not found

    I replaced our url with the example from you article.

    1. Former Member

      Hi John,

      I am also having same issue. Did you manage to solve it?.

      I noticed that you used .../BI instead of .../portal as per Toby's screenshots. However, probe does not connect while using /portal in the URL for us.

      Do you know if ssl port is a requirement?

      Thanks,

      Luis Maestro

      1. No, I haven't gotten this solved.  I haven't been able to get back to this.

        I'm not exactly sure what you are referring to by the /BI.  The links I have above are what was being returned.  BI40TOMCAT is the default name the BusinessObjects assigns to the Tomcat instance when it is installed.  That is not something that I specified.

        Port 8443 is also the default SSL port. I would think this is something that is a requirement.

  5. Former Member

    Hi John,

    Thanks for your reply.

    Looking tutorial above BI Launch Pad's URL seems to be ending with .../portal , but in your  comment URLs ends ../BI . Anyways, I have tried both not success.

    However, It seems my issue is relate to Single Sign-On feature not supported with  Bi launch Pad. SAP analytic yotube video  "SAP BusinessObjects BI 4.1: Platform Monitoring Application"  (25:15) mentioned it  won't work and suggest to create a custom probe.

     

     

     

     

     

     

     

     

    1. Well, that disappointing but unfortunately not surprising that it doesn't work with Single Sign-On.  I had configured mine to use the Administrator login for my testing.  I suppose you could try using the URL for the No Single-Sign On, https://%server%/BOE/BI/logonNoSso.jsp but that wouldn't really test the BI Launch Pad that the users would necessarily be using.

      1. Unfortunately, using the no sso URL doesn't work with the InfoView probe.

        We've raised this as an enhancement request.  Hopefully it will be addressed in a future version soon.

    2. You might consider using a combination of probes to achieve a similar effect

      1.  Use the TCP probe to make sure your application server is listening.  This is a custom one attached to this article  http://scn.sap.com/docs/DOC-39449
      2. Use the CMS Logon probe to make sure your CMS is available for logon

      I know this isn't ideal but will get you most of the way there.