Publishing Engine Programmer's Guide > PTC Arbortext Publishing > Content Pipelines > Creating Content Pipelines with ACL > Creating a Content Pipeline
  
Creating a Content Pipeline
A content pipeline is created by an ACL function call:
handle = get_composer(arr, name [, doc])
The arguments are specified as follows:
arr
specifies the ACL associative array which will be filled with the name and value of each parameter defined for the content pipeline as specified in the .ccffile. If a parameter has a default value not otherwise specified, the default is used. If a parameter has no default value, a null string is used. Parameter values can be specified in the .dcf file associated with the document type, and the value specified in the .dcf is used.
name
specifies the composer to create as well as the base name for the .ccf. If the value pdf is passed, then the search looks for a file named pdf.ccf in each directory for the composer path (including the custom\composer directory, set composerpath option, and the append_composer_path function).
doc
(optional) specifies the document to be published. If it is omitted or specified as 0, the current document is used.
The return value is either a handle or a null string. The handle can be used to reference the composer in later calls. If no .ccf file matches the name parameter, then a null string is returned.