Run AIF inbound and outbound manually

Klaas Deforche — Wed, 17 Feb 2010 17:51:53 +0000

To have AIF import and export message, you have to have 4 batch tasks running (all about it here on TechNet). However, when developing, it is inefficient (and also tad tedious) to wait for those batches.

Here are two jobs to run inbound and outbound messages manually, so you don’t have to wait for the batches to pick them up.

Inbound:

static void KlForrunAIFInbound(Args _args)
{
;
// read the messages
new AifGateWayReceiveService().run();

// process the messages in queue
new AifInboundProcessingService().run();

info("done");
}

Outbound:

static void KlForrunAIFOutbound(Args _args)
{
;
// process messages in queue
new AifOutboundProcessingService().run();

// send messages
new AifGateWaySendService().run();

info("done");
}

Ofcourse, you can put this code in classes, or combine them so they are executed together. Because inbound messages can trigger outbound messages, it’s better to process the inbound messages before the outbound messages.

Writing in the event log from Dynamics AX

Klaas Deforche — Fri, 19 Jun 2009 11:14:55 +0000

Writing to the event log in Windows using AX is very easy when you use the EventLog class from the System.Diagnostics namespace. The following job demonstrates how to use the EventLog class.

static void EventViewer(Args _args)
{
System.Diagnostics.EventLog eventlog;
#Define.LogSource("Dynamics AX")
#Define.LogName("Dynamics AX Log")

;
// check if the log already exists
if(!System.Diagnostics.EventLog::SourceExists(#LogSource))
{
// create new log
System.Diagnostics.EventLog::CreateEventSource(#LogSource, #LogName);
}

eventlog = new System.Diagnostics.EventLog();
eventlog.set_Source(#LogSource);

// write info entry
eventlog.WriteEntry("Just writing in the event viewer.");
// write error entry
eventlog.WriteEntry("Error! Please check the stack trace below. \n\n" +
con2str(xSession::xppCallStack()), System.Diagnostics.EventLogEntryType::Error);
// write warning entry
eventlog.WriteEntry("Job finished." , System.Diagnostics.EventLogEntryType::Warning);

info("Check the event viewer!");
}

A possible use for this is when monitoring batch jobs.
Tested using AX 2009, XP Pro.

Art Of Creation - Dynamics AX Blog » Batch

Run AIF inbound and outbound manually

Writing in the event log from Dynamics AX