Difference between revisions of "Collaborative Development Configurations"
From AgileApps Support Wiki
imported>Aeric |
imported>Aeric |
||
| Line 1: | Line 1: | ||
Any tenant can develop new applications and customize existing ones. | Any tenant can develop new applications and customize existing ones. | ||
[[Service Provider]]s have additional capabilities, designed to allow for collaborative development, testing, and production deployment in the cloud | [[Service Provider]]s have additional capabilities, designed to allow for collaborative development, testing, and production deployment in the cloud | ||
<!--Deprecated | |||
__TOC__ | |||
==Develop on Separate Platforms== | |||
Service providers with appropriate licenses can set up the [[Installable Version]] of the platform | |||
on multiple, independent systems. Those systems can then be configured as development, testing, or | |||
production instances. With that architecture, collaboration is achieved by sharing the [[Metadata Repository]] using a Version Control System like Subversion. | |||
:''Learn more:'' [[Service Provider Settings#Instance Configuration]] | |||
==Develop in the Cloud== | |||
--> | |||
Tenants are created, and their IDs listed in the [[Service Provider Settings#Tenant Configuration]]. | Tenants are created, and their IDs listed in the [[Service Provider Settings#Tenant Configuration]]. | ||
Those tenancies then become [[Development Tenancy|Development Tenancies]]. With that architecture, collaboration is achieved by publishing and subscribing to packages. | Those tenancies then become [[Development Tenancy|Development Tenancies]]. With that architecture, collaboration is achieved by publishing and subscribing to packages. | ||
:''Learn more:'' [[Service Provider Settings#Tenant Configuration]] | :''Learn more:'' | ||
:* [[Service Provider Settings#Tenant Configuration]] | |||
:* Read the [{{DOCHOST}}/whitepapers/LJ%20Collaborative%20Development%20Models.pdf Collaborative Development Models] whitepaper. | :* Read the [{{DOCHOST}}/whitepapers/LJ%20Collaborative%20Development%20Models.pdf Collaborative Development Models] whitepaper. | ||
<noinclude> | <noinclude> | ||
Revision as of 21:27, 24 July 2012
Any tenant can develop new applications and customize existing ones. Service Providers have additional capabilities, designed to allow for collaborative development, testing, and production deployment in the cloud Tenants are created, and their IDs listed in the Service Provider Settings#Tenant Configuration. Those tenancies then become Development Tenancies. With that architecture, collaboration is achieved by publishing and subscribing to packages.
- Learn more:
- Service Provider Settings#Tenant Configuration
- Read the Collaborative Development Models whitepaper.