SMP 3.0 Installation type difference
I know in the new version of SMP, there are two types of installation (Development and Production), when I choose the development type, the wizard install the platform with a embedded database called "Derby" and the intention of this type of environment is development and test purposes. Now the Production database ask to be installed with a custom DB (not derby embedded DB), which must be Oracle or ASE or DB2.
If I planned to have a two tier landscape (DEV&TEST Server and Production), I'm assuming the first server must have installed SMP3.0 as a Development Type and the second one as a Production Type but this scenario leads us to a heterogeneous landscape, with difference on the DB level for both environments.
Now I want to know what is the best practice to install two-tier landscape. Is a good practice install the environments with different type of DB: One Development type (with the derby database) and one Production Type (with the database of my choice)? Should I install both systems as Production type in order to have a homogeneous landscape, even if the purpose of one of them is development and testing? Why now this difference exist, because with SMP 2.x the installation was pretty much the same for production and development environment, the only difference was the license file?
Søren Hansen replied
I am not an SAP employee and don't know best practice, but here is my recommendation.
If you go for a 2-tier landscape (Dev/Test and Production), I would definitely go for Production type in both installations.
Due to the difference in the DB layer, you will want to test your setup on Dev/Test with an architecture as close as possible to production.
You can easily install Development instances on local PC's. Here you would install with the local Derby database.