IBM Tivoli Web Access for Information Management

70 IBM Tivoli Web Access for Information Management

As you can see, it is easy to review your HTML. You can make any adjustments to the data

view and generate the HTML again until it meets your needs.

29

The manual method should

be used until you have decided what layouts you want included in the generated HTML.

Then, you can use the Auto Build process. Since you can have more than one Auto Build file

by specifying a different file name and path on the directive in the BLQPARMS configuration

file, you may find it easier to have an Auto Build file just for the record type with which you are

currently working. If you change the BLQPARMS configuration file, be sure to reload it using

the Web Administration page.

In this example, if we go through the HTML generate process again for update, display, and

inquiry and add to the Auto Build file each time, it will then contain all parameters necessary

to rebuild the HTML for the BLQVPROB data view record without having to specify any input

parameters. This is very useful as you make changes to data view record groups, tables, and

tasks and want to rebuild the HTML so that you can see those changes. Building the HTML

for one data view record one mode at a time is not terribly difficult, but if you have to build the

HTML for multiple data view records as Web Access does, that method can get very tedious.

6.2 Auto Build specifics

Web Access ships an Auto Build file called BLQBATCH. It resides in UNIX System Services

in the following:

/usr/lpp/InfoMan/web/samples/BLQBATCH

Do not modify BLQBATCH or allow the HTML generator to modify it. At some point in the

future, you may need to rebuild the HTML that Web Access ships, and BLQBATCH contains

all the parameters necessary to do that. Therefore, it is important not to change it.

Before you add or replace any entries using the HTML generator Auto Build process, you

need to change the following parameter in your BLQPARMS configuration file:

Auto_Build_file /usr/lpp/InfoMan/web/samples/BLQBATCH

To something similar to the following:

Auto_Build_file /usr/lpp/InfoMan/web/samples/MYHTML

You change the Auto_build_file parameter by editing your BLQPARMS configuration file. You

must also reload the configuration file using the Web Administration page so that this change

will take effect. Then when you run the HTML generator and save the settings in the Auto

Build file, they will be saved in this file.

You do not have to create the MYHTML file, since the Auto Build process will create it for you

if it does not exist already. The location of any Auto Build file must be in a directory within

which you have write access.

When you add or replace an entry in the Auto Build file, you will receive a message that your

entry was added or replaced successfully.

If you specify

replace

, and an entry does not exist in the Auto Build file, that entry will be

added.

If you specify

add

, and an entry already exists in the Auto Build file, another entry will be

added. Therefore, you will typically only want to specify replace.

29

Remember that if you use static PIDTs, you must run BLGUT18 before you generate the HTML. So, until you have

ironed out your data views, you may not want to build the static PIDTs.