Difference between revisions of "Collaborative Development Configurations"
imported>Aeric |
imported>Aeric |
||
| (5 intermediate revisions by the same user not shown) | |||
| Line 4: | Line 4: | ||
__TOC__ | __TOC__ | ||
==Develop on Separate Platforms== | ==Develop on Separate Platforms== | ||
Service providers with appropriate licenses can set up the [[Installable Version]] of the platform | 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. | ||
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|Instance Configuration]] | :''Learn more:'' [[Service Provider Settings#Instance Configuration|Instance Configuration]] | ||
--> | |||
==Package Sharing== | |||
Service providers with appropriate licenses can set up the [[Installable Version]] of the platform on multiple, independent systems. Application packages can then be passed around among development, testing, and production instances. (A package is a zip file that contains XML. Installing a package copies its contents into the current platform instance.) | |||
:''Learn more:'' [[Packages]] | |||
==Develop in the Cloud== | ==Develop in the Cloud== | ||
Tenants are created, and their IDs listed in the Tenant Configuration. Those tenancies then become [[Development Tenancy|Development Tenancies]]. With that architecture, collaboration is achieved by publishing and subscribing to packages. | |||
Tenants are created, and their IDs listed in the | |||
Those tenancies then become [[Development Tenancy|Development Tenancies]]. With that architecture, collaboration is achieved by publishing and subscribing to packages. | |||
:''Learn more:'' | :''Learn more:'' | ||
:* [[Service Provider Settings#Tenant Configuration]] | :* [[Service Provider Settings#Tenant Configuration|Tenant Configuration]] | ||
:* Read the [{{DOCHOST}}/whitepapers/LJ%20Collaborative%20Development | :* Read the [{{DOCHOST}}/whitepapers/LJ%20Collaborative%20Development.pdf Collaborative Development] whitepaper. | ||
<noinclude> | <noinclude> | ||
[[Category: | [[Category:Installation]] | ||
</noinclude> | </noinclude> | ||
Latest revision as of 23:15, 2 August 2013
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
Package Sharing
Service providers with appropriate licenses can set up the Installable Version of the platform on multiple, independent systems. Application packages can then be passed around among development, testing, and production instances. (A package is a zip file that contains XML. Installing a package copies its contents into the current platform instance.)
- Learn more: Packages
Develop in the Cloud
Tenants are created, and their IDs listed in the Tenant Configuration. Those tenancies then become Development Tenancies. With that architecture, collaboration is achieved by publishing and subscribing to packages.
- Learn more:
- Tenant Configuration
- Read the Collaborative Development whitepaper.