Skip Headers
Oracle® Communications Network Integrity CORBA Cartridge Guide
Release 7.1

E23712-01
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Feedback page
Contact Us

Go to previous page
Previous
PDF · Mobi · ePub

Oracle® Communications Network Integrity

CORBA Cartridge Guide

Release 7.1

E23712-01

January 2012

This guide explains the functionality and design of the Oracle Communications Network Integrity Cartridge for CORBA (CORBA cartridge).

This guide is intended for Network Integrity administrators, developers, and integrators.

This guide assumes that you are familiar with the following documents:

This guide assumes that you are familiar with:

Reviewing and Extending in Design Studio

You can download a ZIP file that contains the individual Design Studio files, and you can open these file in Design Studio to review and extend the cartridge.

See Network Integrity Developer's Guide for information about opening files in Design Studio. See Network Integrity Concepts for guidelines and best practices for extending cartridges.

About the CORBA Cartridge

The CORBA cartridge enables CORBA connectivity to Network Integrity, allowing it to use the CORBA protocol to communicate with external systems.

CORBA is a recognized, open (non-vendor specific), and commonly used industry communication standard between systems and devices. This cartridge enables Network Integrity customers to quickly and reliably build deployable cartridges that interact with one or many CORBA systems.

The CORBA cartridge is an abstract cartridge, meaning that Design Studio is used to configure and assemble the run-time cartridge against target systems or devices before it is deployed to the Network Integrity server. Other cartridges can be extended to reference the object request broker (ORB) and NameServer objects produced by the CORBA cartridge to perform discovery, import or discrepancy resolution actions.

Using the CORBA cartridge as a foundation, reusing its functions, and adopting best practices from Oracle, greatly reduce the cost and time to implement base CORBA functions. In addition, you have more time to focus on system specifics or addressing business issues. The included ORB and functions have been extensively tested and documented to deliver rapid value in discovery, import and resolution cartridges.

Cartridge Dependencies

This section provides information on dependencies that the CORBA cartridge has on other entities.

Run-time Dependencies

In order for the CORBA cartridge to work at run time, the AddressHandler cartridge must be installed.

See Design Studio online Help for information about installing the AddressHandler cartridge.

Design Studio Dependencies

To load the CORBA cartridge into Design Studio, the following cartridges must be installed:

  • AddressHandler cartridge

Opening the Cartridge Files in Design Studio

To review and extend the Oracle Communications Network Integrity CORBA cartridge, you must first download the Network Integrity CORBA cartridge media pack from the Oracle software delivery Web site:

https://edelivery.oracle.com

The media pack contains the Oracle Communications Network Integrity CORBA cartridge ZIP file, which has the following structure:

  • \Network_Integrity_Cartridge_Projects\Abstract_CORBA_Cartridge

  • \Network_Integrity_Cartridge_Projects\Address_Handlers

The project Abstract_CORBA_Cartridge contains the extensible Design Studio files.

See the Design Studio online Help and Network Integrity Developer's Guide for information about opening files in Design Studio. See Network Integrity Concepts for guidelines and best practices for extending cartridges.

Compiling and Deploying a Cartridge

To compile and deploy the CORBA cartridge, do the following:

  1. Import projects into Design Studio for Network Integrity.

  2. Clean and build the cartridge.

  3. Deploy the cartridge.

For information about deploying and undeploying, see Network Integrity Developer's Guide.

About the Cartridge Components

The CORBA cartridge is an abstract cartridge that is used by any cartridges that require CORBA connectivity.

This cartridge performs three actions:

Each action is made up of a "Property Initializer" processor (CorbaPropertyInitializer) and a "Connection Manager" processor (CorbaConnectionManager).

Figure 1 illustrates the processor workflow of the CORBA cartridge.

Figure 1 CORBA Cartridge Processor Workflow

the order the processors are run in

Property Initializer

The Property Initializer processor (CorbaPropertyInitializer) sets the properties needed to initialize CORBA connectivity, and writes them to the CorbaSeed (a JavaBean class). The following properties are set and written by the Property Initializer processor:

  • CorbaLoc URL: Obtained from the Request object and used by the "Connection Manager" processor to create the NameServer (NamingContextEXT) object.

  • ORB Command Line: Used to create the ORB, made up of command line arguments (string array), supplies the customization properties supplied by the user to initiating the ORB. The ORB command line is a single-space separated list.

  • (Optional) OrbProperties: Used to create the ORB. These are customized properties (Datatype: java.util.Properties).

  • (Optional) org.omg.CORBA.ORBClass: Used to create the ORB. This class is a Datatype: String.

  • (Optional) org.omg.CORBA.ORBSingletonClass: Used to create the ORB. This class is a Datatype: String.

  • Naming Service Connection Flag: A Boolean to indicate whether the processor should attempt to obtain the NameServer. Default is true. The output NameServer parameter is null if the flag is set to false.

Connection Manager

The Connection Manager processor (CorbaConnectionManager) takes the CorbaSeed produced by the Property Initializer processor and initiates it to establish a CORBA connection. It provides the ORB and NameServer object information to any extending cartridges.

This Connection Manager processor performs the following operations:

  1. Initiates the ORB using the command line arguments and properties contained in the CorbaSeed.

  2. Obtains the NameServer (namingContextExt) object from the CorbaLoc URL.

  3. Returns the ORB and NameServer if successful.

The NameServer can be obtained in two ways:

  • From the IORFile: The IORFile corresponding to the CORBA server is uploaded while creating the scan a configuration.

  • From the CorbaLoc URL: The n CorbaLoc URLs corresponding to n CORBA servers identified in the scope are added into the scope tab while creating a scan configuration.

CORBA URL Address Validation

All cartridges that extend the AbstractCorbaDiscovery action must provide valid CorbaLOC URL addresses. The CorbaURLAddressHandler address handler validates the addresses entered on the Scope Address page in Network Integrity. The address handler validates that the given address is a properly formatted IPv4 or IPv6 CorbaLoc URL.

To address the problem of bootstrapping and allow for more convenient exchange of human-readable object references, ORB::string_to_object allows URLs in the CorbaLoc formats to be converted into object references. If conversion fails, string_to_object raises a BAD_PARAM exception with one of following standard minor codes, as appropriate.

The CorbaLoc URL scheme provides stringified object references that are more easily manipulated by users than IOR URLs. Currently, CorbaLoc URLs denote objects that can be contacted only by transport protocols like IIOP or resolve_initial_references (RIR).

Examples of IIOP and RIR based CorbaLoc are as follows:

CorbaLoc::555xyz.com/Prod/TradingService
CorbaLoc:iiop:1.1@555xyz.com/Prod/TradingService
CorbaLoc::555xyz.com,:556xyz.com:80/Dev/NameService
CorbaLoc:rir:/TradingService
CorbaLoc:rir:/NameService
CorbaLoc:iiop:192.168.14.25:555/NameService
CorbaLoc::[1080::8:800:200C:417A]:88/DefaultEventChannel
 

Refer to CORBA Interoperability Specification for more information about IIOP and RIR formats.

Design Studio Construction

This section outlines the Design Studio construction for each of cartridge action and its associated processors:

CORBA Discovery Action

Table 1 Discover Abstract CORBA Action Design Studio Construction

Action Result Category Address Handler UI Params Model Processors

Discover Abstract CORBA

Device

CorbaURLAddressHandler

n/a

n/a

  • CORBA Property Initializer

  • CORBA Connection Manager


Table 2 Discover Abstract CORBA Action Processors Design Studio Construction

Processor Variable Notes

CORBA Property Initializer

Input: n/a

Output: CorbaSeed

CorbaSeed.java is a JavaBean class that contains the ORB properties and arguments.

CORBA Connection Manager

Input: CorbaSeed

Output: ORB, namingContextEXT

The ORB is a reference of the local ORB initialized. The namingContextExt is a reference of namingContextExt which is the initial naming context or naming server.


CORBA Import Action

Table 3 Import Abstract CORBA Action Design Studio Construction

Action Result Category Address Handler UI Params Model Processors

Import Abstract CORBA

Device

n/a

n/a

n/a

  • CORBA Property Initializer

  • CORBA Connection Manager


Table 4 Import Abstract CORBA Action Processors Design Studio Construction

Processor Variable Notes

CORBA Property Initializer

Input: n/a

Output: CorbaSeed

CorbaSeed.java is a JavaBean class that contains the ORB properties and arguments.

CORBA Connection Manager

Input: CorbaSeed

Output: ORB, namingContextEXT

The ORB is a reference of the local ORB initialized. The namingContextExt is a reference of namingContextExt which is the initial naming context or naming server.


CORBA Discrepancy Resolution Action

Table 5 Resolve Abstract CORBA Action Design Studio Construction

Action Result Category Address Handler UI Params Model Processors

Resolve Abstract CORBA

Device

n/a

n/a

n/a

  • CORBA Property Initializer

  • CORBA Connection Manager


Table 6 Resolve Abstract CORBA Action Processors Design Studio Construction

Processor Variable Notes

CORBA Property Initializer

Input: n/a

Output: CorbaSeed

CorbaSeed.java is a JavaBean class that contains the ORB properties and arguments.

CORBA Connection Manager

Input: CorbaSeed

Output: ORB, namingContextEXT

The ORB is a reference of the local ORB initialized. The namingContextExt is a reference of namingContextExt which is the initial naming context or naming server.


Design Studio Extension

This section gives examples of how to extend the CORBA cartridge. See Network Integrity Concepts for guidelines and best practices for extending cartridges

Creating a CORBA Discovery Action that Extends the CORBA Cartridge

This example explains how to create a discovery action which extends the Discover Abstract CORBA action, and models the collected data into the Oracle Communications Information Model using the CORBA interface.

This example assumes that the CORBA cartridge is loaded in Design Studio and is building without errors.

  1. Open Design Studio in the design perspective.

  2. Create a new cartridge project.

  3. Create a new discovery action.

  4. Add the Discover Abstract CORBA action to the new discovery action.

  5. Change to the Java perspective.

  6. Compile the IDL into Java and package it into a JAR file.

  7. Copy the JAR file to the lib directory of the new cartridge project.

  8. Right-click the cartridge project and select Properties.

    The Properties for <project_name> dialog box opens.

  9. Click Java Build Path.

  10. Click the Libraries tab.

  11. Add the new JAR file to the library.

  12. Add a new discovery processor to the discovery action. Make this processor responsible for calling the appropriate CORBA interfaces needed to collect the data.

  13. Make the new discovery processor use the ORB and Naming Service (NamingContextExt) objects that are output by the Connection Manager processor as its input.

  14. Design an implementation for the new discovery processor that runs one or more CORBA calls to retrieve the intended data.

  15. The cartridge project creates a cartridge (an IAR file) that can be deployed. A scan can be configured and executed using the produced cartridge.

Initializing a Custom ORB

To support an ORB that does not come with the JDK on Network Integrity, you must extend the CORBA cartridge. The steps below represent an example procedure that uses JacORB.

To initialize a custom ORB:

  1. Open Design Studio in the design perspective.

  2. Create a new cartridge project.

  3. Create a new discovery action.

  4. Extend the CORBA cartridge by doing the following (within the discovery action that you created in step 3):

    1. Create a new processor called JacORB Property Initializer.

    2. Insert the JacORB Property Initializer processor between Corba Property Initializer processor and Corba Connection Manager processor.

      This ensures that the output parameter from the preceding processor is used as input for the subsequent processor in the chain.

  5. Copy the JacORB JAR files to the lib directory of the new cartridge project and add them to the buildpath of that project.

    The Jac ORB Property Initializer processor sets the properties below to the corbaSeed JavaBean class.

    • org.omg.CORBA.ORBClass = org.jacorb.orb.ORB

    • org.omg.CORBA.ORBSingletonClass = org.jacorb.orb.ORBSingleton

Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Access to Oracle Support

Oracle customers have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.


Oracle Communications Network Integrity CORBA Cartridge Guide, Release 7.1

E23712-01

Copyright © 2011, 2012, Oracle and/or its affiliates. All rights reserved.

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:

U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle America, Inc., 500 Oracle Parkway, Redwood City, CA 94065.

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

This software or hardware and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.