2tier or 3tier landscape for AS/400 ?

Dear all,
My company is considering upgrade options for current AS/400 server. There are 2 options we are considering.
1.) Upgrade the existing box to a bigger capacity to have higher SAPS. Landscape remains 2tier.
2.) Change 2 tier to 3 tier and split the Application Server from the central instance. No upgrade for the current AS/400 server, but just add few more Application server to run in Wintel server.
Have been advised that AS/400 server has self-managed capability and it is not advisable to split to 3tier.
My questions
a.) Anyone out there who has successful story to share in implementing 3tier landscape with AS/400 server ?
b.) Any write-up about the difference in terms of performance between 2tier and 3tier landscape. Or even to share your experience.
Your advise and comment will be appreciated.
Thanks.
Regards,
Kent

The best landscape for as/400 is 2tier as it has self managed capability.

Similar Messages

Setting up development landscape for E Commerce R/3

Hi Experts,
Need some good document reference for setting up our landscape for E Commerce 5.0.
I have gone through lot of documents and information but nothing consolidated about best practices to follow while doing so,
In our landscape we will have R/3 DEV, QA and PROD (All ready there) AND
3 corresponding AP 7 boxes for IPC and WAS (to deploy ISA java components)
The missing link in this is how best to use NWDI to talk to the 3 AP systems.
Q1 . Should we have 1 separate Box which has NWDI installed or can we use AP7 box for DEV to also use that for NWDI. (In this case on 1 BOX we will have IPC, WAS/ISA and NWDI.. so worried about performance)
Q2 Just in case itu2019s advisable to have a different BOX for NWDI, then how to configure NWDI to have all the 3 different AP 7 Boxes as part of development landscape to deploy ISA java applications from DEV to QA to PROD environment.
Thanks and regards,
Dips

Thanks for the reply.
My client says they dont have a QA environment. So they just have DEV and PROD. Since its a very small setup, We want to setup NWDI just for DEV and then PROD. Is it possible to not have QA ?
Regards,
Dips

Error in XI Sender JDBC adapter for AS/400 DB2

We are trying to connect to AS/400 DB2 from XI's Sender JDBC Adapter. we got the driver from DataDirect (connectjdbc.jar) and configured it within XI .The configuration according to the manual for this jar file is
// Register the driver with the driver manager
Class.forName("com.ddtek.jdbc.db2.DB2Driver");
// Establish the Connection
String url = "jdbc:datadirect:db2://corpserver1:50000;LocationName=ACCTNG";
Connection con = DriverManager.getConnection(url, "test04", "test04");
In XI we configured this as:
Driver = com.ddtek.jdbc.db2.DB2Driver
Connection = jdbc:datadirect:db2://servername;LocationName=NBHAGWAT
and specified the user id and password
Note: The Port Number is optional
When this was done in XI, we got the below error in the Adapter Monitoring:
Sender Adapter v2108 for Party '', Service 'JDBCtoFile':
Configured at 2006-12-19 15:45:31 MST
History:
- 2006-12-19 15:45:31 MST: Retry interval started. Length: 10.000 s
- 2006-12-19 15:45:31 MST: Error: Accessing database connection 'jdbc:datadirect:db2://AS400a;LocationName=NBHAGWAT' failed: DriverManagerException: Cannot establish connection to URL 'jdbc:datadirect:db2://AS400a;LocationName=NBHAGWAT': SAPClassNotFoundException: com.ddtek.jdbc.db2.DB2Driver
- 2006-12-19 15:45:31 MST: Processing started
Is this because there is something wrong because the way the connection string is specified.
Anybody who has configured XI Sender JDBC adapter for AS/400 DB2, please send us some information on this.
Thank you,
Regards,
Balaji

> SAPClassNotFoundException:
> com.ddtek.jdbc.db2.DB2Driver
It looks like your JDBC driver is not found. Have you deployed the driver to XI?
<a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/3867a582-0401-0010-6cbf-9644e49f1a10">https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/3867a582-0401-0010-6cbf-9644e49f1a10</a>

Solaris 10 won't boot up "Cannot load drivers for /pci@400.....

This is the error message that I am getting on a Solaris 10 sparc server
scsi: no major number
cannot load drivers for /pci@400.....
Can't load the root filesystem
Type 'go' to resume
{0} ok
Is there a way for me to correct this issue. It looks like I am missing a scsi driver to boot up the server? Is there a way to boot into single user mode, mount the filesystem and rediscover the hardware, etc.....

First i guess you have to verify that you can find the disks with a probe-scsi-all
next you can boot it of a CD-rom/dvd into single-user:
boot cdrom -s
.. or similar into single-user from a jumpstart image:
boot net -s
Then you can mount the root disk under something such as:
/mnt
and rebuild the config with:
devfsadm -R /mnt
be careful if you have a mirrored filesystem though, you don't want to update just one of the mirrors without first breaking the mirror..
.7/M.

How to implement 3tier architecture for HFM11.1.2.2

Hello Guys,
I want to implement 3tier architecture for HFM11.1.2.2 ie separating web part and apps part in two different servers. Please tutelage on how to achieve the same.

Hi Kashi,
Thanks for the pdf. Do you have any custom doc for the same. I want to implement only Hyperion Financial Management. I dont want FR or FDM. And moreover i want to segregate APP and Web part. When my client sends any request, it should first hit the web server first and then should redirect to the app server. I have implemeted HFM in single server but unable to find any help for implementing 3 tier.
Regards,
Suresh.

Information on 3-System Landscape for XI

Hi All,
Currently we have DEV/QA XI as one system and Prod as another. We plan to seperate QA and have a 3 system landscape for XI... ie, DEV, TEST, PROD.
My Question is
> Any documents on what are the system requirements in doing so?
> Is there any advantage/disadvantage in doing this?
Pavan.

The sysetm configuration might be 2Gb+ Ram with good storage of Harddrive....there can be problem when you have both the dev and QA system on the same server or same instance with dfiferent client......
It;s better to have the Different system for DEV,QA and Production but as far as SLD is concerened standard says to maintain the single SLD but for production it will be good if kept seperate SLD.

Minimum Development Landscape for XI

Hello,
In most cases the proposed optimum landscape for an XI project is the following:
2 XI servers such that
DEV R/3 linked via logical name to XI DEV and
PRD R/3 linked via logical name to XI PRD)
Asking the customer to buy 2 servers for XI in some cases does not sit well.
It is usually the case that the customer (already a SAP customer) has DEV + PRD R/3.
Can we use only one XI server to carry out both productive work and tests / developement work when needed. I am thinkg of filtering messages based on the logical name of the R/3 system. I do not know if this is safe since as far as i know when a DEV system is refreshed and kept uptodate by copying over the PRD the logical name is copied over as well. Therefore the above solution will have a high risk.
Anyone outhere that have faced a similar dilemma and come up with a neet solution?
Thanks
Dimitris Hagigeorgiou

Hi,
No its not at all advisable to have a same server for Dev and Prod. There are certain Best Practices proposed by SAP like DEV>QA>PORD and its advisable to follow it and there are lots of reason behind this kind of landscape.
At this point of time it might sounds good to have a one box which will server as DEV and PROD. But think of if something goes wrong and there are lots of chances to go wrong are DEV. As the name says its a development system ofcourse things will go worng quite often. If the same system is used for Prod then its all Business data and no orgn will compromise of loosing real time business data. There are lot many parameters apart from that like security etc..
Thanks,
Prakash

BI dual landscape for upgrades

We recently built a dual / parallel landscape for our BI system to support a support stack upgrade.   I've used the dual landscape concept for many years when doing ERP upgrades, and it has worked very well.   We thought a dual landscape for BI would work also.   However, we did not consider the automatically generated objects in BI.
What we found is that with 2 development systems, even though BI objects are created with the same logical name, the technical (generated) name will be different between the 2 systems.
Has anyone successfully implemented a dual-landscape for BI?   If so, how did you syncronize the technical names of objects between development systems without transporting the objects from one development system to the other?   Note: I'm of the opinion that you need to be extremely careful transporting objects between systems with different release/support pack levels and therefore avoid it at all costs . . . Note 1090842 + several bad experiences.   Therefore, I am very unlikely to consider transporting the objects created in PSD to RLD as a valid solution.
The following is just an attempt to better describe the issue:
Production support landscape looks like this:
PSD -> BWP   (these systems have lower release/SP levels than the systems in the release landscape)
Release landscape looks like this:
RLD -> RLQ    -
> Changes will eventually go to BWP after release/SP upgrade in BWP
Lets say queryA must be developed and transported to BWP prior to the release/SP upgrade in BWP.
In PSD queryA is created and gets assigned technical name 123456 and is transported to BWP.
In RLD queryA also gets created, but gets assigned technical name ABCDEF.
Sometime after the release/SP upgrade, when you are back to a single landscape (RLD -> RLQ -> BWP), a change needs to be made to queryA.   When you transport queryA to BWP, you end up with 2 queryA's, one with technical name 123456 and one with technical name ABCDEF.

Hey. I worked for years in a dual landscape environment and at one point, some folks were actually looking at three paths all pointing to production. The three path idea got squashed fairly quickly, but we had two landscapes for as long as I can remember. So we essentially had:
PAD --> PAQ --> Prod
PBD --> PBQ --> Prod
This was very helpful to be able to work on major releases and upgrades while still allowing weekly maintenance releases. I never looked for a document that deeply discussed the concept and pitfalls to watch out for.
I will say the system synch-up could often become quite a pain. This may sound a little crazy but we would transport from landscape A to landscape B but dual code from B to A. This was because A was for the triannual major releases and upgrades and B was maintenance work. There were times when we would transport both ways, but we tried to stay away from that (except for queries).
The idea was that anything that went to prod as maintnenance, out of B, should be dual coded in parellel in A. Then once a tri-annual type release went from A, all those new transports and dual coding would be moved to B. This is how we kept everything in synhc and it worked rather well. You always had to be careful around the time of the tri-annual go live, but that's to be expected.
The only objects we had constant problems with werre queries. I don't know of anything you can do about that. We eventually decided to always transport queries between the two landscapes. We would never manually dual code a query. We would eventually get the duplicate query issue in production. The pitfall here is if the same query is getting touched for maintenance and a major release... that was just something we had to workaround. But we never had any major problems with transporting between the two landscapes. The times it became a huge headache is when people would forget to dual code, or just plain to a bunch of prototyping in one of these environments when they should have been using a sandbox.
Not sure if I have answered your question, but hope this helps in some way. At least you know plenty of us feel your pain!

System Landscape for ESS/MSS in EP60 SP2

I have installed EP60 SP2 on J2EE 6.20 and MSSQL. I have imported business packages ESS 50-4 and MSS 60-1-5. I have created the folder Systems in Portal Content and created a system SAP_R3 with aliases SAP_R3_HumanResources, SAP_R3_Cross, SAP_R3_Travel, and SAP_R3_Financials.
My 4.7 R/3 system is app server R3DEV02.domain.com, system id DEV, sysno 01, client 100. My ITS server is http://itsdev01.domain.com:71/scripts/wgate/webgui/! using client 100. My EP path is http://sapport01.domain.com:50000/irj/.
Given this information, can anyone tell me exactly what parameters I must set in the system landscape for system SAP_R3 and what the values should be for ESS and MSS to work properly? If I go to the System Landscape Cockpit, system SAP_R3 fails all tests.
Any and all help is certainly appreciated.

Hello Gary,
WRT SAP_R3 system landscape test failure, I ran into the same issue earlier, for a SAP_R3_Dedicated system. Keep the same setting values, but leave the system id (DEV) Blank, then test.
Your definition of (Application Server Host Address + System Number) should be sufficient for a SAP_R3_Dedicated connection.
I hope this will resolve your system TEST problem.
Regards,
AAAttar

System landscape for DMS Repository in KM

Hi All,
When I create a System Landscape for DMS Repository in KM which sytem template I should choose?Should I choose
'SAP system using dedicated application server' or anything else?

The problem is resolved.

System Landscape for ESS/MSS

Hi Experts,
I am on ERP2004, EP 6.0 SP20. I am trying to create a system landscape for the ESS/MSS Applications. ALways the connection test fails. This is the landscape I am trying to create:
1. One SAP Dedicated Application Server: for SAP_WebDynpro_XSS
 Connector Details:
Application Host: <host>.<company.com>
SAP CLient: 010
SAP System Number: 00
Server Port: 3200 (Using Dedicated Application Server)
WAS Details:
 Host: <hostname>.<company.com>:50000
 Path: /webdynpro/dispatcher/
 System Alias: SAP_WebDynpro_XSS
System Aliases:
SAP_WebDynpro_XSS.
SAP_ITS_XSS
SAP_ITS_EBU
User Management;
Logon Method: SAPLOGONTICKET
User Mapping Type: admin,user.
When I am testing the
Connector Details:
I am getting the following errors:
1. Retrieval of default alias successful
2. Connection failed. Make sure user mapping is set correctly and all connection properties are correct.
WAS Connection Tests:
1. The system ID is valid
2. The system was retrieved.
3. The system object represents an SAP system
4. The following parameters are valid: Web AS Protocol (http) Web AS Host Name (<J2EE Engine Host>.<company.com>:50000)
5. The host name <J2EE Engine Host>.<company.com> was resolved successfully.
6. The server <J2EE Engine Host>.<company.com>:50000 could not be pinged successfully.
SSO is not set up yet. I do not understand why the details of J2EE Engine under WAS details in a system type : SAP Dedicated Application Server? Please help me. I am missing something.
I appreciate your help.
Regards,

Single Sign On set up and every application is working on portal.
But the ping always fails.
I do not understand one more thing from help.sap.com on System Landscape for ESS.
Documentation says:
Set up your system landscape. To do this, set up the following systems:
what kind of system this is: SAP_R3 or SAP_BW/SAP_CRM. In standard portal system template, there is no system like "J2EE engine".

Jv: Connector for AS/400 Urgent Pls!!!

Can anyone please tell me whether the J2ee CA resource adapter available for AS/400?

Hi,
OS/400 is IBM's operating system for its AS/400 and AS/400e line of business computers. OS/400 refers to Software...AS/400 refers to Hardware..
To answer your question: Yes, you can use that connector
Regards
GK Goalla

3 System Landscape for NW2004s BI?

Hi All,
Given the scope of BI systems in NW2004s BI, what is the recommendation regarding 2 vs. 3 system landscape for BI?
With BW, it was (relatively) easy to maintain a Dev, QA and Production system. Now with Portal and Java components of BI, the hardware requirements for a third (QA) instance would make it harder to justify?
What experience have people had with 2 vs 3 system landscapes for BI in NW2004s? Has anyone come across an SAP recommendation or best practice for this?
Thanks,
Matt

Hi Matt,
The NW2004s set-up by default installs the EP and other portal components when you select the Java stack. So I guess your question was whether we can have 1 EP system and 3 BW system in the landscape. But from my experience the lanscape has remained the same i..e - 3 BI system and 3 Portals, the reason clearly being that in order to fully utilize the BI7.0 frontend you need a portal. Now using 1 portal would put lots of load on it as in BI 7.0 many components require portal - Integrated planning, web reports, Admin cockpit, etc.
Bye
Dinesh

Landscape for implementing Recipe Management

Hello All,
Can someone kindly guide me as what's the recommended Landscape for Recipe Management, for example should two different ECC clients should be mantained ?, Recipe Management Recipes/Specifications stored in first 'source box' and Supply Chain data like BOM and Master Recipe stored in target box (basically creating bom/master recipe using transformation process from source box) ???. Kindly please throw some light and also how data is distributed between the two clients. Is Material Master first created in Supply Chain Box (target box), than ALE'd to source box, where it can be linked to Specifications??
Kindly let me know if I am thinking in correct direction, and also how to connect the 2 boxes?
Thanks in advance.
Sachin

Hi Sachin,
I think u r right abt the path proposed. However, i am adding few lines further. When implementing ALE functions it has to be ensured that the SAP system is implemented in a well structured way in both clients. Also it has to be ensured that during installation of ALE, the specification global settings and process functions are not altered in any way.
If ALE business processes are supported, functions and processes must be defined on a cross-system basis. The message types exchanged between the systems are defined in the distribution model. To implement the distribution of business application processes and functions using ALE it is indeeded to construct a logical Distribution Model of the whole system.
Within the framework of this configuration, customers can specify which applications are to run on which systems and which messages are to be exchanged between the applications. For example the Master data distribution for logistics is .
You can specify the relationships between logical systems, message types, BAPIs and filters in the distribution model. Applications and the ALE layer use the model to determine receivers and to control the data distribution.
For more information about maintaining the distribution model see the Customizing Implementation Guide (IMG):
Application Server - IDoc Interface/Application Link Enabling (ALE): Modeling and Implementing Business Processes and Maintaining the Distribution Model
Go thru the link for clarity on the implementation of IDoc interface/ electronic data interchange between the clients and master data.
[http://help.sap.com/erp2005_ehp_04/helpdata/EN/72/c18ee5546a11d182cc0000e829fbfe/frameset.htm]
[http://help.sap.com/erp2005_ehp_04/helpdata/EN/dc/6b7f5643d711d1893e0000e8323c4f/frameset.htm]
thank U,
mahesh

Detail system landscape for SAP APO

Hi All,
Can u pls tell me the system landscape for APO with pictures. (i.e data flow in between ECC to APO through CIF also between APO submodules)
purpose: need to prepare PPT.
Thanks.

Hi
Find the link WRT system integration
System Infrastructure (SAP Library - Integration of SAP APO and SAP R/3)
pls follow below thread for more info
Integration multiple R/3 systems with APO via CIF
Raja kiran

2tier or 3tier landscape for AS/400 ?

Similar Messages

Maybe you are looking for