MxLoader

Bruno, will you be creating an MxLoader version for MAS 8 and beyond?  This tool increases our troubleshooting techniques 10-fold.  It would be great if we had a version for MAS.  

Michael, I'm sure Bruno will step in and reply, but his last few versions have supported MAS for some time. To make the best use I recommend the following configurations:

Service:REST

Authentiction: API

User: <API Key> 

Prior to updating the configuration in Maximo Manage (MAS version of Maximo) generate an API (new application, was previously in Work Centers) which is what you will define as the User.

Everything else so far works exactly the same as it did before.

Mike

Bruno, will you be creating an MxLoader version for MAS 8 and beyond?  This tool increases our troubleshooting techniques 10-fold.  It would be great if we had a version for MAS.  

Yes Michael M., I'm stepping in   :-)

The REST service with API authentication is the suggested configuration for MAS.

I have already used it many times without any problem.

Michael, I'm sure Bruno will step in and reply, but his last few versions have supported MAS for some time. To make the best use I recommend the following configurations:

Service:REST

Authentiction: API

User: <API Key> 

Prior to updating the configuration in Maximo Manage (MAS version of Maximo) generate an API (new application, was previously in Work Centers) which is what you will define as the User.

Everything else so far works exactly the same as it did before.

Mike

Bruno, will you be creating an MxLoader version for MAS 8 and beyond?  This tool increases our troubleshooting techniques 10-fold.  It would be great if we had a version for MAS.  

Hi Bruno,

MAS 8.11 has change API administration. Should MxLoader works in the same way? I have tried to connect Mxloader using a new API Key generated from the new API KEY administrator in MAS and it doesnt works. 

Yes Michael M., I'm stepping in   :-)

The REST service with API authentication is the suggested configuration for MAS.

I have already used it many times without any problem.

Michael, I'm sure Bruno will step in and reply, but his last few versions have supported MAS for some time. To make the best use I recommend the following configurations:

Service:REST

Authentiction: API

User: <API Key> 

Prior to updating the configuration in Maximo Manage (MAS version of Maximo) generate an API (new application, was previously in Work Centers) which is what you will define as the User.

Everything else so far works exactly the same as it did before.

Mike

Bruno, will you be creating an MxLoader version for MAS 8 and beyond?  This tool increases our troubleshooting techniques 10-fold.  It would be great if we had a version for MAS.  

Hi Javier,

You should use the api key generated from Manage, not MAS.

We are also on MAS 8.11 and it works fine.

Regards

Hi Bruno,

MAS 8.11 has change API administration. Should MxLoader works in the same way? I have tried to connect Mxloader using a new API Key generated from the new API KEY administrator in MAS and it doesnt works. 

Yes Michael M., I'm stepping in   :-)

The REST service with API authentication is the suggested configuration for MAS.

I have already used it many times without any problem.

Michael, I'm sure Bruno will step in and reply, but his last few versions have supported MAS for some time. To make the best use I recommend the following configurations:

Service:REST

Authentiction: API

User: <API Key> 

Prior to updating the configuration in Maximo Manage (MAS version of Maximo) generate an API (new application, was previously in Work Centers) which is what you will define as the User.

Everything else so far works exactly the same as it did before.

Mike

Bruno, will you be creating an MxLoader version for MAS 8 and beyond?  This tool increases our troubleshooting techniques 10-fold.  It would be great if we had a version for MAS.  

Hi Javier,

You should use the api key generated from Manage, not MAS.

We are also on MAS 8.11 and it works fine.

Regards

Hi Bruno,

MAS 8.11 has change API administration. Should MxLoader works in the same way? I have tried to connect Mxloader using a new API Key generated from the new API KEY administrator in MAS and it doesnt works. 

Yes Michael M., I'm stepping in   :-)

The REST service with API authentication is the suggested configuration for MAS.

I have already used it many times without any problem.

Michael, I'm sure Bruno will step in and reply, but his last few versions have supported MAS for some time. To make the best use I recommend the following configurations:

Service:REST

Authentiction: API

User: <API Key> 

Prior to updating the configuration in Maximo Manage (MAS version of Maximo) generate an API (new application, was previously in Work Centers) which is what you will define as the User.

Everything else so far works exactly the same as it did before.

Mike

Bruno, will you be creating an MxLoader version for MAS 8 and beyond?  This tool increases our troubleshooting techniques 10-fold.  It would be great if we had a version for MAS.  

Hi Andre,

I'm also having some issues with getting MXLoader working with MAS and want to verify some of my config:

For Server Address, should this be the URL for the Manage environment or for MAS?

If using the REST Service with API Authentication, only the API key should be entered for the User and nothing should be entered for Password?

For the API Service Context Root, is the default value "/maximo/api/" correct, or does this need to be changed at all?

Also, within Manage itself, are there any system properties that need to be updated for this API authentication to work? I'm consistently running into an HTTP 403 Forbidden error, "You cannot log in at this time." I've already verified the user account tied to the API key is active in Manage and isn't blocked for any reason.

Hi Javier,

You should use the api key generated from Manage, not MAS.

We are also on MAS 8.11 and it works fine.

Regards

Hi Bruno,

MAS 8.11 has change API administration. Should MxLoader works in the same way? I have tried to connect Mxloader using a new API Key generated from the new API KEY administrator in MAS and it doesnt works. 

Yes Michael M., I'm stepping in   :-)

The REST service with API authentication is the suggested configuration for MAS.

I have already used it many times without any problem.

Michael, I'm sure Bruno will step in and reply, but his last few versions have supported MAS for some time. To make the best use I recommend the following configurations:

Service:REST

Authentiction: API

User: <API Key> 

Prior to updating the configuration in Maximo Manage (MAS version of Maximo) generate an API (new application, was previously in Work Centers) which is what you will define as the User.

Everything else so far works exactly the same as it did before.

Mike

Bruno, will you be creating an MxLoader version for MAS 8 and beyond?  This tool increases our troubleshooting techniques 10-fold.  It would be great if we had a version for MAS.  

Hi Craig,

For server Address you should put the manage route url

If using the REST Service with API Authentication, only the API key should be entered for the password and nothing should be entered for user

For the API Service Context Root, use the default value "/maximo/api/"

Don't forget to give access to the object structure to the user you are using.

Hope it helps

Hi Andre,

I'm also having some issues with getting MXLoader working with MAS and want to verify some of my config:

For Server Address, should this be the URL for the Manage environment or for MAS?

If using the REST Service with API Authentication, only the API key should be entered for the User and nothing should be entered for Password?

For the API Service Context Root, is the default value "/maximo/api/" correct, or does this need to be changed at all?

Also, within Manage itself, are there any system properties that need to be updated for this API authentication to work? I'm consistently running into an HTTP 403 Forbidden error, "You cannot log in at this time." I've already verified the user account tied to the API key is active in Manage and isn't blocked for any reason.

Hi Javier,

You should use the api key generated from Manage, not MAS.

We are also on MAS 8.11 and it works fine.

Regards

Hi Bruno,

MAS 8.11 has change API administration. Should MxLoader works in the same way? I have tried to connect Mxloader using a new API Key generated from the new API KEY administrator in MAS and it doesnt works. 

Yes Michael M., I'm stepping in   :-)

The REST service with API authentication is the suggested configuration for MAS.

I have already used it many times without any problem.

Michael, I'm sure Bruno will step in and reply, but his last few versions have supported MAS for some time. To make the best use I recommend the following configurations:

Service:REST

Authentiction: API

User: <API Key> 

Prior to updating the configuration in Maximo Manage (MAS version of Maximo) generate an API (new application, was previously in Work Centers) which is what you will define as the User.

Everything else so far works exactly the same as it did before.

Mike

Bruno, will you be creating an MxLoader version for MAS 8 and beyond?  This tool increases our troubleshooting techniques 10-fold.  It would be great if we had a version for MAS.