Issues with /lawson-ios/action/ command

Name	Points
Greg Moeller	4184
David Williams	3349
JonA	3291
Kat V	2984
Woozy	1973
Jimmy Chiu	1883
Kwane McNeal	1437
Ragu Raghavan	1372
Roger French	1315
mark.cook	1244

CDCummins

Basic Member

Posts: 9

12/12/2012 3:23 PM

We are attempting to implement some new components in our production system, and are running into issues. The application works exactly as expected in our test environment, but breaks down when we run it in production.

By using Fiddler, we have found that it is breaking down on calls to IOS. Extracting out the base command of the calls, we have discovered that a call from a web browser to our test environment using http://{test server}/lawson-ios/action/ executes normally: the result is a displayed list of available actions.

However, the same call to our production environment (using http://{production server}/lawson-ios/action/) immediately returns a 404 Not Found error. It should be noted that our production environment is otherwise behaving normally.

We believe that if we can get the basic lawson-ios/action command to work for production, then the application should also begin to run as expected. As far as we can tell, the configuration for the two environments is the same.

Has anyone else run into an issue with lawson-ios/action or its related commands?

Any thoughts on where to look would be greatly appreciated.

Thanks so much!

John Henley

Posts: 3353

12/12/2012 4:07 PM

Do you have LSF/IOS installed the same way on test as you do in production?
When you refer to "/action/", are you talking about a specific servlet?
Can you paste in a successful URL here from your test server (removing the server name, of course)?
"/lawson-ios/" isn't a standard directory name used by any installers that I've come across, but it might be that someone set up an alias on the web server in your test environment that never was set up on your production server.
Can you try http://{production-server}/servlet/SysEnv on your production server and see if that works?

John Henley

Posts: 3353

12/12/2012 4:19 PM

Actually, let me backtrack for a second. Since you posted this in the S3 Sys Admin forum and you mentioned IOS, I assumed you meant this was LSF9, correct?

CDCummins

Basic Member

Posts: 9

12/12/2012 5:01 PM

Hi John,

Yes...this is LSF9, and as far as we can tell, the installation is the same between both envrionments. (As this is my first posting, I hope I submitted it to the correct forum. I thought this was a "generic" S3 forum and thought this would be a good choice. If possible, I would be happy to move it to a more appropriate forum.)

To answer your other questions, I can successfully execute http://{prod server}/servlet/SysEnv against our production environment.

The command I noted in my first post is actually an abbreviated version of many of the commands that have been failing, and they are all auto-generated by the application we are having issues with (LSO). They all have the same /lawson-ios/action/… root, which, as it turns out, stands as its own command.

An example of one of the full commands is http://{server}/lawson-ios/action/navigation?token=ROOT

Again, this command executes normally in test, but fails in production.

Thanks again!

John Henley

Posts: 3353

12/12/2012 5:52 PM

Yes, you are in the correct forum.
It sounds like you have a Java tool, like JBoss seam, installed on the test server in /lawson-ios/, pointed at the Lawson Java servlets in /servlet/.

CDCummins

Basic Member

Posts: 9

12/12/2012 6:37 PM

Thanks, John.

(I must also confess that I am very new to the world of Lawson.)

When you say that I may have a Java tool installed "in /lawson-ios/", where/how would I look to confirm that? I have been trying to see if I could find a physical location of lawson-ios on the test and prod servers, but have had no luck so far.

John Henley

Posts: 3353

12/13/2012 2:54 PM

Since you're familiar with fiddler, you should start with http://{server}/lawson-ios/action/navigation?token=ROOT on the test server, and examining the response headers. That might give you a clue regarding where / what is used to generate the page.

CDCummins

Basic Member

Posts: 9

12/13/2012 8:29 PM

Thanks again, John.

Looking at the response headers in Fiddler for a successful test call, I do see that two servers are noted: Microsoft-IIS/6.0 and WebSphere Application Server/7.0. On the other hand, the headers for a failed production call only have Microsoft-IIS/6.0 noted, so it looks like the issue may be in Websphere. Are there any configuration files, or permissions, I could look at that may explain the failed return from Websphere?

John Henley

Posts: 3353

12/13/2012 8:43 PM

Are you seeing a failure related to WebSphere, are just not seeing an entry in the header?
Using the WebSphere App Server console, you would need to look at the web server configuration (and IIS plugins) on the test server, as well as what apps are deployed on that app server in your test environment, and compare all of that to your production environment. If you're not familiar/comfortable with WebSphere, you might need to enlist some help.

CDCummins

Basic Member

Posts: 9

12/13/2012 8:54 PM

John,

Thanks for the pointer about using the WebSphere App Server console. I will check with my supervisor about using it, and let you know if that does not seem to lead anywhere.

Thanks again!

CDCummins

Basic Member

Posts: 9

12/18/2012 12:49 PM

John,

We were finally able to get the issue resolved.

Essentially, we just uninstalled and redeployed IOS to WebSphere, and re-propagated the plugins.

Once this was complete, the base calls to “http://{prod-server}/lawson-ios/action/” worked as expected, and the LSO functionalities that derive from that command also work as expected.

Again, thanks so much for your assistance with this issue!

John Henley

Posts: 3353

2/15/2013 1:17 PM

Posted By John Henley on 12/12/2012 12:52 PM
Yes, you are in the correct forum.
It sounds like you have a Java tool, like JBoss seam, installed on the test server in /lawson-ios/, pointed at the Lawson Java servlets in /servlet/.

I wanted to update/correct this ... is actually part of LSF 9.0.1 + IOS APIs