![]() ![]() ![]() This log will let you know whether or not the process submission was successful. I also added an output log to the example, myproc.log. The file myproc.txt is created by onTheFly and contains the commands provided to Connect:Direct. NOTE: See the section Using the LCU at the end of this article for more explanation on the LCU and the CDDEF.bin. The advantage of using the cddef.bin rather than relying on the direct command without any parameters is that it is not dependent on the user logged into Windows. This file is produced by the lcu.bat file in the Connect:Direct Common Utilities directory. Direct is the command that opens the CLI, in this case I am using the cddef.bin file to provide the connection information to attach to the Connect:Direct node acting as the pnode for the process. #Batch script check file version download#I also used only file names for source and destination allowing for the use of the default upload and download directories defined in Connect:Direct. This is the line that calls the CLI to submit the process:įor simplicity I created this batch file in Connect:Direct’s Common Utilities directory to avoid the necessity of fully qualifying the path to the direct command. As you can see this example does check the syntax and if three inputs are not provided it displays the required syntax. It requires the snode name, the source file name and the destination file name. In this example onThrFly requires three inputs. This is the file that will serve as the input to Connect:Direct’s Command Line Interface (CLI). The batch file onTheFly echoes the Connect:Direct commands into the file I called myproc.txt. If "%2"= "" goto mysyntax else goto mysyntax3Įcho = If "%1"= "" goto mysyntax else goto mysyntax2 The next step is to copy the file into a text editor, I used Notepad. $SNODE$="CDNODE.CD460" $SNODE_OS$="Windows"įILE="C:\Program Files (x86)\Sterling Commerce\Connect Direct v4.6.00\Server\Process\Sample.html"įILE="C:\Program Files (x86)\Sterling Commerce\Connect Direct v4.6.00\Server\Process\Verify.html" This gives an easy starting point to create a process using a batch file since the Requester has already checked the syntax. For purposes of this article I used the Requester. The first thing you need to do is to create a process, either using the Requester, CDBrowser User Interface or a text editor. The question sometimes arises “Can I create and run a Connect:Direct process from a batch file?” ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |