SAS 9.1.3 Integration Technologies » Developer's Guide


Publish Package Interface
Publish/Retrieve Encoding Behavior
Publishing Packages
INSERT_CATALOG
INSERT_DATASET
INSERT_FDB
INSERT_FILE
INSERT_HTML
INSERT_MDDB
INSERT_PACKAGE
INSERT_REF
INSERT_SQLVIEW
INSERT_VIEWER
PACKAGE_BEGIN
PACKAGE_END
PACKAGE_PUBLISH
LDAP Channel Store Syntax
SAS Metadata Repository Channel Store Syntax
Retrieving Packages
COMPANION_NEXT
ENTRY_FIRST
ENTRY_NEXT
PACKAGE_DESTROY
PACKAGE_FIRST
PACKAGE_NEXT
PACKAGE_TERM
RETRIEVE_CATALOG
RETRIEVE_DATASET
RETRIEVE_FDB
RETRIEVE_FILE
RETRIEVE_HTML
RETRIEVE_MDDB
RETRIEVE_NESTED
RETRIEVE_PACKAGE
RETRIEVE_REF
RETRIEVE_SQLVIEW
RETRIEVE_VIEWER
Filtering Packages
Publishing Examples
Publishing in the Data Step
Publishing in a Macro
Publishing with FTP
Publishing Framework

LDAP Channel Store Syntax

If channel definitions and subscriber definitions are maintained in an LDAP directory, then the syntax for the CHANNEL_STORE property is as follows:

LDAP://hostname:port/dn?attributes?scope?filter?bindname=bindname, password=password; Where:

hostname
name of LDAP server that contains channel information. HOSTNAME must be DNS name or IP address of a host that is running an LDAP server. If HOSTNAME is left blank or is not specified, the macro variable LDAP_HOST is used. If this too is blank or not defined, the LDAP host is assumed to be the host that is running the application that placed the CALL.

Port
TCP port of the LDAP server. If zero or not specified, the macro variable or environment variable LDAP_PORT is used. If this too is blank or not defined, the standard port of 389 is used.

dn
distinguished name is the base object that specifies the point in the LDAP tree where the channel search is to begin. If this value is blank, the macro variable or environment variable LDAP_BASE is used for the definition of the base.

bindname
base distinguished name used to bind to the server. When specifying the bindname on the LDAP store information string, any commas or question marks that are contained within the bindname must be replaced with their ASCII hexadecimal equivalents. The format of the ASCII hexadecimal equivalent consists of a percent sign followed by the ASCII hexadecimal value of the character. For example, if the bindname contains commas, replace the commas as shown:
   bindname=cn=John Smith%2c o=Alphalite Airways%2c 
      c=US, password=JSmith3

password
password used to bind to the server.