job specification file in work flow

I was going thr' workflow pdf and when I came across this job specifiction file, I got confused.

As per pdf I understand that Job specification file is created automatically by the instantiator cgi, right ? There was job specification DTD. Why do we need this DTD, if we are not going to create this xml file ? If its an internal process, what is the use of this file for a developer ? We just create .wft file and place it in wft folder and modify available_templates.cfg file, right ?
Does a developer do anything more than this ?

Pls explain.

Thanks

Find more posts tagged with

Comments

Adam Stoller

I was going thr' workflow pdf and when I came across this job specifiction file, I got confused.

As per pdf I understand that Job specification file is created automatically by the instantiator cgi, right ? There was job specification DTD. Why do we need this DTD, if we are not going to create this xml file ? If its an internal process, what is the use of this file for a developer ? We just create .wft file and place it in wft folder and modify available_templates.cfg file, right ?
Does a developer do anything more than this ?

Pls explain.

Thanks

The job specification file has a DTD because it is XML and must conform to a DTD to be valid.

The job specifications can be created by developers if so desired - but it will have no prompts for additional information (e.g.: no TAG_info() sections, no embedded Perl code, etc. - it is for use in either debugging an existing workflow template (or model I suppose) or for kicking off fully automated workflow processes that do not require any prompts.

Do you need to work directly with job specification files - no.
Should you be able to read and understand job specification files - if you're going to do workflow development, I'd say - yes.

spayal

Thanks for reply. I got the answers but I have some questions.

If I create .wft file without any directives, then why do I need job specification file. Secondly, if job specification file is created automatically then why create it in any case ?

Thanks

nipper

Thanks for reply. I got the answers but I have some questions.

If I create .wft file without any directives, then why do I need job specification file. Secondly, if job specification file is created automatically then why create it in any case ?

Thanks

You seldom need to worry about a job spec. The wft will create the job spec in most cases. Very few people on this list have changed job specs. However there are times when some will do that.

I would not worry about it unless you fall into that latter category. Then start looking at them.

Andy

kaalraa

Thanks for reply. I got the answers but I have some questions.

If I create .wft file without any directives, then why do I need job specification file. Secondly, if job specification file is created automatically then why create it in any case ?

Thanks

If you are a workflow developer and sometimes, you need to change any property of a instantiated flow (job spec)... in that case you might need to know about structure and usage of a job spec file.

Adam Stoller

If you are a workflow developer and sometimes, you need to change any property of a instantiated flow (job spec)... in that case you might need to know about structure and usage of a job spec file.

Please explain how you would use a job specification file to "change any property of an instantiated flow"