BOE 5 TIER landscape

Hi guys
I need some expert opinions.
We have 5 Tiers landscape currently in BW and ECC (2dev, 2QA, and 1 prod)
dev2, and qa2 are used for system upgrades and applying patches.
our plan is to use BusinessObjects 4 as a reporting platform for BW and ECC reports, in doing so do we need to keep the same landscape for BOE ?
I am more using to working with 3 tier landscape in BOE (dev, qa, prod)
Can someone please suggest if we should keep the 5 tier landscape for BO 4, or we should go with standard 3 tier landscape.
Thanks.

Dennis,
I also have questionfor the DR design. Here is my thought, can you comment out?
we want to setup a disaster recovery site for BOE and all ETL.
In production environment I have BOE/Data server installed in one box, MS SQL installed on seperate box.
The plan is to use Doubletake softaware to replicate all the data to corresponding server in DR, like BOE/DS and SQL database.
Per test, the SQL database gets replicated really good through Doubletake, my doubt is how the BOE/DS (job server) is going to work in DR site if production goes down.
Let me know your comments and thanks for the time.

Similar Messages

How to setup Charms in a 2 tier landscape ?

Hi All,
We have a two tier landscape i.e only having development and production system so how to setup STMS and all other settings in this type of scenario.
Can we use Virtual system in STMS as a Quality system ? If yes then please guide us and tell me how to proceed as if we dont know how to add virtual system in SMSY in solman. Please provide us with a clear picture and give us detail documentation if possible.

Hi All,
Please tell me as per the SAP standard recommendation is it necessary to have a cycle like DEV->QUAL-PROD for Charms as we are not having any Quality system or Client here in our landscape.
Please suggest a way how to proceed in this case. Please help me out.

SAP CE7.1 3-tier landscape

I have a customer who wants to build a CE7.1 landscape. He is requesting a 3-tier landscape, but to be honest I don't think that this is required and I have even issues to understand how you will keep the consistency in your development setup. I almost assume that this is related to the previous NWDS (Developer Studio) setup which was installed on the local pc. Does somebody have a reference document or link to the preferred landscape setup for a NW CE7.1 environment or can share his/her opinion ?

HI Sreedhar.
thank you for your fast reply!
1.
You said:
copy entire system so that you get everything including pre-requisites
Is this a BPC functionality or which tool can do this?
2. Ok, so I can "transport" thinks, but only complete AppSets? What about reports and input schedules?
Rgds,
Christian

Netweaver gateway in three tier landscape

Hi experts,
Can You please explain what are the best practices when using SAP Netweaver gateway central HUB deployment in three tier landscape. Is it sufficient/possible to use one gateway system for all (DEV, QAS PRD) systems, or there is a must that every backend system has its own dedicated gateway system?
Thank You and best regards,
Igor

Hi Igor,
I would not support having one gateway system for all three (not even two) landscapes.
For each landscape, it is a standard to have their of set of systems. Rather, any kind of communication between cross landscape systems is usually strictly prohibited.
Still, let us think on what might be the consequences.
Each service will have three system aliases one each for each of Dev, QA and Prod.
What if a production service by mistake starts pointing to a Dev's system alias and starts showing products from Dev landscape? disastrous for the company!!!
If you are worried about having to maintain one extra system for Gateway you can consider 'Embedded Deployment', which I have seen many clients have adopted successfully. (be aware of limitations though)
regards
Krishna

Has anyone implemented ChaRM in a 4-tier or 5-tier landscape?

Iu2019ve setup ChaRM with a 3-tier landscape DV1-QA1-PRD and everything works as advertised. I used the transport route, DV1/120 -c- /QA1/ (clients 149/150) -QA1 -d- PRD/150. Where -c- is a consolidation route and -d- is a delivery route.
Now I need to do a proof of concept to see if I can get CHaRM to work with our current landscape. We have a dual development path and need to make sure we sync our DEV and QA systems. The lanscape Iu2019m trying to use is DV1-QA1-PRD-DV2. The transport route Iu2019m trying is DV1/120 -c- /QA1/ (clients 149/150) -QA1 -c- PRD/150 -d- DV2/120. Iu2019ve tried various combinations and the only way I can get it to work is DV1/120 -c- /QA1/ (clients 149/150) -QA1 -d- PRD/150 -d- DV2/120. When I release and import into PRD it goes to both PRD and DV2. While this gets the transport to my support dev box I need to have another step in the workflow. What Iu2019m looking for is the workflow to act like dev-qa-qa-prd.
Has anyone setup a 4-tier or 5-tier landscape with release and import steps between each system? If so what did you use for your transport route and were they other config changes needed after the route?
Thanks for your time.
Jeff

Hi Jeff
Have a look at these
http://help.sap.com/saphelp_smehp1/helpdata/en/a3/0aae435a1342e8a56998d83a797161/content.htm
/people/dolores.correa/blog/2009/08/27/change-request-management-scenario-retrofit-functionality
Hope it helps
Santosh

ChaRM for 2 tier landscape

Hi
I need to setup ChaRM for a 2 tier landscape. I know how to do the technical side however i need some clarity in regards to the process flow that will be used. Does someone have a diagram or document detailing this process. Basically i just need to know at what point testing happens and when does the transport get triggered to move from DEV to PRD

Hi
Standard charms is for 3 tier so no diagram
for testing it happens in dev only so in short when move the changes to qa it will remain in dev system for ur case
only when request is released ................it goes to prd
regards
Prakhar

Standard process practice to apply Support pack in 3 tier Landscape system.

Dear All,
I know how to apply the support pack in SAP system, but I am interesting to know the standard process practice to apply Support pack in 3 tier Landscape system. For e.g we have development server -
 QA -
 PRD
What is the process to apply support pack in above mention landscape system.
I would like to request all expert help me understand this.
Thanks in advance
Dinesh M
Edited by: dineshdm marotkar on May 13, 2008 12:28 PM

Hi,
If you have only one common transport directory then you have to uncar the files only once.
Uncar should be done once per transport directory.
Before performing the import of support packages if you have done any changes to standard sap programsthen you have to lock them in the reqests and while importing the support packages u have to perofrm spau and spdd adjustments any ways sap will allow you this prior to abap screen generation.
First you have apply the patches on test and then qa and then prd. Make sure you have recent spam/saint update installed.
Also perofrm a kernal upgrade after updating the spam/saint.
Perform a full and tlog backup before importing support pacakges.Because sap does not support uninstalling of support packages.
Regards,
Vamshi.

Default schema names in multi-tier landscape

Hi folks,
We have an interesting problem due to having different named default schemas in each of our 3 hana systems. For example lets say these are our default schemas in our development, staging, and production HANA systems;
DEV_SCHEMA
QA_SCHEMA
PROD_SCHEMA
Each of these replicating data from their corresponding SAP source systems.
Now, we have a view that is developed on DEV hana box and uses DEV_SCHEMA. When this view content is imported to QA or PROD we handle easily with schema mapping. All is well and good although we are not really a fan of this different naming and us developers did not choose this naming (self defense plea here for us brilliant developers whom never make such mistakes... PS: HI LARS! - Go Germany!)
Now we are setting up a connection from BW into HANA using system connection and inside this is a parameter called 'db user'. Although it's called db user it's actually looking for a SCHEMA name. If BW DEV is querying from HANA DEV this schema name would be DEV_SCHEMA. However if BW_QA is querying from HANA_QA then the name would need to be QA_SCHEMA but in our BW landscape we are locked in QA and PROD and normally can not and/or do not want to edit objects in non-native systems. Ideally what we need is our default schemas in HANA to have the same exact name throughout the HANA landscape.
All this said, I can see that it would be great to re-name our entire HANA landscape however that would be a HUGE monumental undertaking as all systems would need to be re-replicated again (at least I think).
Just curious if anybody else has named their schemas differently on each tier? What are most people doing? Naming the default schemas the same consistently or are you using schema mapping?
Thanks,
-Patrick

Hi Luke,
I am new to the project and there seems to be no original version. At some point a bunch of the destination field names were changed on the admin console and errors resulted from it both due to mismatched joins and the use of two word field names. I have documentation of the names for the set of tables in the function area but am having trouble with how everything matches up in the bottom half.. I'll keep working on it
Z

BOE/BW landscape question

HAd a question about managing/configuring BOE in a BW environment.
We are planning to have many non-production systems in our BW landscape. (Dev, Dev+1, Product test, Performance Test, Training..etc).
If we are also including BOE in our environment (Webi, Infoview, etc), do we need a corresponding BOE environment for each BW environment?
We currenrly make all BW changes in our develpment environment and transport thru the landscape to all other environments. Wondering how that works for BO objects , what systems need to be set up, and what is best practice for this and managing changes through the landscape.
Seems that a separate BOE environment for every non-prod BW implies additional cost (hardware and licensing) and we are trying to determine the best scenario.
But also want to maitain the control of versions and changes through the landscape and ability to test them as they progress through.
Thanks.

My recommendation is to have a 1-1 setup.
There are two kinds of connections between BO and SAP.
1) Authentication connections
2) Data connections.
Authentication connections allow your SAP users to use the credentials to log into the BO system. You can indeed create more than one authentication connections within a BOBJ system.
Data connections retrieve data from SAP sources into your BOBJ reports. A single report/dashboard (WebI,CR,XCelsius) can connect to several SAP data sources at once. But you cannot dynamically change the name of the system you are connecting to. At least not by applying generic BOBJ functionality.
SAP Business Objects offers the LifeCycle Manager to help you manage the life cycle of your projects in a multi-leveled environment.
Assuming you are using a single BOBJ installation for multiple SAP systems you have to make sure that the security is well defined in order to separate your development from your production environment. You will probably have to work with separate
folders to host your different environments. In this case you will not be able to use all capabilities of the LCM (like mapping of data connections).
Regards,
Stratos

Best Practice to transport MDM Workflows trough a 3-tier Landscape

Hello Experts,
I wanted to ask you for some Best practices to transport MDM Workflows from D-to Q/P?
Well besides the Archive/Unarchive method because we want to keep the Data of P in the repository
and do not want to import the whole.
Any ideas? Points are for sure!!
Best regards
Carsten

Hi Carsten,
Currently with the MDM 5.5 version the only transport mechanism that will allow you to export your Workflows from the development server to the Production or Quality is the Archieve/Unarchieve method.
but this methods archives the data as well along with the workflow.There is no such method to exort the workflow alone.
But with the onset of the MDM 7.1 there are new transport mechanism included and hopefully they address this issue.
A work around that i can think of at this moment:
- If you have your development server as your Master rep and the Production server as your slave
- Then you can call the workflow from the D to the P.If you do not have any data presntly in the dev.
- and then Normalize the Productions server to make it an individual master rep with its own data.
I am not sure how well this solution will help but just a suggestion....
Hope It Helped
Thanks & Regards
Simona Pinto

IMPORT_OF_COPIES_OK in a 4 System Landscape

Hi folks,
I am working on a 4-tier landscape and using the condition IMPORT_OF_COPIES_OK to check if transports of copies have been imported successfully into QAS.
The landscape looks as follows:
DEV -> QAS -> PPD -> PRD
(TMS is configured in that manner)
I am using a (modified) copy of SDMJ .
In Logical Component:
DEV is defined as D - Source System
QAS is defined as O - Target System
PPD is defined as O - Target System
PRD is defined as P - Production System
In Task List all systems show up, DEV (source), QAS (target) & PPD (target), PRD (production).
The problem is: even the import of transport of copies into QAS is successful, the system reports "not all transport of copies have been imported successfully" when trying to set the status at which the condition is used.
My assumption is that IMPORT_OF_COPIES_OK checks all systems of type "target" and not just the follow up system for DEV. But since I am not an ABAPer I am not really able to have a deeper look into this.
Did anyone come across this problem/phenomenom or does have a solution for it?
Thanks in advance
Regards

Hi,
I am facing the same issue. Did you solve this issue? if so, how?
Best regards,
Pascal

Single-Tier in Dev / Multi-Tier in Prod - BPC5.1 - are there any issues?

Background: We are a new install of SAP BPC 5.1 and initially planned to have both Dev and Prod as a single tier install. In the Blueprint design review, the recommendation was made and accepted to have production as a Multi-Tier landscape. Due to tight timelines, the customer will go-live on the Production Multi-tier landscape and Dev in a Single Tier configuration. As soon as possible, we will move Dev to a Multi-Tier install as well to synchronise Dev to Prod.
Question: Other than being uncommon, is there any know issues with having this current dissimilar landscape?
Edited by: Penelope Thomson on Dec 17, 2007 12:15 PM

There's nothing uncommon about having a development environment that isn't an exact macth to production. Many clients that have large mutli-server configurations don't invest that much money and resources in thier development environment. The downside is that when you do things such as stress testing, user acceptance testing and other configurations in development, you really have to do them again in production if you want a fully tested environement.
Also, if you have different software components (e.g. 64bit OS in production and 32bit in development) you are dealing with different service packs and other components that can have different issues. I've also run into differences in authentication issues between a simple and more complex environment depending on how the components are arranged.
These should all be issues the technical consultant that is doing the server configurations can discuss with you. The bottom line is you'll want to make sure you have the production environment setup with enough time to do a through testing before go-live. As far as moving the application from development to production, going from a single server to mutli-server shouldn't be an issues as long as you're using server mananger to do the backup and restore.

ChaRM - Mainenance Cycle in two system landscape - possible?

Hi Experts,
we are trying to create a maintenace cycle with two systems.
We have a system defined as "Evaluation System" and the second is defined as "Production System".
Generally Question
Is it possible to create a maintenace cycle for a two-system-scenario?
Specific Question - Erorrs/Warnings
While checking the project we got several errors/problems:
1 Differences between BC Set SOLMAN40_CHARM_BASICFUNC_001 and database
2 Differences between BC Set SOLMAN40_SDESK_BASICFUNC_000 and database
3 No consolidation system found for EID-800 (project Z_CRM_T)
4 No track for project Z_CRM_T with log. system EID/800
5 Message from function module /TMWFLOW/CHECK_PRJ_CONS: No export system for CBI-001
CTS
The transport system is configured correct - Check in STMS is OK
Question:
The comparison checks seem to be OK - is it necessary to reactivate the BC Sets?
Kind regards
Tom

Hi,
the system role for your client/systems in the logical component is very important:
- The development system needs to be defined as a Source System.
- If you don't have a QA, leave all target systems empty. If there are one or more consolidation/integration/regression systems, assign them to system role Target System.
- Your production system uses system role Production System.
The defined Development client needs a client dependent (TMS parameter CTC=1) consolidation track to the QA, or in a 2 Tier landscape to the production system. In a 3 Tier landscape you need a delivery track from QAS client to your production client. But as you wrote, TMS has been set up already. I just would like to mention all steps....
Check that all RFC connections have been set up correctly. Especially the Trusted RFC. Don't forget the Trusted RFC to client 000 ot the TMs domain controller.
In tab Systems ( transaction code SOLAR_PROJECT_ADMIN => System Landscape ):
Make sure you see all clients of your logical component. If not hit button System Role Assignment and add your System role.
Then still in the same tab: Hit button Shipment Routes and make sure, you see the complete transport track and only this track here!
After correct setup of TMS, RFCs, logical components and assignment of LC to your project:
First perform a Refresh and a Check in transaction code SOLAR_PROJECT_ADMIN => System Landscape => Change Requests. Then please recreate the maintenance cycle (and task list).
Regards,
Holger

4 System Landscape // ChaRM // No Export System found

Hi Folks,
I got some problems with a 4 system landscape in ChaRM.
The error message I get when doing a consistency check within my SMI project is:
Message from function module /TMWFLOW/CHECK_PRJ_CONS: No export system for NWA-303
Message no. /TMWFLOW/TRACK_N159
Transport route should be as follows:
DEV -> QAS -> INT -> PRD
Since I am still in testing phase I used clients instead of real systems in my configuration (TMS, Logical component,....)
My configuration looks like this:
NWA client 300 -> 301, transport layer ZCHM, transport layer SAP, consolidation
NWA client 301 -> 302, delivery
NWA client 302 -> 303, delivery
Logical Component defined as follows:
Developement System (Source: SAP): NWA:300
Type of Role: D Source System
Quality Assurance System (Source: SAP): NWA:301
Type of Role: O Target System
Integration System (Source: User): NWA:302
Type of Role: O Target System
Production System (Source: SAP): NWA:303
Type of Role: P Production System
Anyone got an idea what is wrong? did I miss anything?
The same configuration works for a 3-tier Landscape (without Integration System).
Any help is appreciated.
Thanks.

Hi Raquel,
Ours problems with RFC and with connections had be corrected with the note below:
1833778 - Activate Change Request management - Check error
Thank you very much!!
Adriana

BOBJ Landscape Architecture

Gurus ,
Client has existing BOBJ (Dev+QA) same box ,Production Box for LEGACY systems
and want to implement new SAP BW landscape DevQAProduction Boxes
What are the options available
1)can we have same BOX for legacy BOBJ and NEW SAP to be implemented for Universes,Crystal Reports,WebI,Xcelsius etc..
OR
2)do we need to have separate Box and separate out Legacy BOBJ with new SAP BOBJ implementation
can we partition database to house both legacy and sap repository on same Box ?
what is the best practise and approach
Thanks

Ingo ,thanks let me rephrase the question
Client has 2 tier architecture ,DEV and PROD for BOBJ and have relational universes
we plan to install 3 tier SAP BW different BOX landscape for (dev,qa,prod) and built OLAP universes
question is what is the best approach ,to use the clients existing 2 tier BOBJ landscape which has relational universes and then also use it to built OLAP universes on top of that ?
OR
built separate 3 tier new BOBJ landscape for SAP BW OLAP universes ??
What are the pros and cons of using 2 tier landscape vs 3 tier landscape
what are the pros and cons of using existing BOBJ relational universe landscape to house now SAP BW OLAP universes?
Thanks

BOE 5 TIER landscape

Similar Messages

Maybe you are looking for