|
1 <?xml version="1.0" encoding="utf-8"?> |
|
2 <!-- Copyright (c) 2007-2010 Nokia Corporation and/or its subsidiary(-ies) All rights reserved. --> |
|
3 <!-- This component and the accompanying materials are made available under the terms of the License |
|
4 "Eclipse Public License v1.0" which accompanies this distribution, |
|
5 and is available at the URL "http://www.eclipse.org/legal/epl-v10.html". --> |
|
6 <!-- Initial Contributors: |
|
7 Nokia Corporation - initial contribution. |
|
8 Contributors: |
|
9 --> |
|
10 <!DOCTYPE concept |
|
11 PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd"> |
|
12 <concept id="GUID-FA12B3F7-4E84-5BBD-8598-9A974FFA7FCC" xml:lang="en"><title>What |
|
13 is Root Server Configurator?</title><prolog><metadata><keywords/></metadata></prolog><conbody> |
|
14 <p>Root Server Configurator is the starter program for the C32exe process. |
|
15 Root Server Configurator is started during device startup and then Root Server |
|
16 Configurator starts all the other servers used for device communication. </p> |
|
17 <p>Examples of these servers are the <xref href="GUID-61E0CD76-A2E3-5066-84A8-146EECA8ADCD.dita">Sockets |
|
18 Server</xref>, the <xref href="GUID-D49696D1-4B84-56B5-909D-A15F599F4B6D.dita">Telephony |
|
19 Server</xref> and the <xref href="GUID-9B83CDD4-FC94-51A0-AC67-CD04BCAFEF08.dita">Serial |
|
20 Communications Server</xref>. </p> |
|
21 <p>The Root Server Configurator is a separate process to the Root Server. </p> |
|
22 <p>To start the Root Server Configurator, a process must start either the <filepath>c32start.exe</filepath> program, |
|
23 or must call the <xref href="GUID-CFCBC5A6-FB1F-3DD7-B275-9B9C7389A8A7.dita"><apiname>StartC32()</apiname></xref> function. In the Techview reference |
|
24 version of Symbian platform, the steps in the startup up of the |
|
25 communications servers are: </p> |
|
26 <ol id="GUID-1036F8B2-A73F-524E-B6FA-A47D890F3089"> |
|
27 <li id="GUID-E1C66978-2D2E-5AF8-8087-5C8F33B359C1"><p> <xref href="GUID-788BD091-186A-5E25-B058-952C7629A8D4.dita">System |
|
28 Starter</xref> calls <filepath>c32start.exe</filepath> to start the Root Server |
|
29 Configurator. </p> </li> |
|
30 <li id="GUID-1C5C4BBB-D5BB-5576-81A1-5C632B6F2BC1"><p>The Root Server Configurator |
|
31 loads the <xref href="GUID-10A0DC8C-70B3-53D0-B63F-786C4BAB36CF.dita">CMI files</xref> </p> </li> |
|
32 <li id="GUID-9CFA086A-65C9-5F17-85E9-9CBFBE3B1D4D"><p>The Root Server Configurator |
|
33 calls <xref href="GUID-9DD1EA2B-DC59-315C-8E9C-CE6D9461B695.dita#GUID-9DD1EA2B-DC59-315C-8E9C-CE6D9461B695/GUID-DD214BA3-907E-3C7F-93C6-924A9A115A02"><apiname>RProcess::Create()</apiname></xref> to start the C32exe process. This |
|
34 starts the Root Server. </p> <p>The Root Server Configurator makes requests |
|
35 to Root Server for Root Server to load all the Comms Provider Modules. </p> </li> |
|
36 </ol> |
|
37 <p>After step 3, the device communications servers are all loaded and ready |
|
38 for use by applications. </p> |
|
39 <p>Figure 1 shows these three steps and how the Root Server and Root Server |
|
40 Configurator relate: </p> |
|
41 <fig id="GUID-09B31A56-73AF-5C89-87A7-E68A435FCDAD"> |
|
42 <title> Figure 1 - How Root Server and Root Server relate, and the |
|
43 steps involved during startup </title> |
|
44 <image href="GUID-4DB70D45-1E74-5357-9824-566962316E12_d0e115451_href.png" placement="inline"/> |
|
45 </fig> |
|
46 <p>Root Server Configurator is configured by two types of files: <xref href="GUID-10A0DC8C-70B3-53D0-B63F-786C4BAB36CF.dita">CMI |
|
47 files</xref>, and the <xref href="GUID-B5FC3F90-9669-5DED-A6E2-CB927273850B.dita">c32start.ini</xref> file. </p> |
|
48 <p>Root Server Configurator does not provide a published API to its server. |
|
49 Root Server Configurator is the only application which uses the Root Server |
|
50 API. </p> |
|
51 </conbody></concept> |