Abstract: An approach that provides routing a SIP message to a proxy server of a called party in a communication network is provided. In one embodiment, there is a routing tool that assists in routing a session initiation protocol (SIP) message to a called party. The routing tool, including a receiving component, receives a SIP message of a user making a call in the network. The routing tool further includes a parsing component configured to parse the message to determine the domain of the called party and performs a table lookup using the domain of the called party in order to: retrieve a destination code; embed the destination code into the message; and route the message based on the destination code.

Abstract: A method and system for specifying a data occurrence in a service-oriented architecture based environment. After a service specification phase of a service, a service interface is received and a service implementation is created. During a service realization phase, a data element of the service is determined to be sourced or not sourced by the service implementation. If the data element is sourced, then the data element is determined to be optional. If the data element is not sourced, then the data element is determined to be mandatory. The data occurrence including an indication of whether the data element is optional or mandatory is displayed. The service specification phase is repeated and the service interface is modified based on the displayed data occurrence.

Abstract: A system and associated method for automatically generating a service specification of a Service Oriented Architecture (SOA) solution. A process model framework and a data model framework are received as inputs. Processes in the process model framework perform services of various complexity levels. Processes are decomposed into a respective set of atomic service processes in the lowest complexity level and data objects are extracted from the decomposed atomic service processes. The data objects are associated with data elements of the data model framework. The data model framework is extended and flexibility patterns are added for reusability of the service specification. The service specification of the SOA solution is generated as process interfaces represented with the data objects according to inputs from a user customizing aspects of the service specification, for either a desired service of the SOA solution or a desired process in the process model framework.

Abstract: An approach is presented for specifying categories of data elements during a service specification phase of a service-oriented architecture (SOA) life cycle defined in a service modeling methodology like Service-Oriented Modeling and Architecture (SOMA). A Unified Modeling Language based SOA modeling tool for the service modeling methodology includes a middleware based integration plug-in that categorizes service-specific data elements as transaction elements, glue elements, core Common Information Model (CIM) elements, and elements extending the CIM elements, and associates the categorized data elements with corresponding operations of the service being modeled.

Abstract: A method and system for specifying categories of data elements during a service specification phase of a service-oriented architecture (SOA) life cycle defined in a service modeling methodology like Service-Oriented Modeling and Architecture (SOMA). A Unified Modeling Language based SOA modeling tool for SOMA methodology includes a middleware based integration plug-in that categorizes retrieved service-specific data elements as transaction elements, optional controller elements, glue elements, optional extension patterns, extension elements and core Common Information Model entities, and associates the categorized data elements with corresponding operations of the service being modeled. A user interface provided by the plug-in enables input of the data elements into the categories and input of the associations between the categorized data elements and corresponding operations of the service being modeled.

Abstract: An approach that provides routing a SIP message to a proxy server of a called party in a communication network is provided. In one embodiment, there is a routing tool that assists in routing a session initiation protocol (SIP) message to a called party. The routing tool, including a receiving component, receives a SIP message of a user making a call in the network. The routing tool further includes a parsing component configured to parse the message to determine the domain of the called party and performs a table lookup using the domain of the called party in order to: retrieve a destination code; embed the destination code into the message; and route the message based on the destination code.

Abstract: A method and system for specifying categories of data elements during a service specification phase of a service-oriented architecture (SOA) life cycle defined in a service modeling methodology like Service-Oriented Modeling and Architecture (SOMA). A Unified Modeling Language based SOA modeling tool for SOMA methodology includes a middleware based integration plug-in that categorizes retrieved service-specific data elements as transaction elements, optional controller elements, glue elements, optional extension patterns, extension elements and core Common Information Model entities, and associates the categorized data elements with corresponding operations of the service being modeled. A user interface provided by the plug-in enables input of the data elements into the categories and input of the associations between the categorized data elements and corresponding operations of the service being modeled.

Abstract: A system and associated method for automatically generating a service specification of a Service Oriented Architecture (SOA) solution. A process model framework and a data model framework are received as inputs. Processes in the process model framework perform services of various complexity levels. Processes are decomposed into a respective set of atomic service processes in the lowest complexity level and data objects are extracted from the decomposed atomic service processes. The data objects are associated with data elements of the data model framework. The data model framework is extended and flexibility patterns are added for reusability of the service specification. The service specification of the SOA solution is generated as process interfaces represented with the data objects according to inputs from a user customizing aspects of the service specification, for either a desired service of the SOA solution or a desired process in the process model framework.