Service Virtualization

  • 1.  Specifying "Model Behavior" on CreateService REST Deployment

    Posted Aug 17, 2016 04:02 PM

    is there a way of specifying "Model Behavior" on CreateService REST Deployment?  Not sure if it would be in serviceProperties.xml or the VRS file.  I would like for them to start up in Learning mode.

     

    Thanks,

     

    Jeff Tucker



  • 2.  Re: Specifying "Model Behavior" on CreateService REST Deployment

    Posted Aug 19, 2016 08:49 AM

    I have included the property called "lisa.vse.execution.mode" in the config file.   For example, if you add this property to the config and set its value to "FAILOVER".  When the service is deployed, it will deploy in failover mode.

    FailOver.JPG

    I believe the following are the value settings for the various modes.

    EFFICIENT     - Most Efficient

    LIVE               - Live Invocation

    TRACK          - Tracking

    STAND_IN

    FAILOVER

    VALIDATION

    LEARNING

    DYNAMIC

    Also see this link in case you want to use the REST API: 

    https://docops.ca.com/devtest-solutions/9-0/en/reference…



  • 3.  Re: Specifying "Model Behavior" on CreateService REST Deployment

    Posted Aug 19, 2016 08:53 AM

    From the documentation:

     

    lisa.vse.execution.mode

    • EFFICIENT uses the most efficient path through a VS model.
    • TRACK records VSE activity at the VS level.
    • LIVE routes requests received by a VS model to a live system (somewhat like a pass through mode).
    • VALIDATION uses both VSE and the live system to determine a response. Both are recorded as tracking information and feed the model healing process. The live response becomes the response of the virtual service.
    • DYNAMIC invokes a script or subprocess for every request that must resolve to one of the other four modes. This approach is useful for tracking requests that only the virtual service model sees.
    • LEARNING automatically "heals" or corrects the virtual service to have the new or updated response from the live system.
    • STAND_IN first routes a request to the virtual service (the same as Most Efficient mode). However, if the virtual service does not have a response, the request is then automatically routed to the live system.
    • FAILOVER first routes a request to the live system (the same as Live System mode). However, if the live system does not have a response, the request is then automatically routed to the virtual service.

    Default: EFFICIENT