Hi Michael,
I have created a new thread as in the previoius thread it was not possible for me to reward points. (The radio buttons to reward points were not visible.)
Previous discusssions are
Hi,
Has anyone used the subscription agent available in admin console.
As I know the subscription agent attaches subscription to more than one site.
I looked into the subsciption agent and found that it has criteria rules. The criteria rules are of 4 different types
1. Static where clause
2. dynamic where clause
3. function
4. interlinkage
In the static where clause
there is a tab named 'Table'. In this tab there are 3 fields
1. Table
2. Field to be read
2. Field Employee key to be read.
First 2 fields are clear. What is the field "Field Employee key to be read " used for. Here generally 'SFAMITABT' is entered. If this field is entered where is the value entered for this field.
Could anyone tell me the purpose of this field.
Any help will be highly appreciated.
doubt2:
There is a background job linked to the subscription agent. What does the background job do?
kind regards
middleware developer
Michael Van Geet
Posts: 204
Registered: 8/9/05
Read Re: Subscription Agent
Posted: Oct 27, 2005 6:40 AM
Click to reply to this topic Reply E-mail this post E-mail this post
Hi,
the subscription agent is used for dynamic subscription & site generation. It allows dynamic changing of criteria fields on subscriptions.
The agents are based on publication, criteria fields and employees. The employees are used to determine the sites to which the subscriptions need to be attached. For example, if employee "Michael" is attached to site "pc798", then the subscription agent determines that site "pc798" must receive the subscription if employee "Michael" is used.
Employees are stored (on the CDB) in table SMOMITABT, of which SFAMITABT is the key. The subscription agents use this table because it contains all the relevant employee information and links to the mobile clients.
In the definition of the agent, it's possible to enter criteria when & how the agent should be executed. You can also start it manually in background by right-clicking on the agent & choosing "execute in background".
I've always found it easiest to use the function-option to determine employees & criteria-fields --> it very flexible.
Grtz,
Michael.
Now the below part is replying back for further information. Here I could award points.
Hi Michael,
Based on your reply, I have additional doubts.
Point 1:
I understood why employees are linked to sites and subscriptions here.
But if I take the static where clause where the criteria rule and the employee exist in the same table, then a field name "Employee Key to be read". Here I enter the Field name.
Where should I enter the actual employee. Let say geetha and Michael sites need data, I need to enter these users. Where should I enter. (I guess, I need to enter in the value tab as follows
Record 1
fieldname = 'SMOMITABT'
operator = 'EQ'
Static Value = 'Michael'
AND/OR = and
Record 2
Fieldname = 'SMOMITABT'
Operator = EQ
Static value = 'Geetha'
)
Point 2:
You have explained that you feel comfortable with the function option to determine employees and criteria fields.
Can you please send me a function for a BDoc which you have done. My email id is jothianjali@yahoo.com
Point 3:
You have explained that the agent can be executed in background. Usually background jobs are required when it needs to be done periodically.
Can you explain a scenario, where the subscription agent needs to be scheduled periodically.
Point 4:
Also when is the options 1. Append , 2. Update come into picture. In real scenaio how it works, when each option is choosen.
I know that this is a very lenghty doubt. I appreciate your valuable time and patience. Could you please throw some more light on this.
kind regards
middleware developer