on 11-22-2006 1:11 PM
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
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
hello Roy,
Are you using alphanumeric password. If not then please try that.
Please award points for useful info.
Regards.
Ruchit.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
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 → Server → Services → Destinations →
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
<b>Checking the Configuration (Optional)</b>
8. Start the NWA and choose System Management → 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.
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
User | Count |
---|---|
84 | |
24 | |
11 | |
9 | |
7 | |
6 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.