cancel
Showing results for 
Search instead for 
Did you mean: 

Remote Systems connected to NWA prompt for uid every time

Former Member
0 Kudos

Hello,

I am trying to connect our production server to be monitored at the NWA.

Now, the problem is that when I want to open the server from the table I receive a popup telling me this:

Connection Type: JMX Connection

Status: Unauthorized

When I enter Username and password for the remote system I am able to connect, but I don't want to enter it manually every time. I have created an HTTP Destination to the production server and set the credentials over there yet it doesn't seem to use it.

Thank you in advance,

Roy

Message was edited by:

Roy Cohen

Accepted Solutions (0)

Answers (4)

Answers (4)

Former Member
0 Kudos

Hello Roy,

This will be needed in case of ABAPp systems not JAVA.

Check if you have assigned the user SLD roles.

Regards.

Ruchit.

Message was edited by:

Ruchit Khushu

Former Member
0 Kudos

Hello Phani,

An update: Once I changed the URL to the DB instance it is working, but now when I am on central mode I receive this pop up for the local system. Do I need to define an HTTP Destination for the local system itself when I am on central mode?

Regards,

Roy

Former Member
0 Kudos

Hi Roy,

In my view, you need to do the same type of setting for all the monitoring systems including your local one

Regards,

phani

Former Member
0 Kudos

Hello Phani,

I did that as well yet for the local system I still receive this JMX connection pop-up when I am on Central mode. When I am on local mode it is working for the local system. It looks a bit strange to define an HTTP Destinattion on the WAS to itself don't you think...?

Regards,

Roy

Former Member
0 Kudos

Hi Roy,

I think If you want to monitor all the systems through CEN you need to register local system aswell

Check in the step 3 if you have given wrong DBHOST

sap.com/tcjejmxwsconnectorsp/<SysID>/<DB Host>

In a central system, the database host is simply the host on which

the Java system itself is running.

Try this out and letme know if it works,

Regards,

Phani

Former Member
0 Kudos

On the development server the host_name = db_name so I am sure I configured it correctly.

Any other ideas?

Former Member
0 Kudos

Hi Roy,

Once we faced a similar situation and it got solved after use of alphanumeric password.

Depends of one of the profile parameters for your syste.

Anyways does this user have s_rfc authorization object in its profile? That is also needed.

Regards.

Ruchit.

Former Member
0 Kudos

hello Roy,

Are you using alphanumeric password. If not then please try that.

Please award points for useful info.

Regards.

Ruchit.

Former Member
0 Kudos

I am using an alphanumeric password and I don't see how it is related...

Former Member
0 Kudos

Hi,

Could you please elaborate this requirement, i.e. where do I check it and how do I assign it?

Regards,

Roy

Former Member
0 Kudos

Hi Roy,

Check wether you have the roles

• SAP_JAVA_NWADMIN_CENTRAL

• SAP_JAVA_NWADMIN_CENTRAL_READONLY

to access centrally

please let me knwo if this is helpful

Regards

Phani

Former Member
0 Kudos

Hi Phain,

Yes I do yet it still pops up the authentication window every time

Regards,

Roy

Former Member
0 Kudos

Hi roy

can u explain me in brief what is ur landscape and which systems u want to monitor i.e u have java systems

regards,

phani

Former Member
0 Kudos

Hi Phain,

I have 2 Java Systems which represents the 2 J2EE engines for development and production.

The NWA and the SLD are installed on the development server and use it's J2EE engine, so for the NWA this is the local system.

I would like to connect the production J2EE engine as well and for that I have:

1. Registered it in front of the dev SLD (Through it's Visual Admin)

2. Added it at the NWA as monitored system by querying the SLD.

This moves me from local view to central view and at this view I cannot connect not the production system and not even to the local system. What I receive is the JMX pop-up. According to an elearning presentation I have and that describes this same error, I have created an HTTP Destination for the production system using it's admin tool yet that doesn't seem to help.

Regards,

Roy

Former Member
0 Kudos

Hi Roy,

Just follow these steps and see

If you want to administer multiple Java systems with the NWA, we recommend that you

store the relevant logon data in the J2EE Engine of CEN, so that you do not need to log

on with a user name and password every time.

1. Start the Visual Administrator for the J2EE Engine of CEN, and log on with your

user as a J2EE Engine administrator.

2. In the navigation bar, choose Cluster &#8594; Server &#8594; Services &#8594; Destinations &#8594;

Runtime, and select the HTTP in the destination tree. Choose the New button.

3. Enter the following name:

sap.com/tcjejmxwsconnectorsp/<SysID>/<DB Host>

<SysID> is the system ID of the Java system to be administered; <DB Host> is

the host on which the database of this system is running.

• In a central system, the database host is simply the host on which

the Java system itself is running.

• In the case of named MSSQL instances, enter the following name:

sap.com/tcjejmxwsconnectorsp/

<SysID>/<DB Host>/<DB Instance>

4. On the next screen, enter the following URL:

http://<j2eehost>:<port>/WSConnector/Config1?style=document

<j2eehost> is the host of the central instance of the Java system to be

administered; <port> is the HTTP port of the J2EE Engine.

5. In the Authentication input field, choose the BASIC entry from the dropdown list.

6. In the User Name and Password fields, enter the corresponding data for a user

with administrator authorization in the Java system to be administered.

7. Save your entries by choosing the Save button.

Please let me know if this helps

Regards,

Phani

null

Former Member
0 Kudos

<b>Checking the Configuration (Optional)</b>

8. Start the NWA and choose System Management &#8594; Administration in the top-level

navigation. In the Detailed Navigation, choose the Systems entry.

9. A list of the Java systems to be administered appears. If you expand the tree for a

system for which you stored access data above, you do not need to make any

additional entries to log on to this system.

Former Member
0 Kudos

Hello Phani,

I jhave followed these exact steps as I already stated yet I still receive the authentication window.

Regards,

Roy

Former Member
0 Kudos

Hello Phani,

Now that double check I see that I made one thing different in your procedure:

at step 3 instead of:

sap.com/tcjejmxwsconnectorsp/<SysID>/<DB Host>

I have entered the host and not the DB host since SAP documentation mandates that it will be entered like this:

sap.com/tcjejmxwsconnectorsp/<SysID>/<Host>

Now, in our case the DB is not exactely the same as the host since it is sitting on a different instance like this: <Host>\SAP.

What do you think?

Regards,

Roy