[Notes] Demo

kashu

　　Exercise 1
　　
　　Integration Repository

• Namespaces have already been created for each user under the software component RKT CaseStudy.
  
• Create a new object of type External Definition of category ‘xsd’ called Flights and import the Flights.xsd file.
  

　　
　　
　　
　　

• Create a new message interface called FlightsIn - Category ‘Inbound’ – ‘Asynchronous’ and refer to the external definition created in the earlier step.
  

　　
　　
　　
　　

• Create a new data type called BookingOrders with the following data structure
  

　　
　　
　　
　　
　　
　　

• Create a new Message Type BookingOrders referring to the data type created in the earlier step (step 4)
  

　　
　　
　　
　　
　　
　　

• Create a new outbound Message Interface BookingOrdersOut referring to the message type created in the earlier step (step 5)
  

　　
　　
　　
　　
　　

• Create a new object of type Message Mapping called BookingOrdersToFlights_Req use the mapping as defined below
  

　　
　　
　　
　　
　　
　　
　　
　　Define the user-defined function copyToLine as shown below.
　　
　　
　　
　　
　　
　　
　　
　　Complete the mapping by assigning source field to target field as explained by instructor.
　　
　　
　　
　　

• Create a new Interface Mapping called BookingOrdersToFlights relating the two message interfaces ‘BookingOrdersOut’ and ‘FlightsIn’
  

　　
　　
　　
　　
　　
　　
　　
　　
　　
　　
　　
　　
　　
　　
　　

• Create a new Context Object called AirlineCode of type XSD string. Assign the same to the element AirlineID in the message interface BookingOrdersOut
  

　　
　　
　　
　　
　　
　　

• Create a new business scenario called FlightBooking with two application components called ‘TravelAgency’ and ‘ReservationSystem’ referring to the Product Version ‘XI RKT Workshop 3.0’.
  

　　
　　
　　
　　
　　
　　
　　
　　
　　
　　Add application component ReservationSystem in the similar way.
　　
　　

• Create two Actions called BookingOrders_Out referring to the message interface ‘BookingOrdersOut’ and Flights_In referring to the message interface ‘FlightsIn’ created earlier
  

　　
　　
　　
　　
　　
　　
　　
　　
　　
　　
　　
　　Add the action Flights_in in the similar way.
　　
　　

• Include these actions into the respective application components and connect them as an asynchronous communication. Refer to the mapping program that was created in the earlier step.
  

　　
　　
　　
　　
　　
　　
　　
　　
　　
　　
　　
　　
　　
　　
　　
　　
　　
　　
　　
　　Integration Directory
　　
　　1)      Create a new Business Scenario FlightBooking## . Expand your node which contains the business scenario.
　　
　　
　　
　　2)      Select the ‘Objects’ tab and select your Business System ‘Travel AgencyCS’ and ‘ReservationSystemCS’ right click and ‘Add to scenario’ FlightBooking##
　　
　　
　　
　　
　　
　　
　　
　　
　　
　　
　　
　　
　　
　　
　　
　　
　　
　　
　　
　　
　　
　　3)      Go to your Business Scenario in edit mode – choose the icon ‘Business Scenario Configurator’ – assign the the two business services to the roles – configure connections – and Generate the same (not in simulation mode) (Use the standard changelist and not the option to create a new changelist)
　　
　　
　　
　　
　　
　　
　　
　　4)      Create a new Communication Channel called FileOut## under the business service ReservationSystem. This should refer to the adapter type ‘XI’(because you are sending your message to the J2SE adapter engine), Message Protocol – XI 3.0, for the target system give the IP address of the system where you installed the file adapter i.e. your local IP address, and the port number from the adapter configuration screen as well as the name of the service from the adapter configuration
　　
　　
　　
　　
　　
　　5)      In the generated receiver determination specify add this channel as the Receiver Agreement. Right click and choose the option ‘New specific’ and add the created communication channel.
　　
　　
　　
　　
　　
　　6)      In the receiver determination specify your conditions – using the context object created in the repository earlier. (ex. AirlineCode = AA)
　　
　　
　　
　　
　　
　　
　　7)      Save and activate all your change. Finally, check and make sure you have the following configuration as shown in the screens below:
　　
　　
　　
　　
　　
　　
　　
　　
　　
　　
　　Executing the scenario
　　
　　1)      Open the file Client_httpAdaptor.html
　　2)      Specify the sever host name of the integration server
　　3)      Specify the HTTP port of the integration server - /nsmicm
　　4)      Specify the sender service name as ‘TravelAgencyCS’
　　5)      Specify the sender interface name as ‘BookingOrdersOut’
　　6)      Specify the Sender Namespace
　　7)      Delete the Optional Parameters
　　8)      Upload file ‘BookingOrders.xml’ after having made sure that it contains the right namespace.
　　9)      Click on the ‘Send’ button