Archives
Integration Flow Designer Enhancements
Transfer Mode Specification for Additional Files
For additional files (files other than the compiled map, Event Server system ‘.msl’ file , or command file) that are defined as part of a system deploy script in the Integration Flow Designer, the transfer mode can be specified as either ASCII (default) or Binary.
The IFD also permits the import and export of server definitions as XML files.
Event Server Enhancements
This feature enables the Event Server to run multiple processes within a single install. It will run each system in a different process allowing the user to add, remove and modify systems without affecting other running systems. Running the Event Server in separate processes also offers a more scalable and robust run-time environment. The Ascential DataStage TX Event Server can be configured to run using the CompoundSystem approach (all systems run in a single process), or to run each system (.msl file) in its own process.
By using the Global (or Central) Resource Management, when running systems in separate processes, they can share resource & the extra overhead is minimal. This could result in faster execution, as the systems run in separate processes.
The following Benefits can be realized by using the Event Server Multiple-processes facility.
• More robust run-time environment where problems occurring in maps or adapter connections in one system process will not cause problems in other Event Server processes
• The ability to add and reconfigure systems without stopping other systems
• The ability to use systems within systems for a single .msl system file for logical processes definitions.
Single Sourcing of Maps
This method is useful to refer a single map in multiple map source files. Using this new functionality, the user can create references to executable maps with one output card and to functional maps located in external map source files.
To reference a map in this case means to "single-source" – or use a map in an external map source file by creating a reference to it.
For maintenance reasons, this method can be used as an alternative to copying maps. By referencing a map, maintenance can be performed in one location instead of the several locations that the user might have copied the map to.
Viewing Run Results as XML
When displaying run results for input and output data, the user can view the results as XML or hexadecimal (hex) in addition to the regular text format.
Run results for data files with the following filename extensions display in XML mode also some of default modes available such as xml, xsd etc.
If XML validation errors occur, they are displayed as text.
Mercator offers a wide variety of adapters for input and output. When you begin developing your map, it is easiest to start with the File adapter. However, you will eventually want to add the commands for the adapter you will really be using. This document outlines the steps required for the MQSeries adapter, which is commonly used.
1. Using Mercator Map Designer, open the map you are developing.
2. Edit the Input or Output card of the executable map as appropriate.
3. Change the AdapterSource from File to MQSeries (server).
4. Type the following in the AdapterSourceCommand: -QMN
a. Queue Manager is what is on the UNIX Mercator server.
b. Queue Name is what is on the UNIX Mercator server.
c. The –QTY parameter means how many messages you are expecting. The s means any unlimited amount.
d. The –LSN parameter means how many seconds the map will listen to receive the messages.
e. The –t parameter means it will set a trace to monitor errors in receiving messages from or to MQSeries. You will want to remove this before moving to production.
5. Change OnSuccess to Delete.
6. Click OK.
7. To test the map, follow the instructions in the documents .
12. Create the functional map by selecting the Rules menu then Functional Map Wizard.
13. If the symbols are green, select each card and click Edit to rename them. Change Out to F_Out_Idoc. Change In1 to F_In_Extract.
14. When you are done renaming the cards, click Create.
15. On the functional map, create indexes to the segments you need until the individual fields are accessible.
• To create an index, right-click on the Output name and select Add Index.
16. Drag the fields from the Input card into the appropriate fields on the Output card per the specifications of the project analysis.
17. In the Segments that you are using, add rules under Data Record. SEGNAM should be the name of the IDoc Segment.
18. The MANDT rule can be the client you are sending to in SAP. However, this can also be left blank as it will default to whatever you use in the adapter command.
19. Fill in the following fields on the Control Record:
• TABNAM =”EDI_DC40”
• IDOCTYP is the Basic Type
• MESTYP, Message Type, is usually the same as Basic Type without the number
• SNDPRN =”MERCATORMM”
• ARCKEY = "[Your Team Name] " +DATETOTEXT(CURRENTDATE( ) )+" "+TIMETOTEXT(CURRENTTIME( ) )
20. Fill in all remaining fields with =NONE. To do this, select the Rules menu then Insert NONE if Empty.
21. Set the audit and trace files.
• Right-click the executable map name and select Settings.
• Expand the MapAudit and MapTrace and set the switches to ON. If appropriate, expand further to specify at which level you want the audit and trace recorded.
Note: Make sure you turn these off before moving to production.
22. Save the map.
23. Click the Build map icon.
24. Click the Run map icon.
25. Click the View run results icon to make sure the input mapped properly.
7. With the From card selected, select the Card menu then New. Fill in the following fields:
• CardName = In_* where * is descriptive of the application
• TypeTree = the input Type Tree you have created (use the drop down arrow to point and click to the Type Tree file location)
• TypeName = the file level of the tree you are testing (use the drop down arrow to point and click to the correct level)
• FileSourcePath = the input source of the data you are testing
Note: You should store all files in the same folders. This eliminates the problem of referential folder paths when you move to quality and production.
8. Click OK.
9. With the To card selected, select the Card menu then New. Fill in the following fields:
• CardName = Out_* where * is descriptive of the application
• TypeTree = the Type Tree you created by importing the .ido file (use the drop down arrow to point and click to the correct level)
• TypeName = Packet
• FileTargetPath = Output.txt
Note: When you have successfully tested your map from one flat file to another you will change the adapter of the output card to R/3. For instructions see 006 - Add R3 Adapter.doc. However, it is a best practice to begin simple so troubleshooting is easier.
10. Click OK.
11. Create the Rule to the functional map on the Idoc level. Type =F_Make_Idoc(). Then drag the record level of the Input card (From) into the parentheses.
When building a map, you start with the Mercator desktop application called Map Designer. From the desktop, you are able to compile the map and run it right from your PC. However, you will most likely run your map in production through a different platform. In that case, you need to compile and transfer your map to that platform. This document only contains instructions for development in the desktop environment. For instructions on testing your map in the UNIX platform.
1. Open Mercator Map Designer.
2. Choose “Create a new map source file” and click OK.
3. Name the file using a project, team, and application identifier.
4. Change the folder to Development folder and then to your team subfolders as appropriate.
Click Save.
5. Click the New map icon.
6. Name the map with the direction and the application as appropriate. For example, Inbound_MM means the map will be sending data into SAP (direction), and the data is Material Master (application).
When building a Type Tree, it is a good practice to develop a Validation Map to confirm that the input file matches the tree design. This is not something that needs to be moved into production and is not a necessary step in the development process. However, the advantage of building a Validation Map is that you can catch problems in your Type Tree before you begin building your map. You should only do this on the Type Trees you have built from scratch. Type Trees that have been imported from another source such as R/3 can be trusted and do not need a Validation Map.
1. Open Mercator Map Designer.
2. Choose “Create a new map source file” and click OK.
3. Name the file using a project, team, and application identifier.
4. Change the folder to Mercator folder and your team subfolders as appropriate. Click Save.
5. Click the New map icon.
6. Name the map *_Validation where * is descriptive of your project, team, and application.
7. With the From card selected, select the Card menu then New. Fill in the following fields:
• CardName = In_* where * is descriptive of the application
• TypeTree = the tree you are testing (use the drop down arrow to point and click to the Type Tree file location)
• TypeName = the file level of the tree you are testing (use the drop down arrow to point and click to the correct level)
• FileSourcePath = the input source of the data you are testing
8. Click OK.
9. With the To card selected, select the Card menu then New. Fill in the following fields:
• CardName = Out_* where * is descriptive of the application
• TypeTree = the tree you are testing (use the drop down arrow to point and click to the Type Tree file location)
• TypeName = the file level of the tree you are testing (use the drop down arrow to point and click to the correct level)
• FileTargetPath = Output.txt, which will create a text file in the same folder where the map is stored.
10. Click OK.
11. Drag In_* to the Rule next to Out_*.
12. Save the map.
13. Click the Build map icon.
14. Click the Run map icon.
15. Click the View run results icon to make sure the input mapped properly.
If your Mercator system will be sending data to or reading data from an R/3 IDoc, you do not have to manually build the Type Tree. Instead, SAP provides a transaction for exporting an IDoc file, and Mercator has a wizard for importing the IDoc file. Using this method will greatly simplify your development process.
1. Import the IDoc from SAP to your Application drive.
a. Open SAP GUI and go to transaction WE63.
b. Select the appropriate Basic type or Enhancement.
c. Make sure the Control, Data, and Status Record checkboxes are selected.
d. Click the Parser button.
e. When the IDoc returns, go to System -> List -> Save -> Local File.
f. Select unconverted and click the Continue icon.
g. Save the file to Development folder and then your team’s folder as appropriate. A good practice is to name the file with the
Example: MATMAS03.ido
h. Click the Transfer button.
2. When the transfer is complete, open Mercator Type Designer.
a. Select “Import a type tree” and click OK.
Note: If you already have the Type Designer open, select the Tree menu then Import.
b. Import from R/3:IDOC and click Next.
c. Choose the correct operating system as appropriate. Click Next.
d. The character set is Native. Click Next.
e. The IDoc type is ALE. Click Next.
f. Save the file to the same location and file name as in step 1.f above. This time the extension will be .mtt. Click Next.
g. When the import is done processing, click Finish.
h. You do not need to make any changes to the type tree.
DirectTV channels are really gives us many channels in low budget .And it is really a mind blowing one which you ever get from any other providers.
- But we are happy now that we can get the favorite channels at very low cost through Direct TV. We can get amazing Direct TV channels in various packages from Direct TV. We are given many opportunities to select the packages based on our wish and our comfort the budget.
- In all the Packages, we get extra channels besides the local channels. Some of the packages offered by Direct TV is mentioned below in which Surprising gifts like DVR or HD receiver after instant rebate is free to take to your home and their channels are really amazing, exiting offer.
- First amazing ultimate Entertainment package is called Premier, which telecast Over 250 channels free.Also we will get premium movie channels and sports networks as an offer.
- Second amazing ultimate HD package is called PLUS HD DVR, which telecast Over 195 channels free.Also we will get 68 XM Satellite Radio channels as an offer.
- Third and very good for the TV fan on the go package is called PLUS DVR, which telecast Over 185 channels free. Also we will get 68 XM Satellite Radio channels and DVR service as an amazing offer.
- Fourth and Fabulous TV lover package is called CHOICE XTRA which telecast Over 185 channels Also we will get 68 XM Satellite Radio channels service as an amazing offer.
- Below are the success mantras of DirectTV and use these services and enjoy.
- FAST RESPONSE
- EASY-TO-USE HOME SYSTEMS
- 24-HOUR ADT MONITORING
- LOW MONTHLY FEES
If your Mercator system will be sending data to or reading data from an R/3 IDoc, you do not have to manually build the Type Tree. Instead, SAP provides a transaction for exporting an IDoc file, and Mercator has a wizard for importing the IDoc file. Using this method will greatly simplify your development process.
1. Import the IDoc from SAP to your KCApps drive.
a. Open SAP GUI and go to transaction WE63.
b. Select the appropriate Basic types.
c. Click the Execute icon or press F8.
d. When the IDoc returns, select the List menu then Download.
e. Select unconverted and click the Continue icon.
f. Save the file to the developement folder that is in your team’s folder as appropriate. A good practice is to name the file with the
Example: MATMAS03.ido
g. Click the Transfer button.
2. When the transfer is complete, open Mercator Type Designer.
a. Select “Import a type tree” and click OK.
Note: If you already have the Type Designer open, select the Tree menu then Import.
b. Import from R/3:IDOC and click Next.
c. Choose the correct operating system as appropriate. Click Next.
d. The character set is Native. Click Next.
e. The IDoc type is ALE. Click Next.
f. Save the file to the same location and file name as in step 1.f above. This time the extension will be .mtt. Click Next.
g. When the import is done processing, click Finish.
h. You do not need to make any changes to the type tree.
Building a Mercator Type Tree is the first step in developing a Mercator system. It is the data definition file for your data. This document includes instructions for standard best practices for development and naming practices. Some projects need a more robust use of the tool, in which case you will need to change the standards for things such as Subclass, Range, and Initiators/Terminators.
1. Open Mercator Type Designer.
3. Under the root level insert
- A Category named “Field”.
- A Category named “Message”.
- A Group named to describe the application.
5. Under the Field level insert Items for each data field. All of the fields should be formatted as follows:
- Item Subclass = Text
- Interpret as = Character
- Pad = Yes
- Value =
- Padded to = Fixed Size
- Justify = Left
6. The Size parameter should have Min = 0 and Max = the length specified in the copybook of the input file. When you enter the Max length, the Padded to Length should fill in automatically to be the same.
Note: If you ever change the Max field, you must manually change the Padded to Length field.
7. Double-click the Record Group and drag each Field into the table. Make sure they appear in the same order as the copybook of the input file.
8. The Range = 1:1 on all Fields.
Note: If you do not have the Range displayed, click the Tools menu then select Options. Choose Group Window. Select “Show range column” and “Show component number”. Click OK.
9. Under the Message level insert a group called Generic.
10. The Partitioned parameter for Generic = Yes.
11. Under the Generic level insert a group called File.
12. Double-click File and drag the Record Group to the table.
13. The Range = s.
Note: There are no Terminators or Initiators on any of the objects.
14. Save the type tree using the name in Step 2 above.
What is Mercator?
• Event driven software than can interface virtually anything to anything.
Transaction Types:
- RosettaNet 3B2, 4B2
- CIDX
- Proprietary XML
- ANSI X.12 EDI (185, 180, 204, 210, 211, 214, 310, 810, 830, 832, 846, 850, 856, 864, 940, 943, 944, 945, 947, 997)
- Proprietary Flat File
- Database (Oracle)
Mercator Integration Broker 6.5
Mercator Event Agent
Mercator Adapters In use
FTP, EMAIL, Socket, Oracle, HTTP, HTTPS, Sink
Mercator Commerce Manager
Partner Manager
Message Manager
Mercator Design Studio
Integrate disparate systems
Increase integration complexity
Manage the integrated environment
Keep up with the B2B revolution
• Utility Adapters:
– Archive (ZIP)
– Archive (Tar)
– Batch file and Shell Script
– Sink (NULL)
– FTP
– HTTP
– LDAP
– XML
• Application Adapter
• Messaging Adapters:
– IBM MQSeries
– MSMQ Messaging
– BEA MessageQ
– BEA Tuxedo
– TIB/RV
– Oracle8 AQ
– Roma BSP
• R/3 Adapters:
– IDOC
– DXOB
– BDC
– BAPI
Mercator delivers a suite of integration brokers for:
• Integrate disparate systems
• Increase integration complexity
• Adapt to new formats and semantics
• Migrate from old to new applications
• Manage the integrated environment
• Keep up with the B2B revolution
