EMS Integration Toolkit

1. Overview

The EMS Integration Toolkit is a collection of browser-based utilities designed for Telecom and Network OSS engineers. These tools help with common tasks encountered when integrating Element Management Systems (EMS) with Operations Support Systems (OSS).

2. Getting Started

Accessing the Toolkit

1. Open your web browser and navigate to https://emstools.web.app
2. Sign in with your Google account
3. Select the tool you need from the navigation tabs

System Requirements

• Modern web browser (Chrome, Firefox, Edge, Safari)
• JavaScript enabled
• Internet connection for initial load only

Navigation

The toolkit uses a tab-based navigation system. Click on any tab at the top of the screen to switch between tools. Your work in each tool is preserved while switching tabs.

3. TL1 Parser/Builder

What is TL1?

Transaction Language 1 (TL1) is a widely-used management protocol in telecommunications. It provides a standardized command structure for managing network elements.

TL1 Command Structure

COMMAND-CODE:TID:AID:CTAG::PARAMETER1=VALUE1,PARAMETER2=VALUE2;

Using the Parser

1. Select the "TL1 Parser/Builder" tab
2. Choose "Parse TL1" mode
3. Paste your TL1 command into the input field
4. Click "Parse Command"
5. View the parsed components in the results panel

Example Input

RTRV-ALM-ALL:NETWORKELEM1:SLOT-1-1:123::TYPE=CRITICAL,SRVEFF=SA;

Parsed Output

{
  "command": "RTRV-ALM-ALL",
  "tid": "NETWORKELEM1",
  "aid": "SLOT-1-1",
  "ctag": "123",
  "parameters": {
    "TYPE": "CRITICAL",
    "SRVEFF": "SA"
  }
}

Using the Builder

1. Select "Build TL1" mode
2. Fill in the command components (Command, TID, AID, CTAG)
3. Add parameters using the "Add Parameter" button
4. Click "Build Command"
5. Copy the generated TL1 command

4. Alarm Mapper

Purpose

The Alarm Mapper helps you create and manage mappings between EMS-specific alarm codes and standardized OSS alarm descriptions. This is essential for alarm correlation and unified monitoring.

Creating a Mapping

1. Select the "Alarm Mapper" tab
2. Enter the EMS alarm code (e.g., ALM_001)
3. Enter the OSS description (e.g., Link Down)
4. Select the severity level:
   • Critical - Service affecting, immediate action required
   • Major - Significant impact, urgent attention needed
   • Minor - Limited impact, scheduled attention
   • Warning - Potential issue, monitoring required
   • Info - Informational, no action needed
5. Click "Add Mapping"

Mapping Table

All mappings are displayed in a table format showing:

• EMS Code - The original alarm identifier
• OSS Description - Standardized alarm description
• Severity - Color-coded severity level
• Actions - Edit or delete mapping

Export/Import

Exporting Mappings

1. Click the "Export" button
2. Choose format: JSON or CSV
3. The file will download automatically

Importing Mappings

1. Click the "Import" button
2. Select a JSON or CSV file
3. Mappings will be added to your existing list

CSV Format

emsCode,ossDescription,severity
ALM_001,Link Down,critical
ALM_002,High CPU Usage,major
ALM_003,Config Changed,info

JSON Format

[
  {
    "emsCode": "ALM_001",
    "ossDescription": "Link Down",
    "severity": "critical"
  },
  {
    "emsCode": "ALM_002",
    "ossDescription": "High CPU Usage",
    "severity": "major"
  }
]

5. Payload Transformer

Supported Formats

How to Transform

1. Select the "Payload Transformer" tab
2. Choose the source format from the dropdown
3. Paste your data in the input area
4. Select the target format
5. Click "Transform"
6. Copy or download the result

Example: JSON to XML

Input (JSON):

{
  "alarm": {
    "id": "12345",
    "severity": "critical",
    "source": "router-01"
  }
}

Output (XML):

<?xml version="1.0" encoding="UTF-8"?>
<alarm>
  <id>12345</id>
  <severity>critical</severity>
  <source>router-01</source>
</alarm>

Working with CSV

When converting to/from CSV:

• The first row is treated as headers
• Arrays are converted to multiple rows
• Nested objects are flattened

6. SNMP OID Browser

Features

• OID Decoder - Decode numeric OIDs to human-readable names
• Walk Parser - Parse SNMP walk output into structured data
• MIB Browser - Browse common MIB trees

OID Decoder

1. Select "Decode OID" mode
2. Enter an OID (e.g., 1.3.6.1.2.1.1.1.0)
3. Click "Decode"
4. View the breakdown of each OID component

Example OID Breakdown

1.3.6.1.2.1.1.1.0 = sysDescr.0

Breakdown:
1      = iso
1.3    = org
1.3.6  = dod
1.3.6.1 = internet
1.3.6.1.2 = mgmt
1.3.6.1.2.1 = mib-2
1.3.6.1.2.1.1 = system
1.3.6.1.2.1.1.1 = sysDescr

Common OID Prefixes

SNMP Walk Parser

1. Select "Parse Walk" mode
2. Paste your SNMP walk output
3. Click "Parse"
4. View the structured table of OIDs and values

Example Walk Input

SNMPv2-MIB::sysDescr.0 = STRING: Cisco IOS Software
SNMPv2-MIB::sysObjectID.0 = OID: SNMPv2-SMI::enterprises.9.1.1
SNMPv2-MIB::sysUpTime.0 = Timeticks: (123456789) 14 days, 6:56:07.89
SNMPv2-MIB::sysContact.0 = STRING: admin@example.com
SNMPv2-MIB::sysName.0 = STRING: router-01
SNMPv2-MIB::sysLocation.0 = STRING: Data Center 1

MIB Browser

Browse the standard MIB tree to find OIDs. Click on any node to expand and see child objects.

7. NETCONF/XML Tools

Features

• XML Validator - Check XML syntax and well-formedness
• XPath Tester - Test XPath expressions against XML
• XML Formatter - Prettify or minify XML

XML Validator

1. Select "Validate XML" mode
2. Paste your XML content
3. Click "Validate"
4. View validation results and any errors with line numbers

XPath Tester

1. Select "XPath Tester" mode
2. Paste your XML in the document area
3. Enter an XPath expression (e.g., //interface/name)
4. Click "Test XPath"
5. View matching nodes

Common XPath Examples

NETCONF Example

<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="101">
  <get-config>
    <source>
      <running/>
    </source>
    <filter type="subtree">
      <interfaces xmlns="urn:ietf:params:xml:ns:yang:ietf-interfaces">
        <interface>
          <name/>
          <enabled/>
        </interface>
      </interfaces>
    </filter>
  </get-config>
</rpc>

8. E2E Integration Generator

Overview

The E2E Integration Solution Generator is a comprehensive wizard that guides you through designing complete integration solutions. It automatically generates architecture diagrams, code artifacts, and deployment configurations based on your requirements.

Four-Phase Approach

Phase 1: Requirements

Capture all integration requirements through six sub-sections:

1.1 Project Details

• Project Name - Unique identifier for your integration (required)
• Description - Brief description of the integration purpose
• Integration Type - ETL/Batch, Real-time Streaming, API Integration, or Hybrid
• Pattern - Point-to-Point, Hub-and-Spoke, Publish-Subscribe, or Event-Driven
• Tech Stack - Java/Spring Boot, Python, or Node.js

1.2 Source System

• System Type - Database, REST API, File System, Message Queue, FTP/SFTP
• System Name - Identifier for the source system (required)
• Data Format - JSON, XML, CSV, Avro, or Parquet
• Connection Details - Connection string or endpoint
• Schema Definition - Sample data or schema structure (required)

1.3 Destination System

Same configuration options as Source System for the target endpoint.

1.4 Data Mapping

• Source Field - Field name from source system
• Destination Field - Corresponding field in destination
• Transformation - Direct Copy, Concatenate, Split, Lookup, Format/Convert, or Custom Logic

At least one field mapping is required.

1.5 Business Rules (Optional)

• Rule Name - Descriptive name for the rule
• Action - Filter/Exclude, Transform, Route/Split, Aggregate, Enrich, or Validate
• Condition - Logic expression (e.g., WHERE status = 'ACTIVE')

1.6 Technical Requirements

• Error Handling - Retry with Backoff, Dead Letter Queue, Alert & Skip, or Fail Fast
• Logging Level - Debug, Info, Warning, or Error Only
• Scheduling - Real-time, Hourly Batch, Daily Batch, or Custom Cron
• Performance Target - Records per second
• Security - Data Encryption, Authentication, Data Masking, Audit Logging

Phase 2: Design

After clicking "Generate Design", the system creates:

Solution Flow Diagram

A Mermaid.js flowchart showing the data flow from source through transformation to destination, including error handling paths.

Architecture Diagram

A component diagram showing the integration architecture with all layers and connections.

Component Breakdown

Table listing all components with their purpose, technology, and status.

Dataflow Specification

Step-by-step specification of data transformations and validations.

Phase 3: Development Artifacts

Generated code artifacts based on your selected tech stack:

Core Integration Code

• Main application/service class
• Source connector implementation
• Destination connector implementation
• Data transformer with mapping logic
• Validator with business rules

Job Orchestration

• Apache Airflow DAG definition
• Kubernetes CronJob manifest
• Shell script scheduler

Database Scripts

• Staging tables DDL
• Error logging tables
• Audit trail tables

Infrastructure as Code

• Terraform modules
• Docker Compose configuration
• Kubernetes deployment manifests

Monitoring Configuration

• Prometheus metrics configuration
• Grafana dashboard JSON
• Alert rules

Phase 4: Execution Framework

Final deployment and testing artifacts:

Execution Scripts

• run.sh / run.bat - Main execution script
• setup.sh - Environment setup
• health-check.sh - Health verification

Test Suite

• Unit test templates
• Integration test templates
• Sample test data

Deployment Guide

Complete markdown documentation with prerequisites, step-by-step deployment instructions, and troubleshooting guide.

Export Options

• Download All - Complete project as ZIP file with folder structure
• Copy Code - Copy individual artifacts to clipboard
• Copy Diagrams - Copy Mermaid code for use in other tools

Validation & Error Handling

The generator includes built-in validation:

9. XML Parser

The XML Parser tab has two modes accessible via the toggle at the top: Parse & Flatten and Compare XML.

9.1 Parse & Flatten

Extracts every element, attribute, and text value from an XML document into a clean 4-column table. Each attribute of each element becomes its own row — no wide dynamic columns, all values stored as plain text.

Output Columns

How to Use

1. Click the XML Parser tab — it opens in Parse & Flatten mode by default
2. Paste XML into the textarea or click Upload XML to load a .xml / .txt file
3. Click Parse XML
4. Review the results — one row per attribute/text value, across all elements
5. Click Download CSV to save as xml_parsed_elements.csv, or Copy Table for tab-separated clipboard data (Excel-compatible)

Example Input

<ManagedObjects>
  <ManagedElement id="NE-WEST-01" type="OTN" vendor="Huawei">
    <Slot name="SLOT-1" adminState="IS">
      <Port id="P1" speed="100G"/>
    </Slot>
    <Alarm id="ALM-001" severity="MAJOR">Loss of Signal</Alarm>
  </ManagedElement>
</ManagedObjects>

Resulting CSV

Path,Element,Attribute,Value
ManagedObjects/ManagedElement,ManagedElement,id,NE-WEST-01
ManagedObjects/ManagedElement,ManagedElement,type,OTN
ManagedObjects/ManagedElement,ManagedElement,vendor,Huawei
ManagedObjects/ManagedElement/Slot,Slot,name,SLOT-1
ManagedObjects/ManagedElement/Slot,Slot,adminState,IS
ManagedObjects/ManagedElement/Slot/Port,Port,id,P1
ManagedObjects/ManagedElement/Slot/Port,Port,speed,100G
ManagedObjects/ManagedElement/Alarm,Alarm,id,ALM-001
ManagedObjects/ManagedElement/Alarm,Alarm,severity,MAJOR
ManagedObjects/ManagedElement/Alarm,Alarm,#text,Loss of Signal

9.2 Compare XML

Compares two XML files attribute-by-attribute and highlights what was added, removed, modified, or unchanged between them. Useful for detecting configuration drift, comparing EMS exports across maintenance windows, or validating changes before and after a network upgrade.

How to Use

1. Click the XML Parser tab then select Compare XML mode
2. Paste or upload the base XML into XML 1 — Base
3. Paste or upload the changed XML into XML 2 — Modified
4. Click Compare
5. Review the colour-coded summary bar and results table
6. Use the filter buttons to focus on specific change types
7. Click Download CSV to export the visible (filtered) results

Comparison Output Columns

Status Colour Coding

Filter Buttons

10. JSON Parser

Purpose

The JSON Parser flattens any nested JSON structure — objects and arrays — into a simple three-column table showing the full dot-notation path, value type, and value. This makes it easy to inspect deeply nested API responses, EMS inventory exports, or configuration payloads without writing code.

Output Columns

How to Use

1. Click the JSON Parser tab
2. Paste JSON into the textarea or click Upload JSON to load a .json / .txt file
3. Click Parse JSON
4. Review the flattened table — one row per leaf value
5. Click Download CSV to save as json_parsed_values.csv, or Copy Table for paste into Excel

Example Input

{
  "managedElements": [
    {
      "id": "NE-WEST-01",
      "type": "OTN",
      "slots": [
        { "name": "SLOT-1", "adminState": "IS" }
      ]
    }
  ]
}

Resulting CSV

Path,Type,Value
managedElements[0].id,string,NE-WEST-01
managedElements[0].type,string,OTN
managedElements[0].slots[0].name,string,SLOT-1
managedElements[0].slots[0].adminState,string,IS

Special Cases

11. Tips & Best Practices

General Tips

• Use keyboard shortcuts - Ctrl+V to paste, Ctrl+C to copy results
• Export regularly - Back up your alarm mappings to avoid data loss
• Validate first - Always validate XML/JSON before transformation
• Use formatting - Prettify data for easier reading and debugging

Troubleshooting

Browser Compatibility

For best experience, use the latest version of:

• Google Chrome (recommended)
• Mozilla Firefox
• Microsoft Edge
• Apple Safari