First off I just wanted to say I'm happy to see this project. I was looking for this very thing last fall.
I downloaded the source and install it on a Solaris machine with one minor problem. Everything went fine up to the make for apache. It wasn't linking in the libs for Tuxedo and produced undefined symbol errors. By changing the order the Tuxedo libs were listed in LIBS1 in the "apache_1.3.20/src/Makefile" file.
I know the wsc is there twice and I'm not sure why, I got this from building the simpapp client from the Tuxedo sample directory with a -v (verbose) switch.
On another note, I was wondering if there were plans to add support for Tuxedo views?
-Dave
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Dave,
Good to hear from you. The project is slowly moving, tho its been a little slow during
the summer months with so many other things to do...
What version of Tuxedo client were you building against? I've done some tests on our
Solaris and 6.4-6.5 with none of the symptoms you described. But I did hear from one
user trying to build against Tux 8.0 who claimed some of the libraries had changed a bit.
If I could ever figure out how to better control the buildclient program to create
a .so file, I'd give up the hard-coded linking I have to do now.
As for views... I admit a lack of full knowledge on my part on this topic. Aren't
views the "C" structure techniques? And if so, the big question would be:
How can you build a C structure in PHP to pass? If these aren't views, please correct me.
I do hope to get some of the nested FML features added in 7.1. In general,
I'd say the future feature list is in a gathering stage. Its at a basic functional level,
enough to perhaps get some people to try it and find where its weak. What's next
is really up to the user group as a whole. I'm open to any ideas.
Brian
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2001-08-04
Brian,
I truly understand the time issue you have with putting into this (or other) projects.
We are currently using Tuxedo 6.5 and are slowly moving to 7.1. I compiled apache/php/tuxedo with tux6.5.
We also use views exclusively in our apps. You are correct, the buffer is allocated with a pointer to a C structure and I was wondering the same thing about how this would be done with php. I have done a few projects over the past year with php calling the "exec" funtion to run a tuxedo client (command line C app) to take advantage of the middleware functionality already built. Although these are all internal web pages there are some security risks in doing it this way.
I guess I was just wondering where this project was at.
Thanks for your reply.
-Dave
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I don't understand why my Solaris and 6.5 linked fine and yours didn't; but its
early beta software and some difficulties are to be expected.
We would have to start a larger discussion to see how/if we could support views.
As I think we both see, the hard part is not creating API function calls to pass
a view to Tuxedo, its building the C structure in the first place. PHP stores information
internally in a very different way that wouldn't lead to any easy conversion.
But I won't rule anything out without further thought.
Thanks for your input and keep an eye on the project. You may want to monitor
the development mailing list. In the mean time, if there are uses in your org
for this (without the view support) please give it a workout.
Brian
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
First off I just wanted to say I'm happy to see this project. I was looking for this very thing last fall.
I downloaded the source and install it on a Solaris machine with one minor problem. Everything went fine up to the make for apache. It wasn't linking in the libs for Tuxedo and produced undefined symbol errors. By changing the order the Tuxedo libs were listed in LIBS1 in the "apache_1.3.20/src/Makefile" file.
From: -lfml32 -lfml -lgp -lnws -lnwi -lbuft -lwsc
To: -lwsc -lbuft -lwsc -lnws -lnwi -lnws -lfml -lfml32 -lgp
I know the wsc is there twice and I'm not sure why, I got this from building the simpapp client from the Tuxedo sample directory with a -v (verbose) switch.
On another note, I was wondering if there were plans to add support for Tuxedo views?
-Dave
Dave,
Good to hear from you. The project is slowly moving, tho its been a little slow during
the summer months with so many other things to do...
What version of Tuxedo client were you building against? I've done some tests on our
Solaris and 6.4-6.5 with none of the symptoms you described. But I did hear from one
user trying to build against Tux 8.0 who claimed some of the libraries had changed a bit.
If I could ever figure out how to better control the buildclient program to create
a .so file, I'd give up the hard-coded linking I have to do now.
As for views... I admit a lack of full knowledge on my part on this topic. Aren't
views the "C" structure techniques? And if so, the big question would be:
How can you build a C structure in PHP to pass? If these aren't views, please correct me.
I do hope to get some of the nested FML features added in 7.1. In general,
I'd say the future feature list is in a gathering stage. Its at a basic functional level,
enough to perhaps get some people to try it and find where its weak. What's next
is really up to the user group as a whole. I'm open to any ideas.
Brian
Brian,
I truly understand the time issue you have with putting into this (or other) projects.
We are currently using Tuxedo 6.5 and are slowly moving to 7.1. I compiled apache/php/tuxedo with tux6.5.
We also use views exclusively in our apps. You are correct, the buffer is allocated with a pointer to a C structure and I was wondering the same thing about how this would be done with php. I have done a few projects over the past year with php calling the "exec" funtion to run a tuxedo client (command line C app) to take advantage of the middleware functionality already built. Although these are all internal web pages there are some security risks in doing it this way.
I guess I was just wondering where this project was at.
Thanks for your reply.
-Dave
I don't understand why my Solaris and 6.5 linked fine and yours didn't; but its
early beta software and some difficulties are to be expected.
We would have to start a larger discussion to see how/if we could support views.
As I think we both see, the hard part is not creating API function calls to pass
a view to Tuxedo, its building the C structure in the first place. PHP stores information
internally in a very different way that wouldn't lead to any easy conversion.
But I won't rule anything out without further thought.
Thanks for your input and keep an eye on the project. You may want to monitor
the development mailing list. In the mean time, if there are uses in your org
for this (without the view support) please give it a workout.
Brian