What is meta? ×
Meta Stack Exchange is where users like you discuss bugs, features, and support issues that affect the software powering all 128 Stack Exchange communities.

I am a new user here, but I am already a TIBCO developer. I could create the wiki about the TIBCO tag, and there's so much more I want to contribute, but it is asking me so much for that.

Tag wikis can be edited by users with more than 1500 reputation, provided:

  • They are in the top 20 answerers for this tag

or

  • They hold the bronze tag badge for this tag

One, I don't have so many points. Two, there are not so many questions in this area to answer. If it goes like that it takes ages for somebody to create the wiki for TIBCO.

Additionally,

users with less than 500 reputation can't create new tags. The tag 'tibco' is new. Try using an existing tag instead.

So there seems to be rigidity in the rules of posts.

share|improve this question
    
Begging for Meta EXP doesn't mean you level up on SO proper –  random Dec 30 '10 at 21:09
add comment

2 Answers 2

This has been brought up before a few time.

As it stands you can post the body of the wiki (in your question here) and we will update it.

In the not too far future we will have a system in place that allows anybody to improve any content so hold tight 6-8 weeks.

share|improve this answer
    
OK, give me some points here, in asking and replying :) –  hB0 Dec 30 '10 at 18:14
add comment

What is TIBCO?

Tibco Software Inc. (Nasdaq:TIBX) is a software company, with headquarters in Palo Alto, California. TIBCO's products enable the real-time distribution of information through patented technology called The Information Bus™, or TIB®. TIBCO is adopted in diverse industries including financial services, telecommunications, electronic commerce, transportation, logistics, manufacturing and energy. Tibco’s main architecture is based on an information-bus oriented system concept. Whereas all the information that is used by the multiple systems passes through one information-bus. Tibco commonly refers to this information-bus as the “TIB”.

Benefits of a TIB-based architecture include:

Easy to create new subsystems – TIB allows developers to create new subsystems, modify existing subsystems, and add new services without having to change the UI or a subsystem’s code. Easy to move subsystems – A subsystem supplying data can be moved to other geographic locations without changing the subsystems that consume the information it supplies. This is important for fault tolerant operation where new subsystems can take over immediately upon the failure of another subsystems. Easier to develop applications – Saves development costs and time because the developers can use a tested API for communications rather than have to design, develop, implement, test, and maintain their own infrastructure code. Faster to develop – Developers can concentrate on applications and business requirements and not have to write and test an infrastructure. Applications will also be faster to develop because they will be linked into existing and well-tested libraries. Developers will not have to create code necessary for inter-subsystem connectivity Easier to maintain – Personnel can concentrate on the application code. The middleware layers are enhanced and maintained by professionals who are specialists in that type of software Easier to change – Changes will be easier to make to subsystems because they will be independent of their data sources and their data consumers Highly scalable – The system will be far more scalable because subsystems and hardware can be added easily and quickly to meet new user demands. Location transparency – The system cal exploit TIB’s subject based addressing to allow system components to be located dynamically, rather than being hard-coded. This supports a range of system migration needs. Easier to monitor – The system can use TIB/Hawk for monitoring. Error management – The system will be able to log and respond to system and business level errors by generating TIB-based notifications or advisories.

share|improve this answer
    
I am hoping to get good number of points here and for the tag-wiki –  hB0 Dec 30 '10 at 18:19
2  
points don't carry through to SO ... so it will not be much help ... I copied this... but it sounds very subjective and markety ... –  waffles Dec 30 '10 at 22:17
    
It's usually best to totally skip the puffery and focus on definite facts, e.g., by saying that those bold terms are the things that the system is designed to support, so leaving aside the question of whether it actually achieves it. It's also good to put in links to other useful sites (e.g., the vendor's site, the documentation, a community's own wiki) especially if they are likely to lead to someone finding the answers without asking a question. –  Donal Fellows Dec 31 '10 at 17:35
    
Thanks, true. OK, so i need to edit this comment for wiki? –  hB0 Jan 1 '11 at 12:57
add comment

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .