Not able to add Web reference in Asp.Net Web application

I need a solution

I am trying to add Symantec VIP soap services (https://services-auth.vip.symantec.com/mgmt/soap) as “Web Reference” in my Asp.net Web application to consume the same.

i have downloaded trail symantec certificate and installed in my system. while adding “Web referenece”, i am getting below error. and i have downloaded the wsdl files from symantec VIP manager and dont know where to add those files.

The document at the url https://services-auth.vip.symantec.com/ was not recognized as a known document type.
The error message from each known type may help you fix the problem:
– Report from ‘XML Schema’ is ‘Data at the root level is invalid. Line 1, position 1.’.
– Report from ‘DISCO Document’ is ‘Data at the root level is invalid. Line 1, position 1.’.
– Report from ‘WSDL Document’ is ‘There is an error in XML document (1, 1).’.
  – Data at the root level is invalid. Line 1, position 1.

please help me to add web reference and move further.

0

Related:

SEPM trigger remote scan with API

I need a solution

I am creating python code to trigger a remote scan on a computer using this API.

       https://apidocs.symantec.com/home/saep#_run_a_scan…

I am wondering if there is any way to do this without Advanced Threat Protection.  Something like setting the date on the computer as having an out of date scan so it triggers SEPM to start another scan on its own.

Also, the documentaion references the eoc.wsdl

       “The evidence of compromise command in XML. See eoc.xsd in the Remote Management and Monitoring documentation for the proper     format.”

I am having trouble finding this wsdl file.  Can anyone help me find it?  I have searched extensivly for Remote Management and Monitoring documentation but have not found the eoc.xsd.

0

1536249554

Related:

Re: Recovery Point for VM Failover through REST

Hi All,

Need a suggestion on Failing over VM through the REST API in RP4VM.Any leeds on it will be very helpful.

I came across the following :

1.The CLI might not be having all the functionalities

2.The API functionalities I came across in the Programming guide either does not cover all operations or might not be stated in the document.

3.We have the Swagger link , where we can test the Requests made : https://<ip>/deployer/swagger/#

4.There are two versions of the API i think : FAPI and deployer (however the FAPI contains methods like failover as i was searching online) and deployer contains more or less the same methods as in swagger. The Fapi documentation is old and for 4.0 , while deployer i could get for 5.1.

Question : How can we failover using the REST API ,present verion we are using is 5.1 , if you can mention the method and the wsdl/wadl , it would be great help.

Related:

Question Mark(?) is not Supported in NetScaler CLI

When running a command with question mark in the NetScaler CLI the question mark is removed.

Example command:

add lb monitor http-cmmvk-80 HTTP-ECV -send “GET /ConnectMVKWS_CancelBooking/mvkservice_CancelBooking?wsdl” -LRTM ENABLED -destPort 8080

If you copy and paste the above command in to a CLI session you will get the following result:

CLI1


If you run the same command via MAS or another automation tool the URL is set but it removes the “?” in the path.

However in MAS the report shows the right command with “?” but it is in fact set without it.

MAS Config Job report example:

MAS Report

NS GUI example after running the above job:

NSGUI
Notice that the “?” is missing from the config.

Adding the “?” via the GUI and the result from ns.log:

Mar 13 11:29:09 192.168.0.14 03/13/2018:10:29:09 GMT ns 0-PPE-0 : default GUI CMD_EXECUTED 739029 0 : User nsroot – Remote_ip 10.8.0.6 – Command “set lb monitor http-cmmvk-80 HTTP-ECV -send “GET /ConnectMVKWS_CancelBooking/mvkservice_CancelBooking?wsdl” -LRTM ENABLED -interval 5 SEC -resptimeout 2 SEC -resptimeoutThresh 0 -retries 3 -failureRetries 0 -alertRetries 0 -successRetries 1 -downTime 30 SEC -destPort 8080 -state ENABLED -reverse NO -transparent NO -ipTunnel NO -tos NO -secure NO -storefrontcheckbackendservices NO” – Status “Success”

The same issue can be seen in other CLI commands like this for AppFW:

bind appfw profile Test2 -denyURL “^[^?]*/winnt/”

The commands with ? are stored in ns.conf as expected.

Related:

7021311: How to Disable Web Service WSDL Metadata in Verastream Host Integrator

All deployed models and pools have web services for accessing table procedures and other features via SOAP/REST. By default, the WSDL metadata is discover-able with a web browser. To enhance security of your Verastream Host Integrator (VHI) web services, you may wish to disable the discover-ability of WSDL metadata, but leave the web services otherwise operational. This technical note describes how to make this server configuration change.

Note: To separately enable user authentication and authorization security features for accessing web services, see Technical Note 10151.

Related:

7021331: SoapUI 4.0 Error Loading Host Integrator HTTPS WSDL

This document (7021331) is provided subject to the disclaimer at the end of this document.

Environment

Verastream Host Integrator version 7.5 or higher

Situation

When using the third-party SoapUI application version 4.0.1 or earlier, and attempting to import a Verastream Host Integrator (VHI) SOAP web service WSDL using an HTTPS (secure TLS/SSL encrypted) URL, you may see a NullPointerException (NPE) error similar to the following:

Figure 1. soapUI error loading WSDL

Error loading WSDL

There was something wrong with the WSDL you are trying to import

Error loading [https://hostname:port/vhi-ws/model/modelname?wsdl]: java.lang.NullPointException

Resolution

Upgrade SoapUI to version 4.5.0 or higher, which is available for download at http://www.soapui.org.

Additional Information

Legacy KB ID

This article was originally published as Attachmate Technical Note 10135.

Disclaimer

This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented “AS IS” WITHOUT WARRANTY OF ANY KIND.

Related:

7021554: Errors in Microsoft Visual Studio When Using Verastream Host Integrator 7.x Web Service

The following errors or warnings may display when you add the Verastream Host Integrator (VHI) web service to your project, or subsequently attempt to build your project.

Warnings When Adding Service Reference

In your Microsoft Visual Studio 2008 or 2010 project using .NET Framework 3.0 or 3.5, after adding a service reference to the VHI web service WSDL, the Error List may display warnings similar to the following:

Custom tool warning: There was a validation error on a schema generated during export:

Source:

Line: 2 Column: 3

Validation Error: The global attribute 'http://www.w3.org/XML/1998/namespace: lang' has already been declared.



Custom tool warning: There was a validation error on a schema generated during export:

Source:

Line: 3 Column: 3

Validation Error: The global attribute 'http://www.w3.org/XML/1998/namespace: space' has already been declared.



Custom tool warning: There was a validation error on a schema generated during export:

Source:

Line: 11 Column: 3

Validation Error: The global attribute 'http://www.w3.org/XML/1998/namespace: base' has already been declared.



Custom tool warning: There was a validation error on a schema generated during export:

Source:

Line: 12 Column: 3

Validation Error: The global attribute 'http://www.w3.org/XML/1998/namespace: id' has already been declared.



Custom tool warning: There was a validation error on a schema generated during export:

Source:

Line: 13 Column: 3

Validation Error: The attributeGroup 'http://www.w3.org/XML/1998/namespace:specialAttrs' has already been declared.



Custom tool warning: The optional WSDL extension element 'UsingAddressing' from namespace 'http://www.w3.org/2006/05/addressing/wsdl' was not handled.

XPath: //wsdl:definitions[@targetNamespace='urn:xmlns:attachmate:vhi-ws:<model or session>:<model name>']/wsdl:binding[@name='<model name>PortBinding']

Errors When Building Project in Visual Studio 2010

In a BizTalk Server 2010 project, after importing a VHI web service as a Service Reference and attempting to build the solution, the Error List may display multiple errors similar to the following:

Node "<Schema>" - Schema reference "http://<hostname>:9680/vhi-ws/<model or session>/<model name>/<file>.xsd" is not a valid reference or does not exist in the current project.

Figure 1. Sample build errors in Microsoft Visual Studio 2010 Error List

Errors When Building Project in Visual Studio 2008

When attempting to compile your project in Visual Studio, the Error List and build output may display multiple errors similar to the following:

error CS0102: The type '<project name>.<service reference name>.<type name>' already contains a definition for '<name>'

error CS0111: Type '<project name>.<service reference name>.<type name>' already defines a member called '<name>' with the same parameter types

Figure 2. Sample build errors in Microsoft Visual Studio 2008 Error List

Error in BizTalk WCF Service Consuming Wizard

If you are attempting to add a Verastream Host Integrator 7.0 web service WSDL to a Microsoft BizTalk Server 2006 R2 or 2009 project using the WCF Adapter, the BizTalk WCF Service Consuming Wizard may display the following error:

Figure 3. 'Error consuming WCF service metadata. Object reference not set to an instance of an object.'

Figure 3. 'Error consuming WCF service metadata. Object reference not set to an instance of an object.'

Related:

7021550: Comparing Web Services in Verastream Host Integrator 6.x vs. 7.x

About Web Services

Web services provide a standard means of communication that enable data to be exchanged between applications over a network. The web services protocol (SOAP) consists of XML data transmitted over HTTP. Verastream Host Integrator provides web service support, which enables other applications (web service clients) to interact with host applications.

Each web service provides a Web Services Description Language (WSDL) document, which defines the operations offered and can be used by third-party tools to automatically generate client-side code.

What’s New in Version 7.x Web Services

The following table summarizes how web services functionality in version 7.1 and 7.0 compare with earlier versions.

Web Services Functionality
Version 7.1.1142 (7.1+SP1)
Versions 7.0 through 7.1.221
Earlier Versions
Component(s) providing web services
Session server (embedded SOAP stack; does not require or use Tomcat or IIS)
Projects created in Web Builder are deployed to Tomcat/Axis “VHI Web Server” (for Java) or Microsoft IIS (for .NET)
Enablement process
Automatic when model package is deployed
Manual build and deployment, which must be repeated when model is changed
Configuration
Administrative Console (See Configuring Version 7.1.1142 below)

Edit service-ctx.xml file (See Configuring Version 7.0 through 7.1.221 below)

Project properties in Web Builder
Stateful web services (multiple client calls using the same host session)
Automatically provided with WS-Addressing and WS-Resource if your SOAP client also supports these standards. (See Stateful Web Services in Version 7.x below.)

Requires manual modification of Web Builder-generated .asmx.cs file to use suspendSession and resumeSession methods, return a session key value on connect, and use this token as an input value for each model procedure method.
SSL (HTTPS) encryption security
Supported (See Encryption in Version 7.x below)

Not supported
Access control security
Credentials can be transmitted in SOAP headers or HTTP basic authentication. (See Authentication and Authorization in Version 7.x below.)

Credentials must be passed in the data payload as input values for the Connect method.
Procedures and model features
All procedures are automatically available. To enable Execute SQL Statement or the ProcessString event handler, enable options in Administrative Console > Server, Model, or Pool Properties > Web Services.
All procedures are automatically available. To enable Execute SQL Statement or the ProcessString event handler, uncomment appropriate lines in the service-ctx.xml file.
In version 6.5 or 6.6: Options are individually configured in Web Builder.

In versions 5.0 through 6.0: Procedures can be hidden by naming with

_HIDE suffix.

Default port numbers
9680 (standard non-secure)

9681 (secure)

8081 (Java)

80 (.NET)

WSDL document location URL
In addition to the URLs supported in version 7.0+:

List of WSDL documents available at
http://<session server>:9680.

Links to WSDL list in Administrative Console > Server Properties > Web Services.

Links to model (non-pooled) and pool WSDLs are available in Administrative Console > Model or Pool Properties > Web Services > Show WSDL.


List of WSDL documents for deployed models: http://<session server>:9680/vhi-ws

Connect to model (non-pooled):

http://<session server>:9680/vhi-ws/model/<model name>?wsdl

Connect to session pool:

http://<session server>:9680/vhi-ws/session/<pool name>?wsdl

See also Version 7.x Naming Tip below.

Java web service:

http://<host name>:8081/axis/services/<project name>?wsdl

.NET web service:

http://<host name>/<project name>/<project name>.asmx?wsdl

The session server, model, and connection method is specified in Project Properties.


WSDL target namespace
See Technical Note 10148
WSDL schema organization
Single embedded schema that uses the WSDL namespace, for compatibility with Verastream Process Designer and other BPEL technologies based on Apache ODE 1.3.x.
Java web services in version 6.6.189 and earlier have two embedded schemas in the WSDL with two different namespaces.
Web service client for testing
See Testing Web Services in Version 7.1

Version 7.1: See Testing Web Services in Version 7.1

Version 7.0: Use third-party tools, such as SoapUI, to import the WSDL and submit requests.



Test client automatically generated by Web Builder (runClient.bat for Java; web application for .NET)
Method timeout (how long the connector waits for response from session server)
See Technical Note 10044
Domains (multiple session servers in a VHI load distribution domain)
Edit the plugin-cfg.xml file (as described in Configuring Version 7.1.1142 below) to configure the domainName key (and serverName for a non-local management server, or management server cluster failover name as described in Technical Note 10103). Alternatively, you can specify DomainName and ServerName environment variables in your SOAP request, which takes precedence over the global configuration in the plugin-cfg.xml file.

Edit the service-ctx.xml file (as described in Configuring Version 7.0 through 7.1.221 below) to uncomment and configure the domainName property (and serverName for a non-local management server, or management server cluster failover name as described in Technical Note 10103). Alternatively, you can specify DomainName and ServerName environment variables in your SOAP request, which takes precedence over the global configuration in the service-ctx.xml file.

In Web Builder project properties, select the connect method “Connect to model via domain” or “Connect to session pool via domain.”
WS-I compliance
Yes
Yes (version 6.6); can also support older non-compliant Microsoft Data Set return type.

Additional Information

The following notes expand on references in the table above.

Version 7.x Naming Tip

Beginning in version 7.0, model names are automatically used in the WSDL URI and target namespace. For the widest compatibility with third-party web service clients, avoid spaces in model names and session pool names (use hyphens, underscores, or mixed case instead).

Testing Web Services in Version 7.1

Beginning in version 7.1, Web Services Explorer is a web service client you can use to test the automatic web services, thereby eliminating the need to use a third-party client such as SoapUI. Web Services Explorer web application functionality is provided by the Management Server component. To access Web Services Explorer, use any of the following methods:

  • Click the “Test” button displayed by Design Tool after successfully deploying a model
  • Click the “Test” link displayed in the list of WSDLs for deployed models at http://<session server>:9680/vhi-ws
  • In a web browser, open the following URL:
http://<management server>:8095/wsexplorer/wsexplorer.jsp?com.attachmate.eclipse.wst.ws.explorer=0&mode=standalone&wsdl=http://<session server>:9680/vhi-ws/model/<model name>?wsdl

For more information on using Web Services Explorer, see http://docs2.attachmate.com/verastream/vhi/7.1/en/topic/com.attachmate.vhi.help/html/reference/web_service_test.xhtml.

Note: Web Services Explorer does not support testing web services that are protected by WS-Security, Basic Authentication, or HTTPS encryption features. If you have these options enabled in the web services SOAP stack configuration, use a third-party client for testing.

Configuring Version 7.1.1142

Beginning in version 7.1.1142 (7.1 Service Pack 1), web services configuration can be accomplished in Administrative Console. (The service-ctx.xml file is no longer used for web services configuration as it was in versions 7.0 through 7.1.221.)

Some options not available in Administrative Console are configurable in other XML files located in the AttachmateVerastreamHostIntegratorsesssrvrserviceswsMETA-INF directory. Note: These XML files are created after web services are initially configured.

The following values are configurable in the service-cfg.xml file:

Description
Key
Original Default
HTTP web service port
hostPort
9680
HTTPS web service port
secureHostPort
9681
HTTP basic authentication for client user authorization without WS-Security
authnMetadata and authnService
false

The following values are configurable in the plugin-cfg.xml file:

Description
Key
Original Default
Session server load distribution domain
domainName
(null)
Non-local management server for load distribution domain
serverName
localhost

Note: After saving changes to these files, you must restart the session server service to for changes to take effect. For information on manually restarting the service, see Technical Note 10004.

Configuring Version 7.0 through 7.1.221

To configure version 7.x web services, edit the service-ctx.xml file located in the following directory:

Windows:C:Program FilesAttachmateVerastreamHostIntegratorsesssrvrserviceswsMETA-INF

UNIX:hostintegrator/lib/container/services/ws/META-INF

For example: To configure different port numbers, change value for the hostPort or secureHostPort properties.

After saving changes to this file, you must restart the session server service to for changes to take effect. For information on manually restarting the service, see Technical Note 10004.

Note: When you upgrade to a later version (hotfix or major release) in the future, the service-ctx.xml file may revert to new defaults. It is recommended that you make a backup copy of your edited service-ctx.xml file. After upgrading in the future, use the backup copy as a guide for editing the installed service-ctx.xml file.

Encryption in Version 7.x

Regarding SSL encryption security in version 7.x:

  • To add a CA-signed certificate for SSL, place it in the server keystore using the Java JSSE keytool. If no certificate exists in the HostIntegratorsesssrvretc directory, a self-signed certificate is generated for non-production purposes.
  • To disable the non-secure HTTP port:

Version 7.1.1142: Uncheck “Enable HTTP Web Services” in Administrative Console > Perspective > Host Integrator > Session Servers > Installation > Servers > your server name > Properties > Web Services.

Versions 7.0 through 7.1.221: Edit the service-ctx.xml file to change the httpEnabled property to false.

Note: Verastream Process Designer R3 does not support connections to encrypted web services.

Authentication and Authorization in Version 7.x

Regarding client authentication security in version 7.x, see Connection C in Technical Note 10151.

Stateful Web Services in Version 7.x

Regarding stateful web services in version 7.x:

Disabling WS-Resource in Version 7.1

For compatibility with some technologies, WS-Resource (Web Services Resource 1.2 Framework) can be disabled in the embedded web service configuration. To disable this feature, see Technical Note 10130.

Upgrading to Version 7.x

If you have an existing Java or .NET web service project in Web Builder, you can continue to re-build and re-deploy it after upgrading to version 7.x.

By default, Web Builder no longer supports creating new web service projects. If you need to enable the deprecated web service project types for new Web Builder projects, please contact Support at http://support.attachmate.com/contact/.

If your web service project is based on a user-defined project type (rather than an installed standard project type), see also Technical Note 10120.

If your existing web service project (created in version 6.6.188 or earlier) does not display in Web Builder version 7.0.961, complete the following steps:

  1. In Web Builder version 7.0.961, right-click the project and click Explore. This will open the project folder, such as C:Program FilesVerastreamHostIntegratorprojects<project name>.
  2. In a text editor, open the project.properties file.
  3. Add the following line:
targetnamespace=myvalue

where myvalue is any non-blank string, such as the project name or urn:xmlns:attachmate:vhi-wb-ws:<project name> (the default value for new web service projects in version 6.6.189 or higher).

  1. Close and re-open the Web Builder application.

Related: