Try OpenEdge Now
skip to main content
Managing ABL Applications
Deployment Considerations : Deployment Topics and Tasks : Encrypting source code procedures : Preparing to use XCODE
Preparing to use XCODE
Before running XCODE, create a directory structure exactly parallel to your source directory structure, then move to the root of the original source directory structure. Supply the root of the new structure as directory, and then supply the pathnames, relative to the current directory, of the files to be encrypted as files. The relative path names are appended to directory. Because XCODE does not create new directories, any directories implied by the directory or files arguments must be created before running XCODE. Encrypted files have the same names as the original source files.You must encrypt both your procedure and include files in order for your encrypted procedures to run.
The dash (-) option tells XCODE to take filenames from the standard input. On UNIX, this allows you pipe output from an ls, cat, or find command to XCODE.
The following shows how you can use XCODE on UNIX. Suppose you have just finished developing and testing the procedures in /usr/test and its four subdirectories and you want to encrypt them for shipment to users.
To encrypt procedures for shipment to users:
1. Create a directory structure parallel to /usr/test, as shown:
cd /usr/test
mkdir /usr/testx
mkdir /usr/testx/ar
mkdir /usr/testx/fm
mkdir /usr/testx/inv
mkdir /usr/testx/oeFk
2. Move to the original development root in preparation for encryption, as shown:
cd /usr/test
3. Encrypt your procedures, as shown:
xcode -k mykey -d usr/testx *.p ar/*.p fm/*.p inv/*.p oe/*.p
Encrypted versions of the source procedures in /usr/test and its subdirectories now reside, with the same names, in /usr/testx and its subdirectories.
Note: You must also encrypt include (.i) files.