The TIBCO Platform is a real-time, composable data platform that will bring together an evolving set of your TIBCO solutions - and it's available now!
A chart showing the TIBCO Platform vision
Jump to content
Articles
Read more about TIBCO use cases, product features, capabilities and more
  • BW5.X - How to switch between HTTP and HTTPS using a runtime configuration in BusinessWorks 5.X


    It is quiet common to use different connection configurations in runtime environments, like for example to use a simple HTTP connection in a test environment and an HTTPS connection in the production environment.

    In BusinessWorks 5.X this is not possible to switch HTTP based Process Starters (HTTP Receiver and Service) between HTTP and HTTPS using a runtime configuration (or more precisely not that I know) but this is possible for SOAP and REST client.

    Switching between HTTPS and HTTP in a SOAP Request Reply activity

    This can be done with the following:

    . Configure the SOAP Request Reply activity for HTTPS using the following in the ‘Transport Details’ tab:

    - An URL using https

    - An SSL configuration

    1*M3AsTTJVW5YpXYwtGAfdYw.png

    . Then in the ‘Input’ tab set the URL dynamically using ‘http’ to just do HTTP or ‘https’ to do HTTPS and use the defined SSL configuration

    Example of using http in the runtime configuration:

    1*kmkoZqFzHRKOAliiyCPNyw.png

    In a real application this is usually managed using a Global Variable.

    Switching between HTTPS and HTTP in a REST Invoke activity

    This can be done with the following:

    . In the ‘Input’ tab set the URL dynamically using ‘http’ to just do HTTP or ‘https’ to do HTTPS

    Example of using https in the runtime configuration:

    1*rB_GU_LXpYVqijuYdbFnKg.png

    In a real application this is usually managed using a Global Variable.

    Note that in the REST Invoke activity there is no SSL configuration. This activity relies on the BW_GLOBAL_TRUSTED_CA_STORE Global Variable to know in which directory to look for trusted public certificates.

    It is also possible to rely on the JVM default keystore to manage the needed public certificates when HTTPS is used. The TIBCO JVM default keystore is the file named ‘cacerts’ present in the following folder : <TIBCO_HOME>\tibcojre64\1.8.0\lib\security

    For more details you can check the following TIBCO support KB article:

    https://support.tibco.com/s/article/Tibco-KnowledgeArticle-Article-38273

    Additional elements

    You can refer to the attached sample project.

    HTTP-HTTPS-Demo.zip


    User Feedback

    Recommended Comments

    There are no comments to display.



    Create an account or sign in to comment

    You need to be a member in order to leave a comment

    Create an account

    Sign up for a new account in our community. It's easy!

    Register a new account

    Sign in

    Already have an account? Sign in here.

    Sign In Now

×
×
  • Create New...