HPE Service Virtualization
Software Version: 3.80
Document Release Date: December 2015
Software Release Date: December 2015
Note: To verify that you are using the most recent version of this document, or to check for recent updates of any other HPE Service Virtualization documentation, visit the HPE Software Product Manuals site (requires an HPE Passport).
This file provides the following information about HPE Service Virtualization 3.80:
This section provides an overview of the features that are introduced or enhanced in HPE Service Virtualization 3.80. For additional details, see the HPE Service Virtualization User Guide, or the Help Center within the application.
Protocols and virtualization enhancements
Java Virtualization. Introduced support for the virtualization of Java applications. You can simulate Java method calls and configure runtime for on the fly virtualization.
Files over FS and FTP/S. Added support for virtualization of file transfers over the general file system and FTP. You can use XML and flat file based communication, such as comma separated values and other text based formats.
ISO 8583. Added the ability to simulate ISO 8583 messages using configurable and extendable JPOS bridge. You can virtualize applications using ISO 8583 by converting native communication into XML over HTTP. Service Virtualization also contains a JPOS bridge configuration accelerator, enabling quick adjustments of unsupported JPOS formats.
Local MQ Binding. Improved performance for MQ communication when Service Virtualization is deployed on the same machine as the WebSphere MQ server, by enabling a direct local connection to the MQ queue manager.
Root Element Routing (Lab feature). Improved Data Model maintenance and simulation performance by adding the ability to divide an XML over MQ service into multiple virtual services, and by adding routing based on an XML message root element.
Virtual Service management and logging enhancements
Web Accessible Message. You can now enable and disable message logging and investigate logged messages directly from the Service Virtualization Management Interface. You can leverage the bulk operation functionality for message logging configuration or investigate flows and differences between logged messages.
Runtime Message Logging. You can now enable and disable message logging without needing to restart the virtual service. This functionality is available in both the Service Virtualization Designer and the Service Virtualization Management interface.
Virtual Service Statistics. Improved virtual service statistics user experience and performance.
Integration and performance improvements
Integration with NV v9.00. Added integration with HPE Network Virtualization 9.00, enabling the configuration of network conditions directly within Service Virtualization environments.
Performance Model Improvements. Improved performance of simulation mode when a performance model is used in the simulation.
Java Script Rule Performance. Improved performance of simulation mode when Java Script is used in the Data Model.
Other improvements
Product Stability. Improved stability of the Service Virtualization Designer and the Service Virtualization Management interface.
HPE Rebranding. The Service Virtualization Designer and the Service Virtualization Management interface were modified to conform with the new company brand standards.
Step-by-step installation instructions for Service Virtualization can be found in the HPE Service Virtualization Installation Guide. The Installation Guide is available in PDF format in the root folder of the Service Virtualization installation package.
You can also open the Installation Guide from the Windows Start menu after installation.
Service Virtualization Server upgrade: To work with FIPS mode and Service Virtualization 3.80, enable FIPS only after successfully installing Service Virtualization Server 3.80.
This section includes:
Minimum hardware configuration
Recommended hardware configuration
For a complete list of all supported operating systems, database servers, browsers, and development environments, see the Service Virtualization support matrix on the HPE Software Support site at: https://softwaresupport.hp.com/group/softwaresupport/support-matrices.
Minimum hardware configuration
The HPE Service Virtualization Server 3.80 and HPE Service Virtualization Designer 3.80 can run on any hardware configuration that is using a supported operating system and has at least 1GB of physical memory installed and available for each product.
With the minimal hardware configuration, you can perform all functional testing scenarios and some basic performance testing scenarios, provided that they do not create too much load on virtualized services.
Recommended hardware configuration
Virtualization hardware sizing is complicated and may include many factors. For detailed sizing recommendations, contact HPE Customer Support. For contact information, see HPE Software Support Online.
The following hardware configurations provide a good performance balance for normal usage scenarios, where each product is installed on a separate machine.
| Service Virtualization Designer |
|
| Service Virtualization Server (32-bit edition) |
|
| Service Virtualization Server (64-bit edition) |
|
| Database server |
|
The following issues were fixed since the last released version:
JDBC issue: ClassCastException from application receiving virtualized data (data type mapping).
Problem: The HP SV JDBC driver often converts data to a type which is not compatible with the code, causing a ClassCastException. Data is converted into String when the code is expecting CLOB.
Solution: Mapping can now be configured per each data source by specifying a resource in the JAR file or in another file in the file system.
Service Virtualization locks out the Windows user account when it is disconnected from the network.
Solution: Service Virtualization Management (SVM) does not load data from the Service Virtualization Server when the user credentials are not valid. Data is refreshed when valid credentials are available.
Service Virtualization does not upgrade TSYS MAINT Soap Over MQ project.
Problem: The issue is caused by an added or removed element on a parent type.
Solution: All descendants and parents of the removed/added element are now properly updated.
JDBC: Unsupported SQL Type: 1111 (JSON) - PostgreSQL backend - Request.
Solution: Support was added for the org.postgresql.util.PGobject type.
JDBC issue: Invalid data conversion error.
Solution: Fixed converter.
Reading MQ message fails when it contains RFH2 header and is sent via JMS.
Problem: Intrusive MQ fails to read messages when the queue extended property control is set to "Force MQRFH2".
Solution: MQMessage.Format is checked for MQC.MQFMT_RF_HEADER_2 value. If it matches, the header is partially parsed (getting the header length) and the header content is skipped, so that the next call to ReadString gets to the real payload. No (meta)data from this header is passed to the processing chain.
Problem with populating the JSON response in a REST Service Virtualization instance.
Problem: In a REST virtual service, adding a third URI space breaks the functioning of the virtual service.
Solution: All the properties with the same name in all sub-types are set when any property is written to. If the properties are different data types, an exception is raised and the rule is not executed. In addition, just one property is added to the HPSV object. The type is based on the first property with the assigned name that is created.
Writing RFH2 message fails.
Problem: The problem occurs with MQ messages using intrusive MQ and containing RFH2 headers. The Designer fails to pass the message through to the real service and reports an error about creating an invalid header.
Solution: If the message is generated with RFH2 format, the minimal/false RFH2 header is inserted before the real payload.
JDBC issue: Unsupported SQL type 1111 for PostgreSQL DB - Response.
Solution: Enabled reading the JSON value stored in the PGobject value as String.
Intrusive MQ not passing message headers correctly during recording.
Solution: When the compensating flag MQC.MQGMO_PROPERTIES_IN_HANDLE on the GetOptions function is used, the properties load correctly.
Request: Add the option to sort runtime view by the messages column.
Problem: In a project with many virtual services, you need to scroll through the Runtime view to find the services that have received messages. This could be a lot quicker if you could sort by the 'Messages (Unique)' column.
Solution: In the Runtime view, you can sort the virtual services.
Request: Introduce virtual service splitting by operation name (root element routing).
Problem: A Service Virtualization MQ project using SOAP over the MQ protocol is too big.
Solution: Virtual service configuration now enables you to specify a request/response "root" element name, which indicates a subset of the messages. Only the messages with the specified root element are consumed by the service.
SOAP virtualization issue: WSSE Signature Verification failure (original request forwarding).
Solution: Added the SignBodyAndHeaders security scheme.
Request: Add support for multi-occurrence choice schema learning.
Problem: SOAP over MQ does not work without WSDL.
Solution: xs:choice learning was implemented.
Request: Add PATCH method to REST verb.
Problem: Service Virtualization does not support the PATCH method in a RESTful service implementation.
Solution: PATCH verb support was added. After a patch is applied, you must create a new REST virtual service in order to have full PATCH verb support.
IE8.
Microsoft Internet Explorer 8 in no longer supported: Apply the procedure from http://support.microsoft.com/kb/323308 and then restart your computer.
JDBC.
The following JDBC types are not supported:
REST services.
The wildcard character * as string was deprecated. As of Service Virtualization version 3.70, the wildcard character * is not supported as a string. The wildcard characters * or ** now represent wildcard segments. For example, a*b is not supported. The new supported format is a/*/b, where * represents any segment value.
Migration limitation for projects with REST services . Because of deprecation of the string wildcard * , Service Virtualization converts any instance of the string wildcard in a URI space to **. This wildcard format represents one or more segments of any value. For example, a*b is converted to **.
If there are multiple uses of the string wildcard in a URI space that would convert to duplicate entries according to the new format, migration fails. For example, both /some/a*b and /some/c*d would be converted to /some/**. In this case, contact HPE Support to assist you in project migration.
Service call activity (SCA).
Deployment of services with SCA via Service Virtualization Management (SVM), SVConfigurator, or Change Server will affect the selected agent.
Workaround: After deployment, you must select the agent manually from within the Designer.
Importing messages into SCA in the Data Model is not supported.
Workaround: Fill in SCA in the Data Model manually.
FIPS.
Problem: Encrypted Service Virtualization projects created before version 3.70 cannot be read by Service Virtualization libraries used by LoadRunner/Unified Functional Testing (UFT) integration versions earlier than 12.50.
This is due to encryption modifications in Service Virtualization 3.70 to enable use on machines with FIPS.
Workaround: To work with Service Virtualization 3.70 and LoadRunner/Unified Functional Testing (UFT) integration versions earlier than 12.50, change settings in the Designer configuration file VirtualServiceDesigner.exe.config.
In the following section of the file, set SV.Encryption.Version value to 1.
<!-- Allows to choose encryption version. Should be kept empty unless really needed.
Empty - use most recent version
1 - version used before SV 3.70; can be used for instance when project is used in integration scenario
by old versions of LR/UFT (before 12.50); does not work with FIPS!
2 - introduced in SV 3.70, works with FIPS
-->
<add key="SV.Encryption.Version" value="" />
Note:
Other limitations
Cannot disable real service when running on a queue on TIBCO EMS.
Observation: Real service is receiving requests even if virtual service is simulating.
Workaround: Stop real service before starting simulation.
Unable to simulate a service on a TIBCO EMS dynamic destination - limitation of EMS API.
Observation: Putting a service into Simulation mode generates an error, written to the server log: TIBCO.EMS.ADMIN.AdminSecurityException: Properties of dynamic destinations are not mutable.
Workaround: Create a destination in EMS for BusinessWorks(BW) service before such service is deployed to a BW Runtime Agent to avoid the creation of dynamic destinations.
Cannot start simulation of EMS service with admin login because of "Not allowed to change permissions of specified principal".
Observation: Putting service into Simulation mode generates an error, written to the server log: TIBCO.EMS.ADMIN.AdminSecurityException: Not allowed to change permissions of specified principal.
Workaround: Reconfigure the service to avoid using an admin EMS account.
MTOM service: Service Virtualization freezes after editing a data model.
Observation: Messages with huge attachments may cause the data model editor to freeze.
Workaround: No known workaround.
MS Office cannot be installed together with Microsoft Access Database Engine 2010 is installed.
Observation: Microsoft Access Database Engine 2010, necessary for data driving functionality, cannot be installed on the same computer as MS Office 64-bit.
Workaround: Install MS Office 32-bit.
Limited support for WebLogic JMS URL.
Observation: If JMS virtual service is configured and the WSDL of WebLogic JMS service is imported in Designer’s virtual service wizard, then WebLogic JMS URL is not parsed correctly and therefore the real destination name (real service endpoint) in the virtual service wizard is not pre-filled automatically.
Workaround: Manually fill in the real destination name in the virtual service wizard. Note that WebLogic uses specific JMS URI format, e.g.: jms://myHost:7001/transports/JMSTransport?URI=JMSTransportQueue (see http://download.oracle.com/docs/cd/E12839_01/web.1111/e13735/jmstransport.htm).
Cannot connect to Standalone server with username or password containing non-English characters.
Observation: User cannot connect to a secured standalone Service Virtualization Server with a user name or password containing non-English characters.
Workaround: Use unsecured standalone server.
Cannot virtualize service with Basic authentication and credentials containing non-English characters on HTTP(s) Gateway agent.
Observation: Virtualization of the service secured with HTTP Basic authentication fails on the HTTP(s) Gateway agent if client credentials contain non-English characters.
Workaround: Use the HTTP(s) Proxy agent to virtualize the service.
Connection to real service fails when using mutual HTTPS.
Observation: Client application does not send the client certificate to establish mutual HTTPS connection.
Solution: Make sure that the Trusted Root Certificate Authorities list on the machine where Service Virtualization is installed does not contain too many installed authorities (50-100). Clean unused or unnecessary authorities to keep the list small. Mutual HTTPS requires the list of trusted authorities to be sent to the client in packet of limited size. The client uses the list to select the correct client certificate. If there are too many authorities, the sent list will be truncated, and your required authority may be in the truncated part.
Limited message import of COBOL messages for all related protocols.
Observation: Import of COBOL message messages for all COBOL related protocols has the following limitations:
1. File content is previewed with invalid characters.
2. Default encoding/character set is used for processed content. The default value is IBM037 (IBM COM EUROPE EBCDIC).
Workaround:
1. No current workaround.
2. Modify the Designer/Server application configuration file (named HP.SV.StandaloneServer.exe.config or VirtualServiceDesigner.exe.config) and add/update the following lines, replacing the value with the desired encoding:
<configuration>
<appSettingsOverride>
…
<add key="ImsMessageProcessor.DefaultCodePage" value="IBM037" />
<add key="CobolMessageProcessor.DefaultCodePage" value="IBM037" />
…
</appSettingsOverride>
</configuration>
Cannot connect to IPv4 address via HTTP proxy agent.
Observation: Error message similar to "Bad Request - Invalid Hostname - HTTP Error 400. The request hostname is invalid" appears in browser when trying to connect to a service using an IPv4 address (something like 16.55.195.180).
Workaround: Either use the service’s host name instead of IPv4 or set the proxy server to HTTP proxy agent’s IPv4 address instead of the host name.
Error during simulation of Websphere JMS service: The value for 'JMS_IBM_Character_Set':'sim_default_JMS_IBM_Character_Set' is not valid.
Observation: During simulation of a Websphere JMS service, the client does not receive any response, and Service Virtualization generates an error such as: The value for 'JMS_IBM_Character_Set':'sim_default_JMS_IBM_Character_Set' is not valid.
Workaround: Open the data model editor for the relevant data model and expand the Default Rule. Either fill in the proper value for the JMS_IBM_Character_Set column in the response, or set as Not Present. Repeat for all necessary operations.
No response received from MQ service in simulation mode.
Observation: MQ Client receives a timeout or a long delayed response, and/or Service Virtualization generates an error such as “Unable to get destination 'hp.sv.dynamic.response.queue.1': MQ reason code is 2085, MQ error is MQRC_UNKNOWN_OBJECT_NAME. ---> IBM.WMQ.MQException: MQRC_UNKNOWN_OBJECT_NAME”. This may happen because the MQ Server and the Service Virtualization Server have different time and performance models and therefore records a long response time.
Workaround: All peers should have the proper time synchronization set. To fix a recorded time difference, either edit the performance model and update the response time value, or use the None performance model for simulation.
Wrong simulation of default rule of COBOL/MQ service.
Observation: Simulation COBOL over MQ service can fail in some cases. This can be caused by an added default value of MQIIH header from the Default rule.
Workaround: Edit the data model of the service. In the Default rule, set the MQIIH header to the value Not Present.
Fail to update schema for XLM service in case type is part of xml inheritance.
Observation: Manual modification of a complex XML schema type in a service description is not supported when the complex type is either created by type derivation (restriction or extension), or is a base type in a complex type derivation.
Workaround: Create a new service using a modified service description.
Uploading files to a Service Virtualization resource from the ALM client corrupts the project.
Observation: In the ALM Resources module, uploading files to a Service Virtualization resource corrupts the Service Virtualization project/service.
Workaround: Do not upload files to a Service Virtualization resource using the ALM client.
Designer crashes with OOM for WSDL with 260 operations.
Observation: WSDLs with more than 100 operations with large schemas (more than 200 leaves) are not supported.
Workaround: Split WSDL.
Designer randomly crashes after/during start.
Observation: Service Virtualization Designer randomly crashed during start or immediately after start, and the log contains an error message with fatal severity.
Workaround: Start Designer again.
Add support for error messages in IMS protocol.
Observation: IMS Connect protocol error messages are not supported.
Workaround: Not available.
Oracle service generates invalid values for the default rule.
Observation: Occurs when the service description is being learned and the type of the learned values is unknown (defaults to string values which cannot be translated to numeric values).
Workaround: In the Data Model Editor, edit values within the default rule so that they can be converted to a numeric value.
SVM: User cannot connect to the Service Virtualization Server when using credentials with non-ascii characters.
Observation: When a username or password contains non-ascii (national) characters, the user can log in to SVM (Service Virtualization Management) but credentials are not recognized by the Service Virtualization Server.
Workaround: Use a user account with credentials containing only ascii characters.
When enabling a disabled metadata, the new column has IsCondition instead of IgnoreCondition.
Observation: When enabling a disabled request metadata, the new column has the Is condition instead of the Ignore condition.
Workaround: Manually change the function on the metadata column to Ignore.
User has full permission (r,w,d,m) on a service but cannot see the service endpoint.
Observation: User has full permission (r,w,d,m) on a service but cannot see the service endpoint properly.
Workaround: Add the Read permission on the specific agent for the user.
SVM: Unable to download file from ALM from IE 8 and IE 9 browsers.
Observation: Downloading a project archive from ALM in IE 8 opens a new window and no dialog box for saving the file is opened. Downloading a project archive from ALM in IE 9 opens a new tab and no prompt for saving the file is shown.
Workaround:
IE 8: Apply the procedure from http://support.microsoft.com/kb/323308 and then restart the computer.
IE 9: Switch to the previous tab where file save prompt is displayed.
Unable to connect to ALM due to error Failed to initialize JVM: JNI_ENOMEM (-4).
Observation: User tries to connect to ALM. The error message “Failed to initialize JVM: JNI_ENOMEM (-4)” is displayed, indicating that JVM is unable to reserve the requested amount of memory.
Workaround 1: Open the “virtualservicedesigner.exe.config” file located in the “Designer\bin” folder. In appSettings section, find the key called "SV.JavaVm.PrealocatedMemorySize" and set the desired amount of memory. The recommended value is 256, as follows: “<add key="SV.JavaVm.PrealocatedMemorySize" value="256" />”. Restart the Designer and retry the connection to ALM.
Workaround 2: Open the “jvm-context” file located in the “Designer\bin\config” folder. Decrease the value of the first parameter in JavaOptions section. The initial and recommended value is “-Xmx128M” (128MB), so try to set it to “-Xmx64M”. Restart the Designer and retry the connection to ALM.
Note: You can combine both settings. In this case it is recommended that the “SV.JavaVM.PrealocatedMemorySize” value is set to double of the “–Xm” value.
JavaScript engine crashes in native code with 80000003 Exception Code.
Observation: Under a high load >10 parallel clients running against a virtual service with a scripted rule, the application may crash with the 80000003 Exception Code, mostly on a 32-bit system.
Workaround: Set maximum engine buffer size to less than 11 in the “scripted-rule-context.xml” file, located in the “Designer\bin\Config” or “Server\bin\Config”.
References are inlined in RPC/Enc communication.
Observation: When sending referenced elements in SOAP RPC/Encoded communication, referenced elements are inlined.
Workaround: None.
Unable to export statistics or list of services running on multiple servers.
Observation: When multiple services are selected, the menu items Export Statistics or Export List are disabled.
Workaround: Make sure you selected services from the same server. Filter out servers that you don’t need.
Batch simulation does not work with Performance Model hot swap
Observation: When performing a hot swap to a new Performance Model that has batch simulation configured, the batch simulation does not work.
Workaround: Restart simulation to use the newly selected Performance Model.
IBM WebSphere MQ Non-Intrusive protocol: Performance model simulation is not supported for a virtual service that is not using a data model.
Installer fails with the error "Error 997. Overlapped I/O operation is in progress."
Observation: The .msi installer may fail with the error message "Error 997. Overlapped I/O operation is in progress" when it is run from the command line with logging enabled and when requiring a flush of the log file after each line using the /l*vx! install.log option.
Workaround: Remove the exclamation mark from msiexec logging parameter (! - Flush each line to the log).
For example:
Correct:msiexec /i HPEServiceVirtualizationServer-x86.msi /l*vx install.log
Incorrect:msiexec /i HPEServiceVirtualizationServer-x86.msi /l*vx! install.log
Upgrade from 3.61 to 3.62: Backup may fail the first time if the Server is running.
Observation: This issue occurs when upgrading from 3.61 to 3.62 using the .msp installation file. During installation, after selecting the "Backup" option and clicking next, the Server is automatically stopped, but backup fails with an error that the Server is running. The backup process waits only a short time for the Server to stop before it continues, causing the backup to fail. The next attempt to run backup is successful.
Workaround: Run Backup again, or stop the Server manually in the Windows services management console before running Backup.
Simulation Preview does not work for C# scripted rules.
Observation: C# rules do not display a result in simulation preview unless the virtual service is in Simulation mode.
Workaround: Switch the virtual service to Simulation mode.
Service Virtualization might send a request to an invalid endpoint during Standby and Learning modes.
Observation: This occurs when the virtual service meets the following conditions:
Workaround: Use the same URI path for the real and virtual services, or use the HTTP Proxy agent.
When using the Apache ActiveMQ 5.12 generic JMS agent, an error occurs during validation of the agent configuration.
Observation: apache-activemq-5.12.0 includes the SLF4J logging library. Both Service Virtualization Java runtime and Apache ActiveMQ framework use SLF4J, causing the error.
Workaround: Remove the org.apache.commons.logging directory from activemq-all-5.12.0.jar.
The Resource Manager deployment tool fails to deploy a project to a remote Service Virtualization Server due to a delayed server response.
Observation: Deployment of a project to a Service Virtualization Server that is online using ResourceManager fails with the message – “Standalone server is not available”.
Workaround: Add the following lines to the application configuration file (ResourceManager.exe.config), and adjust the timeout value to meet your needs:
<appSettings>
<add key="SeV.Global.PingTimeout" value="10000" />
</appSettings>
Visit the HPE Software Support Online web site at: https://softwaresupport.hp.com
This web site provides contact information and details about the products, services, and support that HPE Software offers.
HPE Software online support provides customer self-solve capabilities. It provides a fast and efficient way to access interactive technical support tools needed to manage your business. As a valued support customer, you can benefit by using the support web site to:
Most of the support areas require that you register as an HPE Passport user and sign in. Many also require a support contract. To register for an HPE Passport ID, go to: https://softwaresupport.hp.com and click Register.
To find more information about access levels, go to: https://softwaresupport.hp.com/web/softwaresupport/access-levels.
Visit HPE Software Solutions Now at https://softwaresupport.hp.com/group/softwaresupport/search-result/-/facetsearch/document/KM01702710 to explore how the products in the HPE Software catalog work together, exchange information, and solve business needs.
Visit the Cross Portfolio Best Practices Library at https://hpln.hpe.com/group/best-practices-hpsw to access a wide variety of best practice documents and materials.
The only warranties for Hewlett Packard Enterprise Development LP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HPE shall not be liable for technical or editorial errors or omissions contained herein.
The information contained herein is subject to change without notice.
Confidential computer software. Valid license from HPE required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license.
© Copyright 2011-2015 Hewlett Packard Enterprise Development LP
Internet Explorer®, SQL Server®, Microsoft®, Windows®, Windows Server®, and Windows® 7 are U.S. registered trademarks of Microsoft Corporation.
Oracle, Java, and JDBC are registered trademarks of Oracle and/or its affiliates.
IBM®, WebSphere®, IMS™, and CICS® are trademarks or registered trademarks of International Business Machines Corporation, IBM, in the United States and in other countries.
TIBCO® is either the registered trademark or the trademark of TIBCO Software, Inc. and/or its subsidiaries in the United States and /or other countries.
Intel®, Core™2, and Xeon® are trademarks of Intel Corporation in the U.S. and/or other countries.
SAP® and SAP NetWeaver® are registered trademarks of SAP AG in Germany and in several other countries.