on 05-04-2015 4:06 PM
Hello,
in a customer landscape there are two hosts. One SAP NetWeaver application server and one Oracle database server. The requirements are that all Oracle database components should be on one instance at the database server and that all SAP components should be on the application server only.
That means that the database instance with the SAP NetWeaver schema should be also include the SAP ME WIP, INT and ODS schema.
My question is: will it be possible, that the SAP supporting that development scenario in such a landscape?
According to the SAP Manufacturing Execution 15.0 System Landscape Recommendations on shared server, WIP and ODS should be installed in separate database instances. But the scenario for development environment is not fully clear at this point.
Attached you can find a little sketch for a better understanding of this issue.
kind regards
Matthias
Hello Matthias,
Netweaver instance with Netweaver database should be installed locally on developer's PC, it is required for fast deployment of build results, but WIP/ODS/SAPMEINT databases can be hosted on separate server remotely and all developers can share the same database instance , just create own Site to work with SAP ME.
Regards,
Oksana
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Oksana,
thank you for your reply, but this doesn’t answer my entire issue. The Question is about the SAP Support for such an environment. According to the attached Warning Message, the SAP does not support a scenario, where ODS and WIP Databases are located on the same instances. In my scenario there is also the NetWeaver Database on the same instance. But I wanted to know, will the SAP supporting such a developer environment, or should the support just reject a request according to this development environment? In this case, the customer has to create more instances for the development system in their landscape.
kind regards
Matthias
Hi Matthias,
1. Such development environment will be supported unless the root cause of an issue eventually appears to be about such configuration of databases. For example, performance issues.
2. For sure, such configuration will never be supported for live production environment.
Regards,
Sergiy
User | Count |
---|---|
95 | |
11 | |
11 | |
6 | |
6 | |
4 | |
4 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.