OS upgrade, what are the steps to be taken care?

[Former Member]

Hi,

Following is our tershnical details.

OS: - Windows2003 Server standard edition

Hard Drive:- 200 GB

RAM:- 3 GB

Concurrent users:- 60

We have 23 work process.

Now into my questions.

1)On what basis we will decide how much RAM is required for Our Server?

2)If we are going for an upgrade of Server from Windows2003 Server standard edition to Windows2003 Enterprise edition, what are the steps to be taken care?

Regards,

Lijo Joseph

[former_member185954 · Accepted solution]

Apart from the license part I believe Windows 2003 Server standard edition should be functionally the same as Enterprise Edition from the SAP Point of view, however in terms of features they might be different.

A detailed comparison is available at the below mentioned link.

http://www.microsoft.com/windowsserver2003/evaluation/features/compareeditions.mspx

Hope that helps.

Regards,

Siddhesh Ghag

[Former Member]

Hi,

To install WAS/NWDS the follwing minimum OS updates are required

System Requirements

Operating system Developing with the BI ODBO Connector requires Windows NT/2000/XP. Otherwise, there are no operating system restrictions.

Java Development Kit 1.4+

Web browser To view this documentation set, including the Javadocs, we recommend Internet Explorer 5 or Netscape 6 and above, or compatible frames-capable browsers such as Mozilla, Opera 7+, and Safari.

Adobe Acrobat Viewer To view the Developer's Guide (PDF), Adobe's Acrobat Viewer is required.

Memory Recommended: at least 256MB

Disk space Recommended: at least 50MB

Processor Recommended: at least 300MHz

JDBC If you are developing with the BI JDBC connector, ensure that the JAR files of your database provider's JDBC driver are available in your classpath.

ODBO If you are developing with the BI ODBO Connector, copy the JNI library sapbiado.dll into a location in your system path (for example, into your WINNT\system32 directory). You can find sapbiado.dll in the following location:

[installation drive]:\Program Files\SAP\JDT\ecplise\plugins\

com.sap.tc.ap\comp\BI_UDI\DCs\sap.com\bi\sdk\odbo\_comp\gen\

default\public\default\lib\native\OS_libs\NUC\ntintel\32\.

SAP Query If you are developing with the BI SAP Query Connector, ensure that your system is properly configured with SAP JCo. JCo is available on the SAP Service Marketplace at: http://service.sap.com/connectors/ --> SAP Java Connector --> Tools & Services.

We recommend version 2.1.x.

XMLA If you are developing with the BI XMLA Connector, no additional configuration is necessary. See the note below.

BI Java Connector To deploy applications created with the SDK onto the J2EE server, you need a BI Java Connector.

NetWeaver Developer Studio Configuration

This section describes how to set up a Development Configuration and where to find two additional JAR files on the installation CD that are required in order to develop with the BI Java SDK in the NetWeaver Developer Studio.

Locate the BI Java SDK ZIP file on the NetWeaver '04 Developer Studio CD in the following path: .../eclipse/tools/bi_sdk/bi_sdk.zip

Extract jARM.jar and jARMSat.jar from the /lib/ folder inside this ZIP file to a local folder. You will need these during runtime of any components you develop with the SDK (see Step 12, below).

To set up a Development Configuration in the Developer Studio, open the Development Configurations Perspective.

In the Local DCs view go to Local Development - MyComponents.

From the context menu, select Create new DC; give it a name and select Java as the development component type. Click Next and then Finish.

So that the BI Java SDK's example source files are available in your Development Configuration, go to the folder [installation drive]:\Program Files\SAP\JDT\eclipse\plugins\com.sap.ip.bi.sdk.doc_3.5.0 and open doc.zip. Extract the contents of the docs\examples\com\sap\ip\bi\sdk\samples path from the ZIP file to [installation drive]:\Documents and Settings\<your user name>\.dtc\LocalDevelopment\DCs\sap.com\<your dc>\_comp\src\packages.

In the Developer Studio, go to the Java Perspective and select Properties in the context menu of the new project.

Go to Java Build Path - Source and edit the contained folder to point to src/packages/docs/examples. Click OK twice.

Go to the Development Configurations perspective, in the Local DCs view and open Local Development - My Components - - DC MetaData - DC Definition.

In the context menu of Used DCs, select Add Used DC.

In the dialog, expand Local Development, and from the contained Software components select each of the following components by highlighting and clicking finish:

From BI_UDI:

bi/mmr/core

bi/mmr/cwm_1.0_source

bi/mmr/jmi

bi/sdk/core

bi/sdk/jdbc

bi/sdk/query

bi/sdkresultset

bi/sdk/xmla

From SAP-JEE:

activation

com.sap.exception

j2eeca

jaxm

jcert

jnet

jsse

jta

mail

sapxmltoolkit

servlets

tc/logging

webservices_lib

From SAP_JTECHS:

com.sapportals.connectorframework.framework

com.sap.util.monitor.jarm

To run an application created with the SDK, from the Run menu, select Run …. Select Java Application in the tree and click New. Ensure that the project name is the name of your development component. On the Class path tab, uncheck the flag Use default class path, and add jARM.jar and jARMSat.jar, from the location to which you unzipped them in Step 2 above, as external jars. Click 'Run.

For more information on working with the BI Java SDK within the NetWeaver Developer Studio, see SAP Web AS for J2EE Applications --> Development Manual --> Working with the Development Infrastructure in this Help structure. See Scenario 2, Working with Development Components, in particular.

Regards

RK