This content has been marked as final. Show 8 replies
First of all, I would like to suggest you to migrate to UDS 5.03 which is the latest version of Forte (UDS 5.01+ServicePack 1).
1.Regarding your question #1, SUN will probably provide you with a migration procedure document. It is very clear and details step by step what you need to do, depending on the platform you work with. So, I would suggest you to call your SUN Rep to get a copy.
2. Some of the things UDS now dows better:
- XML Processing
- XSLT Transformation
- Reflection capabilities
- LDAP access
- SOAP cabailities for UDS Service Objects.
- Generation of Java proxies for accessing your UDS service Objects exposed as a SOAP Server.
and so on...
3. Certification Matrix = http://docs.sun.com/db/doc/816-6317-10
Other info = http://docs.sun.com/db/prod/4217#hic
Hope this helps...
We have our current application runing on Forte 3.0.M.2 and we wanted to update our system to UDS 5.0.3
Can you please let me know.
what are the important steps that i should take care before migrating to UDS?
we have our clients running on Windows 98 and Windows 2000 and our server is on SUN Solaris 7 32bits.
please excuse if I am repeating myself...if I check only Compiled and not the Generate C++ Api (for a compiled partition), I don't need the C++ compiler installed.. it is a bit confusing for me because the code generator does seem to generate some .cc files.. just wondering how this does get compiled without a C++ compiler..thanks again
There is no need to select code generator unless you plan on compiling to the platform specific executables.
Without a C++ compile that is compatible with UDS you will not be able to compile the files after you generate the code.
If you select both code generate and compile, then UDS will automatically call the correct compiler calls to compile the generated code into machine dependent files.
Apologies if I got you confused.
If you checked "Compiled" on a Fort� partition your TOOL code will be translated into C++ and during a second phase the .cc & .cdf files compiled.
So you are correct you don't need a C++ compiler to generate the C++ files, but the bunch of files produced still need a C++ compiler to be compiled into a platform dependant executable (usually a .so , .a or .dll file).
The generate C++ API option allows for an SO in a "compiled partition" to be called from a C++ application (it generates a couple of extra files to be used as include & source)
So running the compile scripts over the weekend ... I sympathise, I wish I were down the pub.