Architecture Options - Deployment ChoicesRecently the CIO at a company considering JMP Clinical asked us for an Architectural diagram to share with his infrastructure group. Stan kindly provided and threw in JMP and JMP Pro for good measure. I thought these might be useful to others.
Some possible desktop JMP Clinical deployment architecture optionsSome possible desktop JMP Clinical deployment architecture options
Some possible desktop JMP and JMP Pro deployment architecturesSome possible desktop JMP and JMP Pro deployment architectures
Re: Architecture Options - Deployment Choices@flo_kussener is correct. Talk with your management and sales management about how to proceed.
Re: Architecture Options - Deployment ChoicesHi Hyde,
From my past experiences, a virtual presentation of JMP is another product tahn desktop, so they need to purchase it again.
Check with your Sales team.
Florence
Re: Architecture Options - Deployment ChoicesIf an existing customer has JMP deployed on user laptops then wants to convert users to a VM setup, what is the process for this? Do they just need a signed agreement (presentation virtualization) or do they also need to repurchase JMP (pay first year fees)? I have a customer asking this exact question.
Re: Architecture Options - Deployment ChoicesThose diagrams are good, but the short answer to anyone who asks about the architecture for JMP, JMP Pro, JMP Clinical should be, "JMP (Pro, Clinical) is a desktop application." None of these applications is cloud-based, or multi-machine in any way. No architecture diagram is needed.
If they would like to deploy it into anything other than a desktop/laptop environment they can do so in the same way they would with any other desktop app. Of course they'll need a commensurate license (i.e., a presentation virtualization license).
