Doc:latest/evalguide/csa102 - Revision history

Prasad: /* How to Run csa102 and What to Observe */

2014-11-14T11:38:22Z

‎How to Run csa102 and What to Observe

Show changes

Prasad: /* How to Run csa102 and What to Observe */

2014-11-12T11:17:46Z

‎How to Run csa102 and What to Observe

Show changes

Prasad: /* How to Run csa102 and What to Observe */

2014-11-12T09:09:13Z

‎How to Run csa102 and What to Observe

Prasad: /* Code */

2014-11-12T09:08:33Z

‎Code

Prasad: /* Configuring the Service Group */

2014-11-12T08:34:43Z

‎Configuring the Service Group

Prasad: /* Creating the Sample Project */

2014-11-11T03:32:57Z

‎Creating the Sample Project

Natesh: /* How to create new Project Model csa102 */

2013-06-11T04:05:09Z

‎How to create new Project Model csa102

Stone: /* Launching the SAFplus Platform IDE */

2013-06-07T15:22:08Z

‎Launching the SAFplus Platform IDE

Stone: /* Launching the SAFplus Platform IDE */

2013-06-07T15:21:42Z

‎Launching the SAFplus Platform IDE

Vnpraveendesu: /* Code */

2013-06-07T13:51:07Z

‎Code

@@ Line 338: / Line 338: @@
 ===How to Run csa102 and What to Observe===
-As with the csa101 example we will use the SAFplus Platform Console to manipulate the administrative state of the csa102 service group.
+As with the csa102 example we will use the SAFplus Platform Console to manipulate the administrative state of the csa102 service group.
 <ol>

@@ Line 158: / Line 158: @@
 {| cellspacing="0" cellpadding = "0" border="0" align = "center" width="680"
-  ! style="color:black;background-color:#ffccaa;" align="center"| clCompAppMain.c
+  ! style="color:black;background-color:#ffccaa;" align="center"| main.c
   |-
   |<code><pre>
@@ Line 172: / Line 172: @@
 {| cellspacing="0" cellpadding = "0" border="0" align = "center" width="680"
-  ! style="color:black;background-color:#ffccaa;" align="center"| clCompAppMain.c
+  ! style="color:black;background-color:#ffccaa;" align="center"| main.c
   |-
   |<code><pre>
@@ Line 185: / Line 185: @@
-As with csa101, the <code>clCompAppAMFCSISet()</code> function is called to set the component's HA state, and the following block of code assigns this requested state to the component, while verbosely detailing this process:
+As with csa102, the <code>safAssignWork()</code> function is called to set the component's HA state, and the following block of code assigns this requested state to the component, while verbosely detailing this process:
 {| cellspacing="0" cellpadding = "0" border="0" align = "center" width="680"
-  ! style="color:black;background-color:#ffccaa;" align="center"| clCompAppMain.c
+  ! style="color:black;background-color:#ffccaa;" align="center"| main.c
   |-
   |<code><pre>
-void clCompAppAMFCSISet(SaInvocationT       invocation,
+void safAssignWork(SaInvocationT       invocation,
                          const SaNameT       *compName,
                          SaAmfHAStateT       haState,
@@ Line 203: / Line 203: @@
                compName->length, compName->value, mypid);
-     clCompAppAMFPrintCSI(csiDescriptor, haState);
+     printCSI(csiDescriptor, haState);
      /*
@@ Line 274: / Line 274: @@
 {| cellspacing="0" cellpadding = "0" border="0" align = "center" width="680"
-  ! style="color:black;background-color:#ffccaa;" align="center"| clCompAppMain.c
+  ! style="color:black;background-color:#ffccaa;" align="center"| main.c
   |-
   |<code><pre>
@@ Line 302: / Line 302: @@
 {| cellspacing="0" cellpadding = "0" border="0" align = "center" width="680"
-  ! style="color:black;background-color:#ffccaa;" align="center"| clCompAppMain.c
+  ! style="color:black;background-color:#ffccaa;" align="center"| main.c
   |-
   |<code><pre>

@@ Line 111: / Line 111: @@
 ====Configuring the Service Group====
-To make changes to the Service Group double-click on the box titled '''csa101SG'''. The '''Service Group Details''' dialog is displayed.
+To make changes to the Service Group double-click on the box titled '''csa102SG'''. The '''Service Group Details''' dialog is displayed.
 <span id='Service Group Details'></span>[[File:Tutorial_csa102_ServiceGroupDetails.png|frame|center| '''Service Group Details''' ]]

@@ Line 76: / Line 76: @@
 <br>This can be any existing directory but is usually the project area that was created in the previous section.
-<li>'''Python Location''': Enter the location where Python 2.5.0 is installed on your system. If Python 2.5.0 was installed by SAFplus Platform SDK, the directory is  <code>'''<installation_directory>/buildtools/local/bin'''</code>.
+<li>'''Python Location''': Enter the location where Python 2.5.0 or above is installed on your system. If Python 2.5.0 or above was installed by SAFplus Platform SDK, the directory is  <code>'''<installation_directory>/6.1/buildtools/local/bin'''</code>.
 </ul>

@@ Line 16: / Line 16: @@
 * Launch the '''SAFplus Platform IDE'''
 * Create the IDE project
-* Specify the Resource model (the types of physical hardware in our system)
+* Specify the Resource model for csa102(the types of physical hardware in our system)
 * Specify the Component model (the types of components or applications in our system)
 * Specify which Components run on which Resources

@@ Line 33: / Line 33: @@
 <ul>
-<li>Add the installation directory to the shells search path and then launch the IDE.</li>
+<li>Add the installation directory to the shells search path and then launch the IDE as follows:</li>
 <code><pre>
 # cl-ide

@@ Line 149: / Line 149: @@
 ===Code===
-The code can be found within the following directory
+The code can be geneteted using the same steps as mentioned for csa101. The genetated code can be found within the following directory
   <project-area_dir>/eval/src/app/csa102Comp