Skip to Content
author's profile photo Former Member
Former Member

MI Client & Server component issue


I am using MI Client component 2.5 sp04 and has Netweaver WebAS6.40 (sneak preview). I am able to communicate between MI client and WebAS server component. But I'm not able to logon to the MI Web Console of server. It always gives the same error "Invalid user or password!". I'm using the same login id here which I have used to synchronize between MI client and MI server.

Due to this I'm not able to deploy any applications and

test them.

So my question is -

1. Which login/pwd, System, client and system number values should be used to log onto the console.

2. Is there any way to test my applications without deploying them from Web Console.


Ravi Sharma

HCL Technologies

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

2 Answers

  • Posted on Jan 13, 2005 at 04:00 PM

    I have a question: Are you sure, that you are able to synchronize?

    About your questions:

    1. There is no other user necessary, just ensure that your R/3 user has the following authorization objects:




    I think the last is the authorization object that enables the WebConsole login.

    2. There is no other way to INSTALL a new application on the MI Client. However, there's a possibility to UPDATE an already installed application, as follows:

    0. Stop the MI Client if running

    1. Create a new .WAR file

    2. Delete the old project's folder

    3. Copy the .WAR file in the /webapps folder

    4. Start the MI Client

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Jan 14, 2005 at 12:53 PM

    Hello Ravi,

    the authorizations that Todor mentioned are important. You have to assign them to the user with which you want to logon to your webconsole.

    To determine, whether your sync works, you can as well use the sync-test-URL mentioned in the MI instguide.

    You can of course "deploy" applications using your eclipse IDE directly to the local MI Client installation. Therefor it is necessary to maintain the MDK plugin configuration in eclipse properly. But running applications from eclipse has several limitations:

    Somehow you don't get the same runtime environment as a regularly deployed application. You cannot, for instance, instanciate the singleton of a TransactionManager which means that persistence cannot be tested locally. Additionally you cannot sync due to a missing Mobile Solution Descriptor and conversation ID.

    So my approach is to design as far as possible without these features, to be able to do quick and easy testing from within the IDE. But when it comes to syncing and persistence, you have to go the regular way via webconsole.

    Best regards,


    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.