NW2004s SR1 Application Server - confused...

[Former Member]

Hello all!

I think i might just need some clarification.

I've just finished installing NW2004s SR1 SPS10 (Solaris SPARC 64) with AS-JAVA, EP, BI and DI usage types. After the install I have to run the Template Installer as per the installation guide (pg 99). The first part of this Template Installer section is related to Application Server to configure the NetWeaver Administrator. The steps are as follows:

1. SLD system: configure and activate SLD.

2. SLD system: Connect SLD to CEN (if CEN present)

3. NWA system: Basic Configuration

4. NWA system: Connect NWA to CEN (if CEN present)

5. NWA system: Store access data per each managed Java system (optional)

6. NWA system: Register each managed ABAP system to SLD.

7. Managed Java system: Register system to SLD.

I have installed AS-JAVA which I'm assuming is the Application Server they are talking about. I installed this since it was necessary for EP, DI and BI. However, we don't have an SLD or CEN that they are talking about. So my question is whether or not I need to run this template installer for the Application Server when I don't have the components it's asking for. Seems unlikely...

Also, there's templates to run for BI and DI (in that order). I'm wondering if I don't run the AS template, can I still run these two templates, and how dependant are these templates on the order in which they are ran?

Could I run the DI template first and then the BI?

Thanks,

I'll award points for and help.

Beau.

[Former Member · Accepted solution]

Hi Beau,

You could skip the steps in NWA. That is no problem. The only thing you need is a running SLD to work with the different UTs.

You also could configure the SLD manually (see service.sap.com/instguides -> SAP Netweaver -> Release 2004s -> Installation -> Configuration -> Post-Instalation Guide SLD). There you will find all necessary steps.

Be sure that you at least register your J2EE Server to the SLD!!!

Regards

Daniel

[Former Member · Accepted solution]

Thanks Daniel,

Going to give that a shot today.

Beau.

[Former Member · Accepted solution]

Daniel,

Thanks for the help, that seems to have done the trick.

Wondering if I could bother you with another question regarding the template installer for the BI UT?

When running the BIPostInstallation template it's asking for a "ABAP Administration User." In note 917950 it says the following regarding this user:

- ABAP Administration User (ABAP_ADMIN and ABAP_PASSWORD)

Used by RFC Destination in J2EE; ABAP user

The BI system I'm trying to connect to is a completely different server than this one, which I'm assuming isn't a problem. I've looked around quite a bit on SDN, OSS and Help to see if they mention anything about "ABAP_ADMIN", but I've found nothing but what is in note 917950, which isn't much. The only existing user that could be associated in our existing BI (ABAP) system is J2EE_ADMIN.

Is this the user I'm supposed to use here, or do I need to create ABAP_ADMIN, and if so, what sort of authorizations might this user need?

I appreciate you help and have already awarded you points for you last answer.

If you'd like I'll make this question a new thread and so that you can get more.

Thanks,

Beau

[Former Member]

Hi Beau,

First of all, as my experience showed me, it is no good idea to install all UTs on one Application server (but I also had done this and it works without problems, but it's only a test systems with few users!)

The configuration of the SLD (System Landscape Directory) is an absolute necessary configuration step!!! The SLD is an application that is already installed on the J2EE engine.

The SLD is a central part of any Netweaver landscape. Dependent on the UTs you are using, the SLD has different jobs.

Some examples:

First it is the central point to manage your system landscape! (you need the information of your landscape ro work with the different UTs)

For UT DI it is also necessary to create define your software products, components ...

Also, all JCO Destinations are defined/created in the SLD. Without them you won't be able to connect to any SAP system (indepent of the release) through an WebDypro appliction.

So all UTs needs an configured and running SLD.

If you have any questions about configure and get the best out of your system feel free to send me an email.

Regards

Daniel

[Former Member]

Daniel,

Thanks for the information and I appreciate the response.

This is also just a development system with just a few users which is why we chose to do an "all in one" installation.

Since we don't have an CEN am I right in thinking that the configuration templates that are marked as "(if CEN present)" can be skipped, and I can continue with the other steps?

Also in step 6 "NWA system: Register each managed ABAP system to SLD," we don't have any systems we want to manage, as of yet, via NWA. Could I also skip this step?

Basically, I'm trying to get this system running with the usage types I have installed, but basically as a standalone system for testing.

Thanks.