At this point you might need to choose a strategy for sharing the configuration of your domain, database, and other objects with the rest of your development team.
You may need to account for these two types of configuration, and how you will identify them or keep them separate in your development environment. The two configuration types are:
Configuration of the staging or production servers—including desktops, content management data and structures, entitlements, and other configuration objects. It can also include any database schema definitions that are unique to your project.
Configuration of the development and test servers—including test data and test users, as well as the configurations listed in the previous bullet item.
The main ways to share configuration objects are:
Manually using a set of instructions.
Using scripts such as WLST, DDL, Ant, and so on.
Using JSPs, servlets, and so on
Propagation—moving the database contents of a portal application from one server environment to another.
Each way has its advantages and drawbacks. Most likely you will use a mixture of these techniques.
Related Information
The following topics provide more detail for sharing configuration objects:
