cancel
Showing results for 
Search instead for 
Did you mean: 

Is MI WebConsole and NetWeaver Administrator->Mobile Administrator SAME ?

Former Member
0 Kudos

Hi

I am trying to access MI - WebConsole but could not make it.

I have SAP Web AS 7.0 with MI 2.5 installed with latest service packs. After all configuration (SAP MI 2.5 SP17 Standard install/config guide), I could not get SAP MI WebConsole. Getting 404 error.

After reading few documents I have an assumption/suspection that

MI WebConsole is for SAP Web AS 6.4 and

NetWeaver Administrator -> Mobile Administrator for SAP Web AS 7.0

to do the same functionality.

So the question is...

is MI WebConsole (http://<server:port>/me/WebConsole/login

will not work in SAP Web AS 7.0 as it has been replaced by NetWeaver Administrator -> Mobile Administration ?

(http://<server:port>/nwa

If not, do we still need MI WebConsole inorder to make communication between R/3 (ABAP stack) and MI 2.5 Client(laptop)

Even http://<server>:50100/me is not working. Always getting 404 Error.

I have http and https configured successfully.

Please advice.

Here is my system landscape for the reference:

-


SAP MI 2.5 (middleware) -> installed in a separate server with ABAB+JAVA stack and SAP Web AS 7.0.

SAP ERP 2005 (backend) -> installed in a separate server with ABAB stack only and SAP Web AS 6.40

SAP MI 2.5 (client) -> installed in a laptop with Windows XP Pro.

-


Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

hello sri,

java sync servlet and MI WebConsole will still be supported

for awhile when the Mobile NWA gets matured...

MI WebConsole is only an administration tool, the MI Sync

Servlet is the one responsible for data transfers from

your MI client to MW. In 7.0, the Mobile NWA will become

the primary tool instead of the MI WebConsole and java

sync servlet will also be substituted by the ABAP sync

service. you can easily configure you MI using templates.

your errors might be some configuration problems.

try tracing for exceptions in your J2EE visual admin.

regards

jo