SOAP Web Services Traffic Health

All incoming SOAP web services traffic to your account using a data center-specific domain is listed in this section of the report.

Correcting Your SuiteTalk SOAP Web Services Integrations

The data listed in each column indicates where to find the SOAP web services integration. You should update the integration to use your account-specific domain or to use a dynamic service discovery method to obtain the URL.

Traffic Health reports identify URLs that use data center-specific domains in your account. You must change the data center-specific domains in the URLs to your account-specific domains. To make the necessary changes to a data center-specific URL:

• You may need the help of a developer in your company.

• You may need to ask your company’s IT department to locate the owner of the integration.

• You may need to contact a partner who set up an integration, or the third-party supplier of an integration.

See URLs for Account-Specific Domains for more information.

The following procedure assumes that you have already generated a report. If this is not the case, or if you want to refresh the report data, see Generating a Traffic Health Report.

To correct the items reported for SOAP Web Services:

1. Click SOAP Web Services.

   1. If you see the message No records to show, all of your SOAP web services integrations are using account-specific domains.

   2. If you see items listed in this section of the report, you must identify the non-compliant traffic, and determine the severity.

      Use the number in the Count column to determine the priority of the updates you should make. The higher the count, the higher the priority to make updates to use an account-specific domain or a dynamic discovery method.

      Note:

      Every line reported in the list may indicate a separate integration.

      Column Name	How This Information Can Help You Identify the Traffic
      Host	Domain name (Host header) associated with an incoming HTTP request.
      Source IP	Originating IP address of the request. Indicates the IP address that NetSuite sees as the IP address from which the traffic originates. This IP address may be translated by a NAT (Network Address Translation) device, which operates in the network where your integration server runs.
      User Agent	A user agent is software that acts on behalf of the user. Browsers are one type of user agent. The information in this column can identify the application type, operating system, software vendor, or software version of the requesting software user agent. For SOAP web services, the user agent indicates the name of your HTTP or integration client. The user agent may contain the name of the programming language used to create the integration client. For example, if MS Web Services Client Protocol is part of the user agent name, it indicates a .NET SOAP web services implementation. User agent names beginning with PHP-SOAP usually indicate PHP clients implemented with the NetSuite PHP Toolkit.
      URL Path	Same as the path that shown in the Host column, but the URL Path does not include the domain.
      Authentication Method	May give indications about the implementation. For example, if token-based authentication is listed in this column, it may mean that the integration was implemented fairly recently. Possible authentication methods are: Token-based Authentication (TBA) User Credentials (login operation and subsequent calls) User Credentials (Request Level Credentials) NetSuite Inbound SSO SuiteSignOn (Outbound SSO) No explicit authentication information provided.
      Identity	The email address can name the purpose of the integration, or indicate the use case. The email address could point to a partner or a third-party integration. For example, the email address may look similar the following: [e-mail] [e-mail] [e-mail] [e-mail]
      Response Code	HTTP status code. Failures of requests using a data center-specific URL with 200, 300, and 500 series response codes are listed in this report. 200 series response codes: The request was processed, but it does not mean the request routing (the domain used in the request) is correct. 300 series response codes: Indicate that the response was redirected. However, it also indicates that the request routing (the domain used in the request) should be fixed. Examples of some of the 300 series response codes include: 301 Moved Permanently 302 Found 308 Permanent Redirect 500 series response codes: The operation failed on the NetSuite side because the server could not process the response. You may need to fix the request routing (the domain used in the request). You should also investigate what else may be wrong with the request that caused the server to fail to process the request. For more information about HTTP status codes, refer to the following websites: Mozilla: HTTP response status codes Wikipedia: List of HTTP status codes
      Count	The number of times during the reporting period that the traffic with the same parameters used a data center-specific domain. Count can help you to determine the severity of the problem. Prioritize correcting line items with a high value in the Count column. A higher number indicates a larger volume of traffic is using a data center-specific URL.

2. Update SOAP web services integrations. To help you determine what to do, see the following:

   • If the integration will run in multiple NetSuite accounts, and you use a WSDL file as a source for the schema and NetSuite Port URL, you should always use a WSDL downloaded from https://webservices.netsuite.com/wsdl/v<version>/netsuite.wsdl, where <version> is the web services (WSDL) schema for the endpoint you are currently using. For more information, see NetSuite WSDL and XSD Structure. Also, you must use dynamic discovery methods to determine the correct URL. See Dynamic URL Discovery for SOAP Web Services for more information. See also getDataCenterUrls to retrieve the correct URL for each account you integrate with where you are running SOAP web services. For example:

     • If you are a partner developing SOAP web services integrations for more than one NetSuite customer, you must use dynamic discovery methods.

     • If you are a NetSuite customer and you intend to run the SOAP web services integration in your NetSuite production, sandbox, Release Preview, or other account type, you should use a dynamic discovery method to determine the correct URL.

   • If you do not use a WSDL file for discovering the schema and NetSuite Port URL, you should:

     • Use the URL https://webservices.netsuite.com/services/NetSuitePort_<version> for running the getDataCenterUrls discovery method to get the correct URL for your account.

     • If you cannot use a dynamic discovery method, use your account-specific URL in the format https://<accountID>.suitetalk.api.netsuite.com/services/NetSuitePort_<version>. Administrators and other users with the Set Up Company permission can go to Setup> Company > Company Information and click the Company URLs subtab to view the account-specific domains available for the account where they are currently logged in.

3. After you have updated all of the SOAP web services listed in the original report, generate a fresh report to validate there are no SOAP web services in your account that are using data center-specific domains.

4. Repeat this entire procedure as needed to continue correcting items listed on your Traffic Health report until no items remain in the list.

See the following for an example of items listed for SOAP web services after a report was generated:

Related Topics

Traffic Health

Traffic Health Reports

NetSuite UI Traffic Health

RESTlets Traffic Health

External Suitelets Traffic Health

External Forms Traffic Health

Commerce Traffic Health

Inbound Email Traffic Health

File Cabinet Traffic Health

Best Practices for Cloud Accounts

Understanding NetSuite URLs

URLs for Account-Specific Domains

Dynamic Discovery of URLs

Understanding NetSuite Account Types

Domains

Setting Available Without Login

General Notices