Doc:latest/evalguide/csa104 - Revision history

Bot: 9 revisions

2011-10-24T19:02:03Z

9 revisions

Pradeepac: /* How to Run 104 and what to observe */

2010-08-30T08:36:18Z

‎How to Run 104 and what to observe

Pradeepac: /* How to Run 104 and what to observe */

2010-08-29T03:54:23Z

‎How to Run 104 and what to observe

Pradeepac: /* How to Run 104 and what to observe */

2010-08-28T14:42:55Z

‎How to Run 104 and what to observe

Pradeepac: /* How to Run 104 and what to observe */

2010-08-28T14:39:32Z

‎How to Run 104 and what to observe

Pradeepac: /* How to Run 104 and what to observe */

2010-08-28T14:35:09Z

‎How to Run 104 and what to observe

Pradeepac: /* How to Run 104 and what to observe */

2010-08-28T14:33:04Z

‎How to Run 104 and what to observe

Pradeepac: /* How to Run 104 and what to observe */

2010-08-28T13:04:20Z

‎How to Run 104 and what to observe

Pradeepac: /* How to Run 104 and what to observe */

2010-08-28T13:00:50Z

‎How to Run 104 and what to observe

Senthilk at 03:27, 27 August 2010

2010-08-27T03:27:51Z

New page

==csa104 Provisioning==

===Objective===

The objective is to demonstrate some of the features of the Clovis Object Registry (COR) and Clovis' Object Management (OM) framework.

===What you will learn===

*How to use the Clovis Object Registry to set configuration values in a simple SAFplus Platform application.
*How to manipulate COR values from the SAFplus Platform Console line interface.

===Code===

The code can be found within the following directory
<project-area_dir>/eval/src/app/csa104Comp

{| cellspacing="0" cellpadding = "0" border="0" align = "center" width="680"
! style="color:black;background-color:#ffccaa;" align="center"| clCompAppMain.c
|-
|<code><pre>
ClUint8T clEoClientLibs[] =
{
COMP_EO_CLIENTLIB_COR, /* Lib: Common Object Repository */
COMP_EO_CLIENTLIB_CM, /* Lib: Chassis Management */
COMP_EO_CLIENTLIB_NAME, /* Lib: Name Service */
COMP_EO_CLIENTLIB_LOG, /* Lib: Log Service */
COMP_EO_CLIENTLIB_TRACE, /* Lib: Trace Service */
COMP_EO_CLIENTLIB_DIAG, /* Lib: Diagnostics */
COMP_EO_CLIENTLIB_TXN, /* Lib: Transaction Management */
CL_FALSE, /* NA */
COMP_EO_CLIENTLIB_PROV, /* Lib: Provisioning Management */
COMP_EO_CLIENTLIB_ALARM, /* Lib: Alarm Management */
COMP_EO_CLIENTLIB_DEBUG, /* Lib: Debug Service */
COMP_EO_CLIENTLIB_GMS /* Lib: Cluster/Group Membership Service */
};
</pre></code>
|}

Here we present the Client Libraries. These are set within <code>clCompCfg.h</code>.

{| cellspacing="0" cellpadding = "0" border="0" align = "center" width="680"
! style="color:black;background-color:#ffccaa;" align="center"| clCompCfg.h
|-
|<code><pre>
#define COMP_EO_CLIENTLIB_COR CL_TRUE
#define COMP_EO_CLIENTLIB_CM CL_FALSE
#define COMP_EO_CLIENTLIB_NAME CL_FALSE
#define COMP_EO_CLIENTLIB_LOG CL_FALSE
#define COMP_EO_CLIENTLIB_TRACE CL_FALSE
#define COMP_EO_CLIENTLIB_DIAG CL_FALSE
#define COMP_EO_CLIENTLIB_TXN CL_TRUE
#define COMP_EO_CLIENTLIB_NA CL_FALSE
#define COMP_EO_CLIENTLIB_PROV CL_TRUE
#define COMP_EO_CLIENTLIB_ALARM CL_FALSE
#define COMP_EO_CLIENTLIB_DEBUG CL_FALSE
#define COMP_EO_CLIENTLIB_GMS CL_FALSE
</pre></code>
|}

Within <code>clCompCfg.h</code> we set Clovis Object Registry (COR), the Transaction (TXN), and Provisioning (Prov) libraries to <code>TRUE</code>.

{| cellspacing="0" cellpadding = "0" border="0" align = "center" width="680"
! style="color:black;background-color:#ffccaa;" align="center"| clCompAppMain.c
|-
|<code><pre>
ClCompAppInitialize()

...
clCorMoIdInitialize(&moId);
clCorMoIdAppend(&moId, CLASS_CHASSIS_MO, 0);
clCorMoIdAppend(&moId, CLASS_CSA104RES_MO, 0);
clCorMoIdServiceSet(&moId, CL_COR_SVC_ID_PROVISIONING_MANAGEMENT);
rc = clCorObjectHandleGet(&moId, &objH);
if (CL_OK != rc)
{
clprintf(CL_LOG_SEV_ERROR,"%s: Failed [0x%x] to get the object handle. ",
appname, rc);
return rc;
}

while (!exiting)
{
if (running && ha_state == CL_AMS_HA_STATE_ACTIVE)
{
clprintf(CL_LOG_SEV_INFO,"%s: Hello World! (count = %d)", appname, counter);
#ifdef CL_INST
if ((rc = clDataTapSend(counter)) != CL_OK && (rc != CL_ERR_INVALID_PARAMETER))
{
clprintf(CL_LOG_SEV_ERROR,"%s: Failed [0x%x] to send data tap data",
appname, rc);
}
#endif
if ((rc = update_counter_in_cor(time(0), objH, counter)) != CL_OK)
{
clprintf(CL_LOG_SEV_ERROR,"%s: [0x%x]: cor update failed. Exiting.",
appname, rc);
break;
}

/* Checkpoint new counter number */
rc = checkpoint_write_counter(counter);
if (rc != CL_OK)
{
clprintf(CL_LOG_SEV_ERROR,"%s: [0x%x]: Checkpoint write failed. Exiting.",
appname, rc);
break;
}

counter++;
}

usleep((useconds_t)delta_t*1000);
}
</pre></code>
|}

The main loop body is as we've seen several times already. But, the sleep, rather than being <code>sleep(1)</code> is a <code>usleep()</code> of a variable duration. The duration: <code>delta_t</code> is a number in milliseconds that is settable from COR. We'll see where it gets set later.

{| cellspacing="0" cellpadding = "0" border="0" align = "center" width="680"
! style="color:black;background-color:#ffccaa;" align="center"| clCompAppMain.c
|-
|<code><pre>
#include <stdio.h>
#include <string.h>
...
#include <clDebugApi.h>
...
</pre></code>
|}

We including standard header files, including <code>clDebugApi.h</code> which allows the application to interact with the SAFplus Platform Console.

{| cellspacing="0" cellpadding = "0" border="0" align = "center" width="680"
! style="color:black;background-color:#ffccaa;" align="center"|clcsa104CompOAMPConfig.c
|-
|<code><pre>
#include <clcsa104CompOAMPConfig.h>
</pre></code>
|}
Within <code>clcsa104CompOAMPConfig.c</code> we include <code>clcsa104CompOAMPConfig.h</code>.

{| cellspacing="0" cellpadding = "0" border="0" align = "center" width="680"
! style="color:black;background-color:#ffccaa;" align="center"|clcsa104CompOAMPConfig.h
|-
|<code><pre>
#include <clOmApi.h>
#include <clCorApi.h>
#include <clProvOmApi.h>
#include <clProvApi.h>
#include <clAlarmOM.h>
#include <clHalApi.h>
#include <clHalObjectApi.h>

typedef ClRcT (*fp) (CL_OM_PROV_CLASS*, ClHandleT, ClProvTxnDataT*);

CL_OM_BEGIN_CLASS(CL_OM_PROV_CLASS, CL_OM_PROV_CSA104RES_CLASS)

CL_OM_END

ClRcT clcsa104CompCSA104RESProvConstructor( void *pThis, void *pUsrData,
ClUint32T usrDataLen );
ClRcT clcsa104CompCSA104RESProvDestructor ( void *pThis , void *pUsrData,
ClUint32T usrDataLen );
ClRcT clcsa104CompCSA104RESProvValidate(CL_OM_PROV_CLASS* pThis,
ClHandleT txnHandle, ClProvTxnDataT* pProvTxnData);

ClRcT clcsa104CompCSA104RESProvUpdate(CL_OM_PROV_CLASS* pThis,
ClHandleT txnHandle, ClProvTxnDataT* pProvTxnData);

ClRcT clcsa104CompCSA104RESProvRollback(CL_OM_PROV_CLASS* pThis,
ClHandleT txnHandle, ClProvTxnDataT* pProvTxnData);

ClRcT clcsa104CompCSA104RESProvRead(CL_OM_PROV_CLASS* pThis,
ClHandleT txnHandle, ClProvTxnDataT* pProvTxnData);

void clcsa104CompCSA104RESProvObjectStart(ClCorMOIdPtrT pMoId,
ClHandleT txnHandle);

void clcsa104CompCSA104RESProvObjectEnd(ClCorMOIdPtrT pMoId,
ClHandleT txnHandle);
</pre></code>
|}

Next in <code>clcsa104CompOAMPConfig.h</code> we have several header files being included. Included is <code>clOmApi.h</code> which is the main header file for using the Object Management subsystem. This is Clovis' support for object-oriented like programming in C. Next <code>clCorApi.h</code> is the main header for using the Clovis Object Registry. <code>clProvOmApi.h</code> is the main header for the Clovis Provisioning OM class. We define an Object Management class: <code>CL_OM_PROV_CSA104RES_CLASS</code> which inherits from another Object Management class: <code>CL_OM_PROV_CLASS</code>. This last class is the class whose API was imported with the <code>#include clProvOmApi.h</code>. The subsequent code in the above table declare functions that will be member functions of the new Object Management class: <code>CL_OM_PROV_CSA104_CLASS</code>. Note that function header comments have been omitted for clarity.

{| cellspacing="0" cellpadding = "0" border="0" align = "center" width="680"
! style="color:black;background-color:#ffccaa;" align="center"| clcsa104Compcsa104Res.c
|-
|<code><pre>
extern ClUint32T delta_t;
extern ClCharT appname[80];
</pre></code>
|}

Above we define/declare a variable that is used for provisioning. The extern is a reference to a variable defined in clCompAppMain.c.

{| cellspacing="0" cellpadding = "0" border="0" align = "center" width="680"
! style="color:black;background-color:#ffccaa;" align="center"| clcsa104CompOAMPConfig.c
|-
|<code><pre>
ClOmClassControlBlockT pAppOmClassTbl[] =
{
{
CSA104COMP_CSA104RES_PROV_CLASS_NAME,
sizeof(CL_OM_PROV_CSA104RES_CLASS),
CL_OM_PROV_CLASS_TYPE,
clcsa104CompCSA104RESProvConstructor,
clcsa104CompCSA104RESProvDestructor,
NULL,
CSA104COMP_CSA104RES_PROV_CLASS_VERSION,
0,
CL_MAX_OBJ,
0,
CSA104COMP_CSA104RES_PROV_MAX_SLOTS,
CL_OM_PROV_CSA104RES_CLASS_TYPE
},

};
</pre></code>
|}

Within <code>clcsa104CompOAMPConfig.c</code> we define the global <code>pAppOmClassTbl</code> so that will know about the new class and be able to instantiate members of the class. Line 27 specifies the name of the class. This is optional. Defined is the size of instances of the class, next we specify the base class, followed by the constructor and destructor for the class respectively. The <code>NULL</code> specifies the table of functions for the class, in this case there is no such table. <code>0</code> is the instance table pointer. The next three lines of code.
<br>--> <code>CL_MAX_OBJ,</code>
<br>--> <code>0,</code>
<br>--> <code>CSA104COMP_CSA104RES_PROV_MAX_SLOTS,</code>
<br>specify the max number of object instances allowed, current number of object instances, and max number of object instances so far respectively. Followed by the Class Type ID for the class.

{| cellspacing="0" cellpadding = "0" border="0" align = "center" width="680"
! style="color:black;background-color:#ffccaa;" align="center"| clcsa104Compcsa104Res.c
|-
|<code><pre>
ClRcT clcsa104CompCSA104RESProvConstructor( void *pThis, void *pUsrData,
ClUint32T usrDataLen )
{
ClRcT rc = CL_OK;

/* Override "semantic check" virtual method in provClass*/
((CL_OM_PROV_CLASS*)pThis)->clProvObjectStart = clcsa104CompCSA104RESProvObjectStart;
((CL_OM_PROV_CLASS*)pThis)->clProvValidate = (fp)clcsa104CompCSA104RESProvValidate;
((CL_OM_PROV_CLASS*)pThis)->clProvUpdate = (fp)clcsa104CompCSA104RESProvUpdate;
((CL_OM_PROV_CLASS*)pThis)->clProvRollback = (fp)clcsa104CompCSA104RESProvRollback;
((CL_OM_PROV_CLASS*)pThis)->clProvRead = (fp)clcsa104CompCSA104RESProvRead;
((CL_OM_PROV_CLASS*)pThis)->clProvObjectEnd = clcsa104CompCSA104RESProvObjectEnd;

...

return rc;
}

ClRcT clcsa104CompCSA104RESProvDestructor ( void *pThis , void *pUsrData,
ClUint32T usrDataLen )
{
ClRcT rc = CL_OK;

...

return rc;
}
</pre></code>
|}

The above table presents the Contructor. It initializes the function pointers defined in the Base Class. These are the Update method, the provisioning validation method, and the provisioning rollback method. These are declared in <code>clcsa104CompOAMPConfig.h</code> in the class definition. The destructor doesn't do anything except return <code>CL_OK</code>. There's no destruction work to do for this class.

{| cellspacing="0" cellpadding = "0" border="0" align = "center" width="680"
! style="color:black;background-color:#ffccaa;" align="center"| clcsa104Compcsa104Res.c
|-
|<code><pre>
ClRcT clcsa104CompCSA104RESProvUpdate(CL_OM_PROV_CLASS* pThis,
ClHandleT txnHandle, ClProvTxnDataT* pProvTxnData)
{
ClRcT rc = CL_OK;

/*
---BEGIN_APPLICATION_CODE---
*/

clprintf(CL_LOG_SEV_INFO, "Inside the function %s", __FUNCTION__);

ClNameT moIdName = {0};

rc = clCorMoIdToMoIdNameGet((ClCorMOIdPtrT)pProvTxnData->pMoId, &moIdName);
if (CL_OK != rc)
{
clprintf(CL_LOG_SEV_ERROR,"%s: Failed while getting the MOId Name from moid. rc[0x%x] ", appname, rc);
return rc;
}
/*
---END_APPLICATION_CODE---
*/

</pre></code>
|}

{| cellspacing="0" cellpadding = "0" border="0" align = "center" width="680"
! style="color:black;background-color:#ffccaa;" align="center"| clcsa104Compcsa104Res.c
|-
|<code><pre>
switch (pProvTxnData->provCmd)
{
case CL_COR_OP_CREATE :
case CL_COR_OP_CREATE_AND_SET:

/*
* ---BEGIN_APPLICATION_CODE---
*/

clprintf(CL_LOG_SEV_INFO,"%s: Inside create request for the object [%s] ", appname, moIdName.value);

/*
* ---END_APPLICATION_CODE---
*/

break;
case CL_COR_OP_SET:

/*
* ---BEGIN_APPLICATION_CODE---
*/

if ( pProvTxnData->attrId == CSA104RES_DELTA_T)
{
delta_t = *(ClUint32T *)pProvTxnData->pProvData;
clprintf(CL_LOG_SEV_INFO,"%s: The delta time is now [%d] ", appname, delta_t);
}

/*
* ---END_APPLICATION_CODE---
*/

break;

case CL_COR_OP_DELETE:

/*
* ---BEGIN_APPLICATION_CODE---
*/

/*
* ---END_APPLICATION_CODE---
*/

break;
default:
clprintf (CL_LOG_SEV_ERROR, "Prov command is not proper");
}

...

return rc;
}
</pre></code>
|}

When the COR object associated with csa104's provisioning is updated, <code>clcsa104CompCSA104RESProvUpdate</code> function is called. A new value is set for the <code>delta_t</code> variable that is used to control the sleep interval in the application's main loop.

===How to Run 104 and what to observe===

<ol>
<li>Start the application as usual with the SAFplus Platform Console.
<code><pre>
# cd /root/asp/bin
# ./asp_console

cli[Test]-> setc 1
cli[Test:SCNodeI0]-> setc cpm
cli[Test:SCNodeI0:CPM]-> amsLockAssignment sg csa104SGI0
</pre></code>

Again, there are two log files to observe <code>/root/asp/var/log/csa104CompI0Log.latest</code> and <code>/var/log/csa104CompI1Log.latest</code>. After running the above commands you should see the following output in these logs when using <code>tail -f</code>.

{| cellspacing="0" cellpadding = "0" border="0" align = "center" width="680"
! style="color:black;background-color:#ffffaa;" align="center"| /root/asp/var/log/csa104CompI0Log.latest
|-
|<code><pre>
Mon Jul 14 19:06:29 2008 (SCNodeI0.21202 : csa104CompEO.---.---.00051 : INFO)
Component [csa104CompI0] : PID [21202]. Initializing
Mon Jul 14 19:06:29 2008 (SCNodeI0.21202 : csa104CompEO.---.---.00052 : INFO)
IOC Address : 0x1
Mon Jul 14 19:06:29 2008 (SCNodeI0.21202 : csa104CompEO.---.---.00053 : INFO)
IOC Port : 0x80
Mon Jul 14 19:06:29 2008 (SCNodeI0.21202 : csa104CompEO.---.---.00054 : INFO)
csa104: instantiated as component instance csa104CompI0.
Mon Jul 14 19:06:29 2008 (SCNodeI0.21202 : csa104CompEO.---.---.00055 : INFO)
csa104CompI0: cpmHandle = 0x1
Mon Jul 14 19:06:29 2008 (SCNodeI0.21202 : csa104CompEO.---.---.00056 : INFO)
csa104CompI0: Waiting for CSI assignment...
Mon Jul 14 19:06:29 2008 (SCNodeI0.21202 : csa104CompEO.---.---.00057 : INFO)
csa104CompI0: checkpoint_initialize
Mon Jul 14 19:06:29 2008 (SCNodeI0.21202 : csa104CompEO.---.---.00064 : INFO)
csa104CompI0: Checkpoint service initialized (handle=0x1)
Mon Jul 14 19:06:29 2008 (SCNodeI0.21202 : csa104CompEO.---.---.00066 : INFO)
csa104CompI0: Checkpoint opened (handle=0x2)
Mon Jul 14 19:06:29 2008 (SCNodeI0.21202 : csa104CompEO.---.---.00067 : INFO)
csa104CompI0: Section created
</pre></code>
|}

{| cellspacing="0" cellpadding = "0" border="0" align = "center" width="680"
! style="color:black;background-color:#ffffaa;" align="center"| /root/asp/var/log/csa104CompI1Log.latest
|-
|<code><pre>
Mon Jul 14 19:06:29 2008 (SCNodeI0.21209 : csa104CompEO.---.---.00049 : INFO)
Component [csa104CompI1] : PID [21209]. Initializing
Mon Jul 14 19:06:29 2008 (SCNodeI0.21209 : csa104CompEO.---.---.00050 : INFO)
IOC Address : 0x1
Mon Jul 14 19:06:29 2008 (SCNodeI0.21209 : csa104CompEO.---.---.00051 : INFO)
IOC Port : 0x81
Mon Jul 14 19:06:29 2008 (SCNodeI0.21209 : csa104CompEO.---.---.00052 : INFO)
csa104: instantiated as component instance csa104CompI1.
Mon Jul 14 19:06:29 2008 (SCNodeI0.21209 : csa104CompEO.---.---.00053 : INFO)
csa104CompI1: cpmHandle = 0x1
Mon Jul 14 19:06:29 2008 (SCNodeI0.21209 : csa104CompEO.---.---.00054 : INFO)
csa104CompI1: Waiting for CSI assignment...
Mon Jul 14 19:06:29 2008 (SCNodeI0.21209 : csa104CompEO.---.---.00055 : INFO)
csa104CompI1: checkpoint_initialize
Mon Jul 14 19:06:29 2008 (SCNodeI0.21209 : csa104CompEO.---.---.00062 : INFO)
csa104CompI1: Checkpoint service initialized (handle=0x1)
Mon Jul 14 19:06:29 2008 (SCNodeI0.21209 : csa104CompEO.---.---.00064 : INFO)
csa104CompI1: Checkpoint opened (handle=0x2)
</pre></code>
|}

<li>As before, unlock the application with:
<code><pre>
cli[Test:SCNodeI0:CPM]-> amsUnlock sg csa104SGI0
</pre></code>

In the active component log file you should start to see the "Hello World" lines displaying at a rate of about 1 per second.

{| cellspacing="0" cellpadding = "0" border="0" align = "center" width="680"
! style="color:black;background-color:#ffffaa;" align="center"| /root/asp/var/log/csa104CompI0Log.latest
|-
|<code><pre>
Mon Jul 14 19:07:27 2008 (SCNodeI0.21202 : csa104CompEO.---.---.00080 : INFO)
csa104CompI0: Hello World! (count = 0)
Mon Jul 14 19:07:27 2008 (SCNodeI0.21202 : csa104CompEO.---.---.00085 : INFO)
**** Inside the function : [clCompAppProvTxnStart] ****
Mon Jul 14 19:07:27 2008 (SCNodeI0.21202 : csa104CompEO.---.---.00087 : INFO)
Inside the function clcsa104CompCSA104RESProvObjectStart
Mon Jul 14 19:07:27 2008 (SCNodeI0.21202 : csa104CompEO.---.---.00089 : INFO)
Inside the function clcsa104CompCSA104RESProvValidate
Mon Jul 14 19:07:27 2008 (SCNodeI0.21202 : csa104CompEO.---.---.00105 : INFO)
Inside the function clcsa104CompCSA104RESProvUpdate
Mon Jul 14 19:07:27 2008 (SCNodeI0.21202 : csa104CompEO.---.---.00107 : INFO)
Inside the function clcsa104CompCSA104RESProvObjectEnd
Mon Jul 14 19:07:27 2008 (SCNodeI0.21202 : csa104CompEO.---.---.00116 : INFO)
**** Inside the function : [clCompAppProvTxnEnd] ****
Mon Jul 14 19:07:28 2008 (SCNodeI0.21202 : csa104CompEO.---.---.00123 : INFO)
csa104CompI0: Hello World! (count = 1)
Mon Jul 14 19:07:29 2008 (SCNodeI0.21202 : csa104CompEO.---.---.00124 : INFO)
csa104CompI0: Hello World! (count = 2)
Mon Jul 14 19:07:30 2008 (SCNodeI0.21202 : csa104CompEO.---.---.00125 : INFO)
csa104CompI0: Hello World! (count = 3)
</pre></code>
|}

<li>In the SAFplus Platform Console return to the Slot 1 context by entering <code>end</code> until it prints the Slot 1 prompt: <code>cli[Test:SCNodeI0]-></code>.
<code><pre>
cli[Test:SCNodeI0:CPM]-> end
cli[Test:SCNodeI0]->
</pre></code>

<li>Now set the context to the COR server using the following command:
<code><pre>
cli[Test:SCNodeI0]-> setc corServer_SCNodeI0
</pre></code>

<li>Then, dump the object tree:
<code><pre>
cli[Test:SCNodeI0:COR]-> objTreeShow
</pre></code>

You should see something like the following. There may be extra entries, but you should at least see an entry where <code>ClassName = CLASS_CSA104RES_PROV_MS0</code>.

{| cellspacing="0" cellpadding = "0" border="0" align = "center" width="680"
! style="color:black;background-color:#ffffaa;" align="center"| SAFplus Platform Console
|-
|<code><pre>
cli[Test:SCNodeI0:COR]-> objtreeshow

Objects (Instance Tree):
[0] ClassName=Chassis ClassId=0x10001 inst=0 [flgs=0x508]
[0] ClassName=SCNodeRes ClassId=0x10007 inst=0 [flgs=0x508]
*[3] ClassName=CLASS_SCNODERES_PROV_MSO ClassId=0x10009 inst=0 [flgs=0x508]
[0] ClassName=csa104Res ClassId=0x10002 inst=0 [flgs=0x508]
*[3] ClassName=CLASS_CSA104RES_PROV_MSO ClassId=0x10003 inst=0 [flgs=0x508]

</pre></code>
|}

<li>Next, dump the <code>CLASS_CSA104RES_PROV_MS</code> object with:
<code><pre>
cli[Test:SCNodeI0:COR]-> objectShow \Chassis:0\csa104Res:0 3
</pre></code>

{| cellspacing="0" cellpadding = "0" border="0" align = "center" width="680"
! style="color:black;background-color:#ffffaa;" align="center"| SAFplus Platform Console
|-
|<code><pre>
Showing Object
ClCorMOId:[Svc: 3] (/).(10001:0000).(10002:0000):

[Class:0x10003] Object
{
[CSA104RES_COUNTER ] [0x0002] = [431]
[CSA104RES_DELTA_T ] [0x0003] = [1000]
}
</pre></code>
|}

The 3 is the service ID of the object and is the value in brackets next to the asterisk on the <code>ClassName=CLASS_CSA104RES_PROV_MSO</code> line.

<li>Now, set the delta_t attribute to 10000 instead of 1000 with:
<code><pre>
cli[Test:SCNodeI0:COR]-> attrSet \Chassis:0\csa104Res:0 3 null 3 -1 10000
</pre></code>

{| cellspacing="0" cellpadding = "0" border="0" align = "center" width="680"
! style="color:black;background-color:#ffffaa;" align="center"| SAFplus Platform Console
|-
|<code><pre>
Execution Result : Passed
</pre></code>
|}

You should see lines like the following in the logs for csa104:

{| cellspacing="0" cellpadding = "0" border="0" align = "center" width="680"
! style="color:black;background-color:#ffffaa;" align="center"| /root/asp/var/log/csa104CompI0Log.latest
|-
|<code><pre>
Mon Jul 14 19:15:59 2008 (SCNodeI0.21202 : csa104CompEO.---.---.04230 : INFO)
csa104CompI0: The delta time is now [10000]
Mon Jul 14 19:15:59 2008 (SCNodeI0.21202 : csa104CompEO.---.---.04232 : INFO)
Inside the function clcsa104CompCSA104RESProvObjectEnd
Mon Jul 14 19:15:59 2008 (SCNodeI0.21202 : csa104CompEO.---.---.04241 : INFO)
**** Inside the function : [clCompAppProvTxnEnd] ****
Mon Jul 14 19:15:59 2008 (SCNodeI0.21202 : csa104CompEO.---.---.04248 : INFO)
csa104CompI0: Hello World! (count = 510)
Mon Jul 14 19:16:09 2008 (SCNodeI0.21202 : csa104CompEO.---.---.04249 : INFO)
csa104CompI0: Hello World! (count = 511)
Mon Jul 14 19:16:09 2008 (SCNodeI0.21202 : csa104CompEO.---.---.04254 : INFO)
**** Inside the function : [clCompAppProvTxnStart] ****
</pre></code>
|}

indicating that the component has received the updated value of delta_t

You should also notice that the lines in the log are now being printed with a 10 second interval between lines.

To confirm that the value of delta_t was updated you could dump the <code>CLASS_CSA104RES_PROV_MS</code> object with:
<code><pre>
cli[Test:SCNodeI0:COR]-> objectShow \Chassis:0\csa104Res:0 3
</pre></code>

{| cellspacing="0" cellpadding = "0" border="0" align = "center" width="680"
! style="color:black;background-color:#ffffaa;" align="center"| SAFplus Platform Console
|-
|<code><pre>
Showing Object
ClCorMOId:[Svc: 3] (/).(10001:0000).(10002:0000):

[Class:0x10003] Object
{
[CSA104RES_COUNTER ] [0x0002] = [523]
[CSA104RES_DELTA_T ] [0x0003] = [10000]
}
</pre></code>
|}

<li>To end the example first change the state of csa104SGI0 to LockAssignment.
<code><pre>
cli[Test:SCNodeI0:COR]-> end
cli[Test:SCNodeI0]-> setc cpm
cli[Test:SCNodeI0:CPM]-> amsLockAssignment sg csa104SGI0
</pre></code>

<li>Then change the state to LockInstantiation.
<code><pre>
cli[Test:SCNodeI0:CPM]-> amsLockInstantiation sg csa104SGI0
</pre></code>

<li>Then close the SAFplus Platform Console session.
<code><pre>
cli[Test:SCNodeI0:CPM]-> end
cli[Test:SCNodeI0]-> end
cli[Test]-> bye
</pre></code>

</ol>

===Summary and References===

We've seen how to:
*Create a simple ProvOm class.
*Use callbacks to the class's update method to update variables in the application at runtime.
*Use the SAFplus Platform Console to cause the classes update method to be invoked.

For further reading :
*Clovis SAFplus Platform User Guide: sections on COR,
*clProvOmApi.h
*clOmObjectManage.h
*clOmApi.h

@@ Line 499: / Line 499: @@
 |}
-<li>Next, dump the <code>CLASS_CSA104RES_PROV_MS</code> object with:
+<li>Next, dump the object with:
 <code><pre>
 cli[Test:SCNodeI0:COR]-> objectShow \Chassis:0\csa104Res:0 PROV

@@ Line 522: / Line 522: @@
 <li>Now, set the delta_t attribute to 10000 instead of 1000 with:
 <code><pre>
-cli[Test:SCNodeI0:COR]-> attrSet \Chassis:0\csa104Res:0 PROV null 3 -1 10000
+cli[Test:SCNodeI0:COR]-> attrSet \Chassis:0\csa104Res:0 3 null 3 -1 10000
 </pre></code>
@@ Line 533: / Line 533: @@
 |}
-You should see lines like the following in the logs for csa104:
+The 3 is the service ID of the object. You should see lines like the following in the logs for csa104:
 {| cellspacing="0" cellpadding = "0" border="0" align = "center" width="680"

@@ Line 558: / Line 558: @@
 You should also notice that the lines in the log are now being printed with a 10 second interval between lines.
-To confirm that the value of delta_t was updated you could dump the <code>CLASS_CSA104RES_PROV_MS</code> object with:
+To confirm that the value of delta_t was updated you could dump the object with:
 <code><pre>
 cli[Test:SCNodeI0:COR]-> objectShow \Chassis:0\csa104Res:0 3

@@ Line 473: / Line 473: @@
 </pre></code>
-You should see something like the following.  There may be extra entries, but you should at least see  an entry where <code>ClassName = CLASS_CSA104RES_PROV_MS0</code>.
+You should see something like the following.
 {| cellspacing="0" cellpadding = "0" border="0" align = "center" width="680"

@@ Line 479: / Line 479: @@
   |-
   |<code><pre>
-cli[Test:SCNodeI0:COR]-> objtreeshow
+cli[Test:SCNodeI0:COR]-> objTreeShow
 Objects (Instance Tree):
-     [0] ClassName=Chassis ClassId=0x10001 inst=0 [flgs=0x508]
+     \Chassis:0
-         [0] ClassName=SCNodeRes ClassId=0x10007 inst=0 [flgs=0x508]
+         \PayloadNodeRes:0
-             *[3] ClassName=CLASS_SCNODERES_PROV_MSO ClassId=0x10009 inst=0 [flgs=0x508]
+            (provisioning)
-         [0] ClassName=csa104Res ClassId=0x10002 inst=0 [flgs=0x508]
+        \PayloadNodeRes:1
-             *[3] ClassName=CLASS_CSA104RES_PROV_MSO ClassId=0x10003 inst=0 [flgs=0x508]
+            (provisioning)
    </pre></code>