Migrate the Verizon eBonding Integration to a Production System

  • Release version: Zurich
  • Updated July 31, 2025
  • 2 minutes to read
    • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of Migrate the Verizon eBonding Integration to a Production System

    This guide details the essential steps for ServiceNow customers to migrate the Verizon eBonding integration from a development or test environment to a production environment. The migration requires coordination with Verizon’s implementation manager and careful configuration to ensure seamless communication between ServiceNow and Verizon’s production systems.

    Show full answer Show less

    General Preparation

    • Obtain the production SOAP password from Verizon, using the same Verizon SOAP user ID as in the test environment.
    • Create an integration user in the ServiceNow production instance with the same username and password as the development instance to maintain authentication consistency.

    Migration Steps

    1. Request the Verizon eBonding plugin for the production instance. Activating the plugin adds a “VZ eBonding” category field, which triggers integration functions. To minimize user impact, consider disabling this category from the list during activation.
    2. Set up the Verizon certificate and keystore by copying them from the development instance or regenerating separate versions for production and development.
    3. Configure integration properties such as user ID and password provided by Verizon for the production system.
    4. Update all Verizon eBroker SOAP Message functions to point to Verizon’s production SOAP endpoint (commonly https://pubwebsvc.vzbi.com:443/TroubleManagementv3r0). Unlock each SOAP Message function record and update the endpoint URL accordingly.
    5. Apply any customizations captured in an update set from the development environment to the production environment.
    6. Provide Verizon with the ServiceNow production SOAP endpoint URL (e.g., https://yourproductioninstance.service-now.com/ETMSPublish.do?WSDL) for integration setup on their side.
    7. Coordinate a production turn-up with Verizon to perform basic testing and validate the integration.

    Important Considerations

    • Do not create test tickets in the production system without prior approval from Verizon, as these tickets will be treated as real incidents.
    • Ensure all configurations and credentials are correctly applied to avoid disruptions in ticket exchange and integration workflows.

    This topic outlines the tasks required for moving the Verizon eBonding integration from a Dev/Test environment to a Production environment.

    This process requires coordination with your assigned Verizon implementation manager.

    General Tasks

    The following work can be performed any time:
    • Obtain a production SOAP password from Verizon. Your Verizon SOAP user ID is the same as that used against the Verizon test broker.
    • Create an integration user for Verizon in the ServiceNow Production instance. Use the same user name and password that was created for the development instance, so that the communication between Verizon and ServiceNow is properly authenticated.

    Migrating to a Production Environment

    Perform these tasks in order.
    • Task 1: Request the Verizon eBonding plugin for the production instance. When the plugin is installed, the only immediate user interface change is an additional Category field named VZ eBonding. All of the triggers for the integration are dependent on the category being set to VZ eBonding. Enabling the plugin on the production instance should not affect your users. If you wish to take additional precautions, disable the VZ eBonding category from the list when the plugin is activated for the instance.
    • Task 2: Set up the Verizon certificate and keystore. Copy these directly over from the Dev instance or regenerate them so that you have separate versions for the Dev and Production instances.
    • Task 3: Configure the integration properties to work with the Production Verizon eBonding system. This is userID, password, and other properties provided by your Verizon representative.
    • Task 4: Change all the Verizon eBroker SOAP Message functions to use Verizon's production SOAP Endpoint. In most cases, the endpoint URL will be: https://pubwebsvc.vzbi.com:443/Trouble_Management_v3r0. Verify this URL with the Verizon implementation specialist.
      • In the SOAP Message Functions related list, click each function, clear the Lock check box, and enter the production endpoint.
      • Configure the SOAP Message Functions related list and add the SOAP endpoint column. In the SOAP Message Functions list view, unlock and update the endpoint for all records by Edit multiple records in a list using the list editor.
    • Task 5: Apply any customizations. If customizations to the integration on the Dev system were captured in an update set, apply that update set to the Production system.
    • Task 6: Provide Verizon with the production SOAP Endpoint. The SOAP endpoint should look something like this: https://yourproductioninstance.service-now.com/ETMSPublish.do?WSDL.
    • Task 7: Coordinate a Production turn up with your Verizon representative to do basic testing.
      Warning:
      Do not create test tickets against the production system without working with the Verizon team. Any tickets created are treated as real tickets.