Code

Re: How to Deploy InfoPath in the Remote Machine

vasanthaprabu — Mon, 03 Apr 2006 09:05:04 GMT

Hello Friends,

Thank you for your all replies.. I think I have got enough Knowledge to deploy an InfoPath.
But the installation of InfoPath to every machine.... Its something looks bad.. Its Okay its not a big deal.

Once again Thanks to everybody. I have deployed that successfully.

Regards,
Vasanth.

Re: How to Deploy InfoPath in the Remote Machine

Abhishek — Mon, 03 Apr 2006 05:12:58 GMT

Hi,
yup,If u r gonna access the form from 100 systems,then u have to install the form in those 100 systems.

An easier alternative to this is to use digital signatures which ofcourse u have to spend.
regards,
Abhishek

Re: How to Deploy InfoPath in the Remote Machine

vasanthaprabu — Fri, 31 Mar 2006 04:53:06 GMT

HI Abhishek,

Thanks for your reply...
I have followed all the step and is working fine...

But...See if I am going to access the Form in 100 systems ( just imagine).
For that 100 System I have to install the Form and then access the form from the SharePoint Library...
Its something painful job to the user to install the Form in your system before use.. isn't it?..

Regards,
vasanth.

Re: How to Deploy InfoPath in the Remote Machine

Abhishek — Fri, 31 Mar 2006 04:34:45 GMT

Hi Vasant,
For Ur first question:Yes,You have to install the form using the .msi file in all the systems from where u need to access the form

For ur 2nd question i.e "So I have to mention the server path of the msi file also is it?.." :I dint understand this one.
So just follow the following steps to successfully access the forms from different machines.

1)Go to Tools-->Form Options.In the Security Tab,Select Full Trust.
2)Create the msi file
3)First install the form in ur machine.
4)Go to the folder where the form is located(By default it is C:\Program Files\InfoPath Form Templates)
5)Double click the .xsn to open the form.
6)Do not fill the form.Just save it as say form.xml.
7)Place the form.xml in the forms folder of ur form library in SharePoint.
8)Send the msi file to all the systems that need to access the form.Install the form in these systems.

Thats it.Now the form can be accessed from other machines.

Regards,
Abhishek

Re: How to Deploy InfoPath in the Remote Machine

vasanthaprabu — Thu, 30 Mar 2006 15:52:01 GMT

HI,

I followed each steps in the link... but finally I concluded that..

if I publish it into the SharePoint Library..wherever the user way to fillout the form using different machine..there are also the form template needs to be install and register there right?..

So I have to mention the server path of the msi file also is it?..

Anyway other way is there?...

Regards,
Vasanth.

Re: How to Deploy InfoPath in the Remote Machine

Abhishek — Thu, 30 Mar 2006 08:07:59 GMT

Oooops sorry AndersR :)))
dint notice that.

Regards,
Abhishek.

Re: How to Deploy InfoPath in the Remote Machine

AndersR — Thu, 30 Mar 2006 06:36:39 GMT

Abhishek: that link sure does look like the link i posted just above ;-)

Vasanth: did you follow the description in the article step by step?

Follow the one called "Deploying a Fully Trusted, Registered Form to a Form Library" and you should have that form running from sharepoint in no time :-)

hth

Re: How to Deploy InfoPath in the Remote Machine

Abhishek — Wed, 29 Mar 2006 06:37:44 GMT

Hi Vasant,

To deploy a fully trusted registered form in SharePoint, u cannot directly publish it.
There is a work around though as described in the following link.
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/ipsdk/html/ipsdkDeployURNFormToSharePoint_HV01086376.asp

Check it out.
Once u get the hang of it, its quite easy.
regards,
Abhishek

Re: How to Deploy InfoPath in the Remote Machine

vasanthaprabu — Wed, 29 Mar 2006 05:57:05 GMT

Hi AndersR,

I am still confuse that I have already remove the publish URL from the Manifest file and I change the urn to my own and same thing I did in the template.xml and then compress it to xsn.

After that I have register the xsn file using js file in the computer.

Any steps needs more to publish it in the SharePoint library?

Regards,
Vasanth.

Re: How to Deploy InfoPath in the Remote Machine

AndersR — Tue, 28 Mar 2006 20:37:38 GMT

Hi Vasanth

when you publish to a sharepoint portal, the url in the manifest is the unique identifier, just as is the case when you set your own namespace/urn.

when you publish a trusted / signed form to a sharepoint form library you therefore need to replace the default template.xml for the library with your own.

theres a description for this on MSDN:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/ipsdk/html/ipsdkDeployURNFormToSharePoint_HV01086376.asp?frame=true

hth

Re: How to Deploy InfoPath in the Remote Machine

vasanthaprabu — Tue, 28 Mar 2006 12:44:53 GMT

HI,

I have register the Infopath in the other machine using js file provided by MicroSoft( if you dont have .NET for creating MSI file) and orking fine when run form.

But if publish it into the SharePoint Portal I get the same not trusted fully error and register again.

Can you clear me out from this problem.

Regards,
Vasanth.

Re: How to Deploy InfoPath in the Remote Machine

vasanthaprabu — Tue, 28 Mar 2006 03:37:28 GMT

Hi,
Thank for your reply,
can you tell me How can I mention all the files while using Makecab.exe in the command prompt. becoz I have only mention one file at a time... is there any other key word........

Regards,
Vasanth.

Re: How to Deploy InfoPath in the Remote Machine

Matt Faus — Tue, 28 Mar 2006 03:25:34 GMT

I think if you use makecab (installed by default on most Windows platforms) you can propery change the extension to .xsn directly and it will work.

Re: How to Deploy InfoPath in the Remote Machine

vasanthaprabu — Tue, 28 Mar 2006 02:59:05 GMT

Hi AndersR,

the problem is, the VS.NET Cab Project add OSD file while compress the file... So if I change the cab to xsn file..i got that error.

I am trying in different way to compress the file..

regards,
vasanth.

Re: How to Deploy InfoPath in the Remote Machine

AndersR — Mon, 27 Mar 2006 19:30:06 GMT

Hmm the error doesnt ring any bells, but it sounds like you have accidentially corrupted your manifest or template file.

Try and grab an older build (you *are* using source safe or similar right?;-) from before you did the change and see it this one can be converted to an MSI file.