For each server model, there is a connection_includefile.edml file that defines the connection type and maps the properties that are defined in the include file to elements in the MX interface.
provides, by default, seven definition files, one for each of the predefined server models, as listed in the following table.
| ASP JavaScript | ASP_Js |
| ASP.NET CSharp | ASP.NET_Csharp |
| ASP.NET VBScript | ASP.NET_VB |
| ASP VBScript | ASP_Vbs |
| ColdFusion | ColdFusion |
| JavaServer Page | JSP |
| PHP MySql | PHP_MySql |
uses the quickSearch and searchPattern parameters to recognize connection blocks and the insertText parameter to create connection blocks. For more information on XML and regular expression search patterns, an include file for a new server model, you need to map the connection parameters with the UI, Live Data, and Preview In Browser. The following sample XML file, which is associated with the default ASP JS server model, maps all connection page variables with their respective live values before sending the page to the server. For more information on XML and regular expression search patterns,
<participant name="connection_includefile" version="5.0"> <quickSearch> <![CDATA[// HTTP=]]></quickSearch> <insertText location=""> <![CDATA[<% // FileName="@@filename@@" // Type="@@type@@" @@designtimeString@@ // DesigntimeType="@@designtimeType@@" // HTTP="@@http@@" // Catalog="@@catalog@@" // Schema="@@schema@@" var MM_@@cname@@_STRING = @@string@@ %> ]]> </insertText> <searchPatterns whereToSearch="directive"> <searchPattern paramNames="filename"> <![CDATA[/\/\/\s*FileName="([^"]*)"/]]></searchPattern> <searchPattern paramNames="type,designtimeString"> <![CDATA[/\/\/\s+Type="(\w*)"([^\r\n]*)/]]></searchPattern> <searchPattern paramNames="designtimeType" isOptional="true"> <![CDATA[/\/\/\s*DesigntimeType="(\w*)"/]]></searchPattern> <searchPattern paramNames="http"> <![CDATA[/\/\/\s*HTTP="(\w+)"/]]></searchPattern> <searchPattern paramNames="catalog"> <![CDATA[/\/\/\s*Catalog="(\w*)"/]]></searchPattern> <searchPattern paramNames="schema"> <![CDATA[/\/\/\s*Schema="(\w*)"/]]></searchPattern> <searchPattern paramNames="cname,string"> <![CDATA[/var\s+MM_(\w*)_STRING\s*=\s*([^\r\n]+)/]]></searchPattern> </searchPatterns> </participant>Tokens in an .edml file—such as @@filename@@ in this example—map values in the include file to properties of a connection object. You set the properties of connection objects in the .js implementation file.
All the default connection dialog boxes that come with MX use the connection_includefile.edml mapping file. To let MX find this file, its name is set in the .js implementation file as shown in the following example:
var PARTICIPANT_FILE = " connection_includefile ";When you create a custom connection type, you can use any mapping file in your custom dialog boxes. If you create a mapping file, you can use a name other than connection_includefile for your .edml file. If you use a different name, you need to use this name in your .js implementation file when you specify the value that is assigned to the PARTICIPANT_FILE variable, as shown in the following example:
var PARTICIPANT_FILE = "myConnection_mappingfile";1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117