Step 5 - Pulling some information from the Server
 | The aim of this step is to:
|
 | After completing this step you will be able to:
|
 | For this, you will use the following tools:
|
If you select a Movie in the list of current moviews, an SMS is sent to the Server. This Mobile Originated (MO) SMS contains the ID of the Movie. You may see this from the Mobile Simulator, sending the SMS:
And also from the Server Simulator, receiving the SMS.
The Server should send back the information about this Movie, i.e. a short description and the show times for today. For this, let’s create an Agent. 
We will label our Agent ‘IOD_Movie_2’.
We then define that our Agent will return some Text through SMS:
Here is the text we want to send:
| A war re-erupts on Earth between two robotic clans. 14:00 - 17:45 - 22:00 |
And the server will send this information when the message data of the SMS it receives contains ‘getShowtime*2’:
Do not forget to activate this Agent:
Now, if we select our movie 'Transformers' again, the server receives the SMS and sends back the information to the Mobile Simulator.
In the Mobile Simulator, we see that a new SMS has been received.
If we double click the icon, we may see the content of this SMS.
Using an Agent, we may send Text Messages, Data Messages, Raw Data or even a more complex Scenario. Let's have a look at the 'Add Cinema' feature of our first menu. If you click the 'Add Cinema' menu entry, the Applet will ask you a city name.
The Applet will then send an SMS to the Server. The content of this SMS is "getCinema*CityName".
We will now create an Agent labeled "Add_Cinema_Beijing".
But, this time, we will use a scenario and we will trigger the Card Interpreter instead of the Applet. Here is the script that will update a record in the EF ADN.
| /* This 3G script updates a record of in the Abbreviated Dialing Numbers EF file * GSM interpreter TAR: B0 00 10 * UICC interpreter TAR: B0 00 00 * USIM interpreter TAR: B0 00 01 * Card Manager TAR: 00 00 00 * * Test with GSM interpreter */ public class UpdateADN_3G { public void script() { short MF = (short)0x3F00; // MF (3F00) short TELECOM = (short)0x7F10; // DF TELECOM (7F10) short ADN = (short)0x6F3A; // EF ADN (6F3A) selectById(MF); // Select MF selectById(TELECOM); // Select DF TELECOM selectById(ADN); // Select EF ADN // Create a stream ByteStream s = new ByteStream(); // Set the new ADN Record into the stream (28 bytes) s.write("0x4265696A696E67FFFFFFFFFFFFFF" + "089100680146731393FFFFFFFFFF"); // Update the third record of the EF ADN updateRecord((byte)0x03,(byte)0x04,s.toByteArray()); } } |
Our scenario will target the 2G Interpreter, which TAR is B0 00 10.
And this Agent will be triggered only when it receives an SMS containing "getCinema*Beijing":
If we try again to add Beijing's Zyrcon Cinema, we see on Server side that the SMS is received and answered.
Now, we have three Zyrcon Cinemas defined in our EF ADN!
If we select the Beijing Zyrcon Cinema, the Applet automatically Setups a Call and a new Mobile Simulator is opened for you to either pick up the call or reject it.
Our Zyrcon Cinema Wireless Solution is working fine in our Simulated Environment.
With the full version, you may now proceed with the deployment of your Applets and Libraries on a Real Card.
For this, you will need a proper License that you may buy on the Gemalto Web Store in the 'Kits & Software' section.