General Conventions

 

§        Spell out all words used in the name.  Do not abbreviate unless the object name becomes long.

§        Avoid the use of underscores within object names.

§        Object names shall be in standard “Hungarian” (upper and lower) case.

§        No spaces are allowed in object names.

 

 

Prefixes associated with BizTalk objects are contained in the following table:

 

Configuration/Object Name

Prefix

Suffix

Example

 

 

 

 

Orchestration Port Types

oprt

Type

oprtPOTypeSend

oprtPOTypeReceive

oprtPOTypeBoth

Send Port

sprt

Send

Both

 

Adapter:

FILE

SQL

HTTP

SOAP

sprtPOSendFILE

Receive Port

rprt

Receive

Both

 

rprtPOReceive

Orchestration Port

oprt

Send

Receive

Both

oprtPOReceive

oprtInvoiceSend

 Mult Part Message Type

mpm

Type

mpmSalesOrderType

 Multi Part Message

mpm

 

mpmSalesOrder

 Correlation Type

cor

Type

corMatchPOToSupplierType

 Correlation Set

cor

 

corMatchPOToSupplier

 Role Link Type

rol

Type

rolReceivePOType

Role Link

rol

 

rolReceivePO

 Variables (Opt)

.net coding standards

 

Messages (opt)

msg

 

msgNWPO

Orchestration

orc

 

orcOrderProcess

Message Queue

que

 

queErrors

BizTalk Receive Location

rloc

TransportType :

FILE

SQL

HTTP

SOAP

rlocPOFILE

BizTalk Schema Specification

sch

(opt)

FLATFILE

XML

EDI

IDOC

ENV

schPurchaseOrderXML

BizTalk Map

map

Drop sch from schema prefixes, add "To" in between

mapPOFLATFILEToTriggerXML

Functoid (Within Maps)

fnc

 

fncCurrentDate

Send Pipeline

spip

XML

FLATFILE

IDOC

EDI

 

Receive Pipeline

rpip

 

 

 

Schema/Document Definition Naming Convention

In addition to the “sch” prefix that is appended to all BizTalk specifications and document definitions, the following convention should be followed:

“sch” + [Description] + [Type of Schema]

where:

§        Description = a document description maybe a project name or entity name or application name

§        Type of Schema: FLATFILE, EDI, XML

Map Naming Conventions

In addition to the “map” prefix appended to all BizTalk maps, the following naming convention should be followed:

“map”  + [SourceSpec] + “To” + [DestinationSpec]

where:

§        SourceSpec = name of source specification excluding the specification prefix “sch”

§        DestSpec = name of destination specification excluding the specification prefix “sch”