Concurrent Development

aware_support

The only explanation I can think of for this weird behaviour is that you have some other axis.jar file somewhere that gets pulled in instead of the correct one. Can you search your machine for all occurrences of axis.jar?

Is it possible that you have some old version of this file that resides in AwareIM/Tomcat/shared/lib directory?

PEFS

Wouldn't that be a problem with the way the software is functioning?

I have my production Aware IM app in the default folder location of C:\AwareIM and the trial version of 5.2 in the following location C:\AwareIM_5_2

Hopefully it is not that I cannot use a different folder name for the installation of the application...can it? I checked my C:\AwareIM and I do have a version of axis.jar present in that installation (it is version 1472)

Timo

I have searched the entire c:\ drive for axis.jar but only found one.

located in C:\AwareIM\Tomcat\shared\lib\
and datetime stamped 08/01/2012 7:31:42pm

NB: I also made the suggested change to the setenv.bat

aware_admin

Timo, is the output of your Configuration Tool the same as that of PEFS?

aware_admin

I think it dawned on me what the problem is. I bet both PEFS and Timo have startupOptions.props file in the AwareIM/bin directory and ACDC doesn't.

PEFS, Timo, could you please add axis.jar after aware.jar in the CONFIG_TOOL_STARTUP variable definition in this file, so it ends like this:

../Tomcat/shared/lib/awareim.jar;../Tomcat/shared/lib/axis.jar; com.bas.uiconfiguration.Application

and restart Aware IM

PEFS

That corrected it for me. However, if you do not put the .xml extension in the file name it will save as a bsv.

Timo

Yes that fixed the export for me. 🙂

The files type selector only seems to affect the list of files displayed and not the type of being created.

no matter what you select in "Files of Type:"

The type of file created is determined by the extension on the file name no matter what you select in "Files of Type:"

e.g.

FileName => FileName.BSV (i.e. defaults to BSV)
FileName.BSV => FileName.BSV
FileName.XML => FileName.BSV

This is not as intuitive as it could be; most other programs generally use the drop down to default/determine the file type being create.

Timo

I have an issue where I can import a Business Space (.BSV), exported from the previous Aware IM version. I can then export and import that as a .BSV file without any trouble... the problem is when I export it as a .XML file then try importing that .XML file.

The error is:

Exception while loading business space version Import error occurred. Please see output of the Configuration Tool for details off the error.

I don't know where the output of the Configuration Tool is. Please point me in the right direction.

I exported a Business Space in both .BSV and .XML formats, I can import the .BSV but not the .XML file. 🙁

pniehaus

aware_admin wrote
I think it dawned on me what the problem is. I bet both PEFS and Timo have startupOptions.props file in the AwareIM/bin directory and ACDC doesn't.

PEFS, Timo, could you please add axis.jar after aware.jar in the CONFIG_TOOL_STARTUP variable definition in this file, so it ends like this:

../Tomcat/shared/lib/awareim.jar;../Tomcat/shared/lib/axis.jar; com.bas.uiconfiguration.Application

and restart Aware IM

I still have the non functioning XML export problem.
I do not have a startupOptions.props file in either the server's

AwareIM/bin

nor in the Config tool's

C:Program Files\AwareIM\bin

directories.
The server has only one instance of axis.jar (dated 8-1-2012).

pniehaus

OK Found the problem:

The axis.jar file is not included in the ConfigTool distribution for windows. (Or does not get installed)

Found it on the internet and installed it in the

 \Aware IM Configuration Tool\lib

Export to XML now works.

I am probably breaking something though because the axis.jar I downloaded may not be the correct version (dated ‎11/‎06/‎2009 ‏‎19:35).
Any comments from support? Can I use the axis.jar off the linux server distribution?

aware_admin

Yes, you can - you did the right thing. This is an omission that will be fixed in the next maintenance release

« Previous Page