11/22/2024 8:55:38 AM
|
| |
| slxdeveloper.com Community Forums |
|
| |
|
|
The Forums on slxdeveloper.com are now retired. The forum archive will remain available for the time being. Thank you for your participation on slxdeveloper.com!
Forum to discuss general administration topics for SalesLogix (including LAN & remote topics). View the code of conduct for posting guidelines.
|
|
|
|
SalesLogix Agent functionality 
Posted: 31 Aug 07 1:18 AM
|
Hi All,
Can anybody tell me, how does SalesLogix Agent functionality works in the SalesLogix system. What all needs to be done to set up the Agent in the SalesLogix system?
Thanks in Advance.
Amit |
|
|
|
Re: SalesLogix Agent functionality
Posted: 31 Aug 07 7:53 AM
|
Agents are executed as part of the synchronication process. At the end of a sync cycle the SyncServer.exe program calls AgentQueue.exe which checks to see if there are any SLX Agents that should be run. If something need to be run AgentRunner.exe is called to run the scheduled Agent.
Agents a setup using the WorkGroup Administrator. Scripts, reports, and some other items can be run.
If you haven't already you may want to check out the help in the WorkGroup Administrator. |
|
|
| |
|
Re: SalesLogix Agent functionality
Posted: 03 Sep 07 3:42 AM
|
Hi Frank,
I had gone through the help in the Administrator.
The saleslogix system had been upgraded from version 5.0 to version 6.2.
An agent had been created in the system for importing the details from a text file. But this is not working.
The import is happening when the import button on the client is selected manually.
Upon looking in the system, there is no SalesLogix Synchronization Server listed as one of the services.
Is this the problem? If yes, do we need to define the Synchronization Server service or are we missing anything else.
Thanks,
Amit
|
|
|
|
Re: SalesLogix Agent functionality
Posted: 03 Sep 07 8:23 AM
|
Normally, Agents do not operate unless you have sync implemented and the sync server running.
However, there is a "trick" that's been used by several partners to use the agent as a "job processor/runner".
NOTE: You MUST have certain exe's available to do this:
AgentQueue.exe and Agentrunner.exe
Here's how to use the "Agent" to run scheduled jobs w/out the sync server:
Background:
The "Agent" jobs are normally run by the Sync Server. When a job is in setup in the "que" using the (WG)Admin and scheduled for a particular time, the sync server checks for "queued" agent jobs after a sync run. If there are any scheduled they are then launched. Now if one does not have a sync server setup (and if you have no remotes that would be true) it is possible to use the AgentRunner as a job scheduler. In order to do so, you need to know a little bit about how the "Agent" subsystem works.
Working forward:
Setup an Agent in the (WG)Admin:
Systems->Agents
Insert->Agent or RMB Add Agent
Fill in:
Name: some Unique name for this Agent
Select User (usually administrator)
Email (normal email addresses or list separated by the ; character)
Action: (ex: CRW-EMailReport-As-PDF)
Argument: Select the report you want to run/email
Description: (Optional but recommended - EX: Special agent)
NOTE: Do NOT select anything else - not even the Active checkbox or schedule
Click OK and Save
We need to know the ID of the agent - so locate it by:
SELECT AGENTID
FROM sysdba.AGENTS
WHERE NAME = 'some Unique name for this Agent'
At this point we have two choices as to how we proceed so I'll describe both:
OPTION A:
Create a .CMD file and put the following in the file:
REM
REM My Agentrunner
REM
"C:\Program Files\SalesLogix\Agentrunner.exe" SalesLogixDbAlias AGENTID
Where:
SalesLogixDBAlias is the Alias for your SalesLogix db (EX:SalesLogix")
AGENTID is the ID of the AGENT Job (EX: Q6UJ9A001AJL)
Save the file in a location of your choice
Test the job by doing a Start-Run (-Browse to the cmd file) OK
- the job should run - if not, re-check your steps
Using the Windows Task Scheduler, Setup a Scheduled task to run the cmd file above
OPTION B:
Create a file and name it "TheAgents.que" in the SalesLogix Program Directory (using Notepad or some other text editor) and put the following in the file:
Agentrunner SalesLogixDbAlias AGENTID
Where:
SalesLogixDBAlias is the Alias for your SalesLogix db (EX:SalesLogix")
AGENTID is the ID of the AGENT Job (EX: Q6UJ9A001AJL)
Save the file in a location of your choice
Test the job by doing a Start-Run (-Browse to AgentQueue.exe in the SalesLogix Directory) OK
- the job should run - if not, re-check your steps
Using the Windows Task Scheduler, Setup a Scheduled task to run the following:
"C:\Program Files\SalesLogix\AgentQueue.exe"
Either method will let you run multiple jobs.
OPTION A:
Same Time (Sequentially): Add more lines to the .CMD file for additional jobs
Different Times: Create more .CMD file(s) for each job and setup Task Schedules
OPTION B:
Same Time (Sequentially): Add more lines to the "TheAgents.que" file
Different Times: Not possible with this option.
--
rjl
|
|
|
|
Re: SalesLogix Agent functionality
Posted: 18 Mar 14 6:00 PM
|
RJ,
I know this is an old thread, but I'm having issues with this.
Agent script created and runs fine. I've run via sync and your non-traditional method above, and everything runs as expected, but... Running as suggested above, with either method, the issue is that the script ends, but AgentRunner continues to run and take up all the CPU on the server.
What do I need to do to make AgentRunner stop? Besides Task Manager and End Process?!?!!
Thanks in advace for your help.
Dawn |
|
|
|
You can
subscribe to receive a daily forum digest in your
user profile. View the site code
of conduct for posting guidelines.
 Forum RSS Feed - Subscribe to the forum RSS feed to keep on top of the latest forum activity!
|
|
|
|
|
|
|
|