Kablink Component
I have been considering replacing my current intranet system with teaming (2.0 open source) but I have a few questions that I need to know first. 1. My current intranet system is completely in-house developed (by me) and written almost entirely in PHP. Along with that I also have an incident system where people can request computer support. It is also written in PHP. I need to be able to integrate that into teaming if I choose to go that way. Integration could be as easy as just passing the username of the logged-in user in teaming to my application (through post, I guess) so it knows who is accessing it. There is very little information that I can find about external applications, just that it supports them. Is there more information so I can figure out how to make it work if it is possible?
2. Part of my current intranet system requires using IE (which I want to get away from) because some of the file sharing areas are just UNC paths to file locations. We have a large number of files in folders that I need to be able to support in teaming workspaces. I see the option for a mirrored file folder but I also saw in teaming 1.0 that it was only in the purchased product. Is that going to be the case with teaming 2? If I try it now I get an error.
Also, I have it setup to talk to my eDir tree for authentication and I have found one user that can't login using eDir credentials. Me. Everyone else that I've tried works fine. I get a long java exception that is thrown but it says more information is available in the tomcat logs. I'll look for those. Hopefully I can find them. It says something about return size unexpected or number of objects returned or something like that.
Replies
|
|||||||||||||||||||||||||||||||||||||||||||
On question 1 Teaming supports multiple ways to intergrate a PHP application. I will try to explain the basics of each and you can decide which is the best for your situation.
Remote Applications - Teaming supports a model of development similar to Facebook. A remote application can be registered in Teaming. This application will have session information sent to it when a user loads a page containing that application. The remote application can then use the session information to query Teaming, a remote database, or some other system and provide back to Teaming a HTML fragment that is then displayed inside Teaming where the remote application was placed. This method may work for you although you would need to write the adapter that handled requests from Teaming which are sent via the HTTP Post method.
Workflow integration - This may not be something you've considered but Teaming supports workflows that can contain custom workflow callouts to third party systems like your PHP application. You could model an incident in Teaming and create a workflow that models the various states the incident can be in. Then on transisions between states a custom callout to your PHP application can trigger processing in your system and even return data to be associated with the Teaming entry.
iFrame - There is always an iFrame.
For the authenticaion question you will need to look at single sign-on solutions to get a seamless user experience between the two applications.
Question 2 related to mirrored folders is a bug in Kablink Teaming. Mirrored folders are not configurable in Kablink although the option is there to create one.