So you are ready to build remote files on your UNIX machine using AllFusion Gen r7.x or Gen r8.x, but after accessing the UNIX machine and entering the familiar command 'iefad', nothing happens! Was it typed incorrectly, is it the wrong machine, or is someone playing a cruel joke?
The answer is: None of the above. As some of you may already have discovered either by reading the AllFusion r7 New Features Guide or by trial and error, the iefad within the UNIX environment is gone! In AllFusion Gen r7 and beyond, the iefad is replaced by using the Windows Build Tool and accessing the remote files via a client/server connection or by entering the Build Tool commands from the UNIX command line. Within this document, we will cover building remotes 1) using the Build Tool Client/Server method. This method requires a connection to a running Build Tool Server. 2) using the UNIX command line.
The intent of this document is not to duplicate the Gen Build Tool Guide but to give a more visual detailed description of the steps needed to build applications for UNIX using the Build Tool or the UNIX command line. The guide provides more details on command parameters and profile token specifications.
Build from the Build Tool Client:
Following are the steps to build UNIX modules using the Build Tool Client.
- Generate the remote files targeting a specific database under UNIX. Transfer the remote files to the UNIX machine and place in the desired build location. This can be done using FTP or other file transfer methods. To this point, nothing is different from the build methodology within AllFusion Gen 6.5.
- Start the r7 Build Tool Client. Once open, enter the name of the UNIX server machine in the hosts field which contains the remote files. Once this is entered, a dialog box will display. Enter the port number of the remote Build Tool Server (default is 7776) and a userid and password. This will initiate the client/server connection.
Note: The Build Tool Server is started via a script. The script by default contains the port of 7776. Reference the Gen r7 Build Tool Guide (Chapter 3) for details concerning the contents of this script and how to run this script.
An alternate server may be specified at the time of the build by either running the script with a different port specification or by using the UNIX Build Tool command line to specify a different server. ('bldtool -c SERVER -p xxxx' where xxxx is an alternate port to reference on the connection)
- From the directory tree on the left column of the Build Tool Client, find the location of the remotes that were moved to the UNIX machine. Select the directory containing the remotes and use the large arrow to display them in the right column in preparation for build.
- Select the profile and verify the correct database, userid, password and other tokens are specified for the build process.
- Highlight the remote file(s) and select build to perform the split, build and install of the modules. The build will occur on the server machine specified in the Build Tool Client using the Build Tool Client profile.
Building from the Unix command line:
Following are the steps to build UNIX modules using the UNIX command line.
1. Generate the remote files targeting a specific database under UNIX. Transfer the remote files to the UNIX machine and place in the desired build location. This can be done using FTP or other file transfer methods. To this point, nothing is different from the build methodology used within AllFusion Gen 6.5.
2. Access the UNIX machine. Verify the environment variables AEPATH, AEHOME, PATH, LIBPATH and other pertinent variables similar to prior versions of AllFusion Gen are correct.
3. If a database is used and/or other tokens such as library or external file locations are needed, set up a user profile. The user profile(s) are placed in the $HOME location as that is where the build process looks for them. The profile is of the format 'user.<profile_name>.profile'. The profile_name portion can be any meaningful name and is case sensitive when referenced from the Build Tool commands. Reference Appendix B of the Build Tool Guide for listing of available tokens used within the profile. Here is an example of a profiles content:
Unixbox1% cat user.SAMPLE1.profile
4 To initiate the build process, enter the command 'bldtool -c COMMAND'. You will then be prompted to enter a command. You will see the following displayed from the command line: Note: This command can be combined with the command sequence in step 6 (below) or separated out as done here.
Unixbox1% bldtool -c COMMAND
+ [ -c = ]
+ [ -c != -c ]
+ [ -c = -c ]
+ [ COMMAND = command -o COMMAND = COMMAND ]
+ [ != ]
+ /home/it/gen70/runtime/bt/jre/bin/java -classpath /home/it/gen70
dtool.Bldtool -c command
5. Enter a command (BUILD, SPLIT , CLEAN or STATUS) following the necessary parameters outlined in Chapter 4 of the r7 Build Tool Guide. For the purpose of this document, we will perform a BUILD. If no file is specified, all .rmt's will be split (if necessary) and all .icm's will be built and installed. The order of the build is DDL, Cascade Library, Operations Library, and Load Modules.
In this example, we will BUILD all .rmt's located in a specific directory for a specific profile. The command used would look like this:
BUILD ?l /home/USER07/sample/ -f SAMPLE1. Again, the profile name is case sensitive.
6. The application will build in the designated location and reference the profile specified from the $HOME location which contains tokens for database and other file references. The results will be similar to this:
BUILD -l /home/USER07/sample/ -f SAMPLE1
/home/USER07/sample/ORCDB Splitting ORCDB.rmt
/home/USER07/sample/ORCDB Split Complete ORCDB.rmt
/home/USER07/sample/ORCDB Building ORCDB.icm
chmod +x /home/USER07/sample/ORCDB.scrpt
/home/USER07/sample/ORCDB Build-OK -ORCDB.icm
/home/USER07/sample/CASCADE Splitting CASCADE.rmt
/home/USER07/sample/CASCADE Split Complete CASCADE.rmt
/home/USER07/sample/CASCADE Building CASCADE.icm
chmod +x /home/USER07/sample/CASCADE.scrpt
/home/USER07/sample/CASCADE Build-OK CASCADE.icm
/home/USER07/sample/LOADMOD1 Splitting LOADMOD1.rmt
/home/USER07/sample/LOADMOD1 Split Complete LOADMOD1.rmt
/home/USER07/sample/LOADMOD1 Building LOADMOD1.icm
chmod +x /home/USER07/sample/LOADMOD1.scrpt
/home/USER07/sample/LOADMOD1 Build-OK LOADMOD1.icm