Client is vodafone spain. main machine-----> 10.40.51.

19 This is an integration project and here tibco is used to integrate multiple appl ications. In this project there two type of Calls one is for consultation and another one is for provision. The Business process supported by Tibco can be divided in the following categori es: 1. Processes for consultation: When one application needs some information from another application, the requester application uses this type of processes to get the required information. 2. Provisioning processes: These processes are used to provision the produc t e.g. activating a new mobile connection. 3. Use processes: There are the reusable processes such as SMS, Error and E mail which can be invoked by any process. and coming to the architecture, here we have 5 typed of components are used, suc h as SAc,SDc,BPI,SD,SA. 1). SAc (Service Application channel): The SAc service integrates the channel ad apters with Tibco Processes and also does the transformations between native dat a model to Particular Model. The SAc service is created as Publish or r equest/reply adapter service. 2). SDc (Service Domain Channel): These services will receive the data from SAc and perform validation, mapping and/or transformations between Particular Model (PM) to Common Data model (CDM). 3). BPI (Business Process Integration): BPI defines the Business Processes which we need to create for implementing business functionality. BPI can invoke one o r more then one domain service. 4). SD (Service Domain): SD is the service which exposes a specific business fun ctionality of the end application. SD service performs the Mapping / transformin g the data from CDM to PM. They are also used to implement the reusable processes e.g. Error management, email, SMS etc. SD can also be implemented as a composite service, which invokes multiple SA. 5). SA (Service Application): SA interacts with final systems and also transform s data from PM to native data format. Service application is created as subscrib er or request/response adapter service. It is an actually Old flow that maintains the all data in clarify application Now they are introducing new system such as SPIRIT(Seibel CRM/PRM). For this we doesn't use SAc Adapter to get interation with SPIRIT. We use the web service an d provide the concrete WSDL SPIRIT team to get request by SDc component. then PI gets data as 1. Clarify 10.1(CRM post-paid) -----customer relation Management(CRM). for Service activation/deactivation in postpaid. 2. Clarify 11.5(CRM pre-paid) also known as NCRM------- for Service activat ion/deactivation 3. HLR (Activate the services in Telecom network) 4. SERPA (Activate the services in Telecom network) --IVR 5. CUR (Provide the list of services owned by customer) CQ--------Clear Quest 6. Catalog (Product catalog for the pre-paid) NTR------- Network Trouble request. 7. Arbor(Billing - Post-paid) TFR------- Test Fault Report. 8. Infranet (Billing - Pre-paid) 9. IRIS

10. 11.

NPPI Recargas------ for recharges

Tocreate buffer touch <buffername> vi <buffername> fieldName <tabSpace> value . .