Service Virtualization

  • 1.  Virtualization

    Posted Feb 02, 2017 08:22 AM

    Hi ,

     

    In our project due to some environment issue we want to replicate the Database. Is it possible to virtualize Database through Ca Devtest ? Please reply ASAP.



  • 2.  Re: Virtualization
    Best Answer

    Posted Feb 02, 2017 09:48 AM

    I would point out that we do not 'replicate' the physical database nor do we act like DBMS software; rather, we virtualize an interface between the application and the database.  

     

    Research the use and installation of the of the Java Agent and/or Application Insight as you consider how you will virtualize.

    DevTest Java Agent - DevTest Solutions - 10.0 - CA Technologies Documentation 

    Using Application Insight - DevTest Solutions - 10.0 - CA Technologies Documentation  

      

    You might also contact your CA Account team to ensure licensing is in place if you consider using Application Insight.  

     

    The high level approaches below are listed in least to most complex order. 

     

    1) Most recommended approach.  Java virtualization above the data access (DAO) layer.  At this layer, you are recording and virtualizing pretty much at the POJO class / method level.  You do not need to worry about managing the lower level handshaking that occurs as you move closer to the network layer.

     

    2) Next approach.  Agent-based virtualization of the JDBC layer between the application and database.  The drawback here is that you are starting to manage the virtualization at the Object to Relational mapping layer.  The virtualization begins to get more 'chatty' at this level.

     

    3) Least recommended due to deprecation and complexity.  JDBC Driver level virtualization has been deprecated so you would use the Agent.  When virtualizing at this layer, you are on the verge of virtualizing the network transport so your service has to deal with all of the low level chatter that occurs between the application and the database.  I believe the live database must remain intact because of low level pings and other activities that occur at the network stack. Due to deprecation of driver-based features, very limited CA Support is available.