Visual Builder

Get Involved. Join the Conversation.

Topic

    Rajeev Singh
    VBCS stand-alone Vs VBCS bundled in OICAnswered
    Topic posted October 4, 2019 by Rajeev SinghRed Ribbon: 250+ Points 
    87 Views, 4 Comments
    Title:
    VBCS stand-alone Vs VBCS bundled in OIC
    Summary:
    VBCS stand-alone Vs VBCS bundled in OIC
    Content:

    Is there any advantage and disadvantage of using stand alone VBCS vs VBCS bundled in OIC?

    Which one shall we use? One advantage which I see in using VBCS bundled in OIC is that i automatically get access to all the integrations developed in OIC through Service catalogue. I can directly start consuming the services in my VBCS application.

    Is there any way to achieve the same thing if I am using stand alone VBCS?

    Best Comment

    Shay Shmeltzer

    There are settings in your stand-alone VB tenant and the app level to map integration server to your VB instance.

    However if you want to use Process in OIC with VB you need to use the VB that comes with OIC.

    One difference between VB stand-alone and OIC is the licensing approach - OIC is licensing VB by concurrent end users using your apps. VB stand-alone is licensed per OCPU.

    Comment

     

    • Shay Shmeltzer

      There are settings in your stand-alone VB tenant and the app level to map integration server to your VB instance.

      However if you want to use Process in OIC with VB you need to use the VB that comes with OIC.

      One difference between VB stand-alone and OIC is the licensing approach - OIC is licensing VB by concurrent end users using your apps. VB stand-alone is licensed per OCPU.