Platform-specific file name extensions

Maps built for execution on Windows platforms use the default .mmc compiled map file name extension.

The Build for Specific Platform command creates a compiled map file in the format required for a specified platform, which accounts for byte-order and character set differences on that platform.

By default, the Map Designer assigns a platform-specific file name extension to maps built for specific platforms. You can change the default file name extension under Window > Preferences > Transformation Extender Compiled Map Extensions.

The default file name extensions for compiled maps are listed in the following table.

Platform: Extension
HP-UX (Itanium processor): .hpi
IBM® AIX® (RS/6000® processor): .aix
IBM z/OS®: .mvs
Linux® (Intel processor): .lnx
Microsoft Windows: .mmc
pLinux: .pnx
Sun Solaris (SPARC processor): .sun
zLinux: .znx

Create a folder exclusively for platform-specific maps.

To build a map for a specific platform:

Select the map in the Outline view or the Composition view.
Select the Build for Specific Platform option in one of the following ways:
- From the menu bar, click Map > Build for Specific Platform.
- Right-click the map and click Build for Specific Platform.
Select the specific platform on which you plan to run the map.

After the map is built for the specific platform, perform a binary file transfer of the compiled map file to the remote server environment. For example, to transfer the ported map to your UNIX server, you can use the File Transfer Protocol (FTP). You can also deploy the compiled maps from the Map Designer to the remote servers. Double-click the .dtxdeployment file that is under your project in the Navigator view, or in the Misc folder under your project in the Extender Navigator view. In the Deployment Editor, click Deploy to build and transfer the maps to the remote servers that you specified under Window > Preferences > Transformation Extender Deployment.

A platform-specific build is not required if all of the items referenced in map rules have specific character sets and a specific byte order. No items have a native definition.
For example, you might have a map whose only purpose is to convert data from ASCII to EBCDIC. However, to avoid mistakes, always use the Build for Specific Platform option when your target platform has a different byte order or character set than the byte order or character set in your map development environment.
A platform-specific build is not required if you select a platform whose byte order and character set are the same as the byte order or character set on your development machine.