Jun 30, 2016

MEC: Change out file name dynamically

Background

Manipulating the out file name generated by the middle ware is a common scenario. By default file names are generated with a GUID (13a7a838-a706-4273-b190-9d58a79bf04e). It is more practical if the file name is human readable.

Solution

  1. In the Mapper add User function to change the file name. (Note: this function should the last function in the map)
    image
  2. Add similar code to the function. This code set file name to the manifest information of the map.
    [sourcecode language='java'  padlinenumbers='true' collapse='false' toolbar='false']
    String date = new java.text.SimpleDateFormat("yyMMdd").format(new java.util.GregorianCalendar().getTime());
    String time = new java.text.SimpleDateFormat("HHmmss").format(new java.util.GregorianCalendar().getTime());
    
    String fileName  = "EDI_832_OUT_"+ date+time;
    
    setManifestInfo("map:FileName", fileName);
    [/sourcecode]
    
  3. Then, configure the relevant Send (in partner agreement) object to take the given file name.
    image
  4. And you are done. !!!

Jun 5, 2016

Development with MEC older version

Presently I’m working with a MEC older version (Ver 9.1).

This version is not part of an Eclipse plugin. It’s a standalone application that use for MEC mapper development. Very tedious to work with.

MEC Mapper different than the Eclipse version. But Flat file definition tool, it’s manager & the partner agreement tool looks the same.

Mapping manger looks like this.

Mapping Manger

  1. Load button to retrieve all the existing mappings.
  2. New button to create a new one
  3. Generate & Publish buttons to compile the map & deploy to the server
  4. Import & export button: Once you create a map, you cannot change it. Instead, import existing version and export with a new changes and new version number

Mapper looks like this.

Mapper

  1. Mapping flow is organized in “tree-view” like structure.
  2. You can generate the map from this screen. But to publish you have to close this and go back to Mapping manger & publish.
  3. Two options to save (to DB & to File)
  4. Validate map option also available on this screen.

Mar 28, 2016

ISO SDK : Unkown Error

Problem

I’ve got following error when I try to testing after configuring ISO SDK.
ISO_ERROR_Unknown

Solution

When you configure “SERVER” path in the registry entry  (HKEY_CURRENT_USER\Software\Lawson\MangoDev)  make sure correct path of LSO server path is set.  

How to get correct LSO PATH?

  1. Go to the log viewer of the LSO by clicking
    LogView
  2. Then select following entry & copy LSO server path
    LSOServerPath

What I got wrong?

I’ve set LSO client installation path (that can be access through Web browser) to the “Server” registry entry.

Jan 26, 2016

How MEC Message Flow Work

Like any other middle-ware application MEC has unique architectural components. Below diagram depicts them.

Sol_Consept

  1. Inbound message will be consumed by the MEC and goes through detection rules defined in the partner agreement. Detection is either channel or XML detection. If inbound message is a flat file, channel detection will be used.
    For XML detection, inbound message must have meta data to configure the detection.

    Note below payload has RequestHeader as meta data.
    <ItemInfo>
    <RequestHeader>
    <environment>A</environment>
    <program>B</program>
    <company>A</company>
    </RequestHeader>
    <RequestBody>
    <!-- Items goes here-->
    </RequestBody>
    </ItemInfo>



    detection configuration is:
    XMLDetect
    • Detection information  & rules are saved in MEC storage. MEC will evaluate all saved detections (in a order) until its find the correct one.
  2. Once the detection has passed, process the message based on the defined processing steps. (in the given order)
    mec_proc
    • These steps are also saved on the MEC Storage
  3. Generate the output message.

Jan 18, 2016

M3 Integrations (MEC)

I was able to refresh my knowledge of   M3 integration with MEC (M3 E-collaborator).  MEC is a middle-ware specifically design for M3 integration development. Over the past few years it has been evolved.

MEC has following components:
  1. Flat-File definition tool -  Using this tool you can create XML schema file. Also it can generate sample Flat File & XML file for the schema. 
  2. Flat-File Repository manger - Is the repository for the local and server definitions. 
  3. Mapper - Use to transform data to a output file or update M3 directly for the given input schema and the defined logic. It has certain functions to perform this level of transformation.  (Later, with my next posts I'm hopping to reveal them). If you are familiar with Ms-BizTalk server, it's orchestration and MEC mapper is  similar in behavior. 
  4. Partner Admin tool - Use to configure agreement for the integration such as, 
  • Detection
  • Processes
  • Error handling
  • and other admin tasks (e.g. communication, web-service definitions, EventHub subscriptions etc.) 
Its mapper look as follows, 

MEC Mapper
MEC Mapper


Aug 23, 2015

Microsoft Band- My Health Companion

I was looking for a kind of monitor or tool to track my varies health related things. Doctor recommended me to walk at least 3 km &  workout 15mins daily.  I want to track my sleeping patterns as well.  ( Note: This is not to diagnose something, but to stay healthier)

I found Microsoft Band is satisfying my needs. Also it provides additional cool features. (As always Microsoft gives us something more additionally) It stands among similar products. So, three weeks ago, I bought a Microsoft Band.

20150808_105256

Now I can

  1. keep an eye on my sleeping pattern.
    20150808_105316
  2. see the distance I made so far
    20150808_124937
  3. see details about my workout session
    20150808_125121

Microsoft Band require Microsoft Health App which sync through Bluetooth 4.0 and App will sync to Microsoft Health web dashboard where you see drilled-down data.

image
image

Why don’t you try it?

Feb 25, 2015

Add Scrip Map error in IIS 7

Error:

The specified module required by this handler is not in the modules list. If you are adding a script map handler mapping, the IsapiModule or the CgiModule must be in the modules list.

image

Background:

I had this error message when configuring BTSHTTPReceive.dll into Handler Mappings  of IIS 7 in my development machine.

Solution:

Windows 7 64 bit:

  1. Go to the “Control Pannel” –> “Programs and Features”
  2. Click on “Turn Windows features on or off”
  3. Make sure “Application Development Features” are enabled.

image