Do I need a Server License?

[christophhasler]

Hallo

I'm planing to create a component that will print VPE-Documents triggered from a little (self made) engine, that works as scheduled agent.
This engine will run on a Windows 2003 or Windows 2008 Server, maybe as Windows Service, WCF Service or Enterprise Service.

My question:
It's not provided to start the printing from client-side, only from scheduled service on one of the mentioned server. What kind of license i need (server-license or not)? And what is the price for it? How is then license-model (open, each server, each processor, each customer...?)

Thanks for any feedback.
Chris H.

[IDEAL Software Support]

We dropped server licenses with VPE v4.0 R2 in spring 2008. Server Licenses are no longer required for the Standard, Enhanced and Professional Editions, if you are using VPE v4.0 R2 or higher.

[christophhasler]

Thanks for your answer.

Just one more question:
My customer, who will be the owner of the planged component, has a VPE v4.0 license (but not a server license, i think a developer & runtime license).

What is the possiblitity and price to run VPE on this runtime environment?

Thanks for your answer
Chris H.

[IDEAL Software Support]

The SDK license belongs to the customer and it can not be transferred. If you wish to develop software with VPE v4.0, you need you own license.

[christophhasler]

Ok i see, i will need my own license to develop.

But, what shuld the customer do with his v4.0 license to run printing as mentioned? Can he buy a standalone runtime version or...? And what is the price?

What would be the licence scenary, when the customer develops his own component him self?

Thanks for your answer(s)
Chris H.

[IDEAL Software Support]

Runtime Licenses are not required (except for dycodoc and for VPE Interactive Edition). If you acquire an SDK (Software Development Kit) license, you may ship your created application without purchasing runtime licenses. For details, please see the licensing terms at http://idealsoftware.com/ev_order.php.