OD filters

I have inclusion filters defined to deploy (.htm,.pdf) files in OpenDeploy. so only these files will be deployed to the target server.
What if I create a executable file and rename it with .pdf extension?

As per documentations it will deploy? right.

Is there any way to validate, if the file is a pdf file or an exe file and then deploy it to PROD?

Thanks for your support

-----------------------
TS 6.5, OD 6.0.1

Find more posts tagged with

Comments

Adam Stoller

I have inclusion filters defined to deploy (.htm,.pdf) files in OpenDeploy. so only these files will be deployed to the target server.
What if I create a executable file and rename it with .pdf extension?

As per documentations it will deploy? right.

Is there any way to validate, if the file is a pdf file or an exe file and then deploy it to PROD?

Thanks for your support

-----------------------
TS 6.5, OD 6.0.1

You could possibly run a pre-deployment DNR script that somehow validates the files before sending them along and if they aren't found to be valid, prints out the XML snippet that will cause OD to consider it a failure.

cute_guy

Ghoti,

Thanks for the reply.

Is there any utility available with Interwoven/ any other to validate the file is a exe or not.

Ambuj

Ghoti,

Thanks for the reply.

Is there any utility available with Interwoven/ any other to validate the file is a exe or not.

I would suggest you to check with Interwoven Support if they have any utility available for this?

Adam Stoller

Ghoti,

Thanks for the reply.

Is there any utility available with Interwoven/ any other to validate the file is a exe or not.

If you're using Perl you should be able to use the -B directive to verify if a file is binary - e.g.:

if (-B $file){
    # file is binary
}
else {
    # file is not binary
}

- and this should work on both Windows and Unix - however, you will find that PDFs are binary and thus this would not satisfy your original request.

For that, if you are on Unix (or have Unix utilities for Windows) you could use the file command:

(FishTank) DOCS > file *
HC1_5.doc:                Microsoft Office Document
HC1_5.pdf:                PDF document, version 1.3
HC1_5test.pdf:            PDF document, version 1.3
HC3-2.xls:                Microsoft Office Document
HCdoc.txt:                UTF-8 Unicode English text, with very long lines
HealthCheck_2.doc:        Microsoft Office Document
HealthCheck_Spec.doc:     Microsoft Office Document
HealthCheck_Spec.pdf:     PDF document, version 1.3
HealthCheck_Spec_bak.doc: Microsoft Office Document
JAD.ppt:                  Microsoft Office Document
TARS.xls:                 Microsoft Office Document
images:                   directory
olb_wfts.graffle:         directory
olb_wfts.pdf:             PDF document, version 1.3

Migrateduser

Ghoti,

Thanks for the reply.

Is there any utility available with Interwoven/ any other to validate the file is a exe or not.

Not that I'm aware of, however, if you are only looking for DOS/Windows type executables, you should be able to write a small 'C' program that can check for you.

If I remember my x86 assembler class back from college correctly, the first two bytes of all EXE files are marker or "Magic" bytes to mark the file as an EXE type regardless of the extension. If my memory is really good, the value of those bytes for an EXE file are ASCII "MZ".

Thanks,
Mike