Getting Started with JBuddy-CF IM Event Gateways
Post-Installation Configuration
Assuming the installation of JBuddy-CF finished correctly and ColdFusion Server is currently shutdown per the installation instructions, you are ready to create IM Event Gateways using JBuddy-CF so start ColdFusion Server. It's as simple as 1-2-3!
- Proxy Settings
- Specify IM Accounts
- Create Gateway Types Automatically OR Create Gateway Types by Hand
- Create Gateway Instances for each IM account you specified in step 2
JBuddy-CF makes outgoing TCP socket connections to the specified IM services. The default hosts, ports, client version numbers, etc that JBuddy-CF will use are specified in the property files corresponding to the IM protocol. See {cf.root}\lib\AIM.properties for AIM connectivity. See {cf.root}\lib\MSN.properties for MSN connectivity, etc. If a direct TCP socket connection to the specify host and port are not permitted by your internet firewall or if your organization has some type of IM archival or management solution in place, you have may have to modify some settings for a particular IM service. JBuddy-CF supports DIRECT, SOCKS4, or SOCKS5 connectivity to the IM services. To change the connectivity or other IM service specific settings:
- cd to {cf.root} and then into lib\
- Edit a .properties file corresponding to the IM service (AIM, ICQ, MSN, YIM, JSC, XMPP, SAMETIME)*
* You may need to restart your ColdFusion MX server for changes to take effect if you have already started an IM Event Gateway of this type.
Each Gateway Instance requires it's own IM screen name and password. Follow these steps to specify your IM accounts:
- cd to {cf.root} and then into gateway\config\
- Create or edit a .cfg file corresponding to each Gateway Instance you created. Supply a screen name and password
You can create JBuddy-CF Event Gateway Types automatically using a supplied script.
- cd to {cf.root} and then into gateway\config\
- Open register_jbuddy_cf_gatewaytypes.cfm in a text editor
- Change the password from 'admin' to your CF Administrator password and then save the file
- Next, deploy the file to your wwwroot
- Now request it with your browser. This should register all the new JBuddy-CF eventgateway types automatically
- Proceed to Create Gateway Instances
You can manually create JBuddy-CF Event Gateway Types within CF Administrator.
Refer to Event Gateway Types table below)
- Expand the Event Gateway tab
- Click Gateway Types item
- Create a new Gateway Type from the types below and corresponding to the screen name and password you used above
- Saving the new Gateway Type
Within CF Administrator, expand the Event Gateway tab then click Gateway Instances item:
- Create a new gateway instance for the gateway type you just created above
- Specify the ColdFusion Component to handle events from the IM event gateway (CFC Path)
- Specify the cfg File for corresponding IM account (the file you edited in Specify IM Accounts)
- Click the start button to tell your gateway instance to connect to the IM service
The following table describes the instant messaging event gateway types available within JBuddy-CF.
Type Name |
Description |
Java Class |
Startup Timeout |
Kill on Startup Timeout |
AIM |
AIM event gateway |
com.zion.jbuddycf.AIMGateway |
60 |
enabled |
ICQ |
ICQ event gateway |
com.zion.jbuddycf.ICQGateway |
60 |
enabled |
MSN |
MSN Messenger event gateway |
com.zion.jbuddycf.MSNGateway |
60 |
enabled |
YIM |
Yahoo Messenger event gateway |
com.zion.jbuddycf.YIMGateway |
60 |
enabled |
JSC |
*JBuddy Message Server event gateway |
com.zion.jbuddycf.JSCGateway |
60 |
enabled |
*The JSC event gateway type allows ColdFusion to work with Zion's Enterprise Instant Messaging solution, JBuddy Message Server and is available as a separate product from Zion Software.
JBuddy, JBuddy-CF, JBuddy Message Server are trademarks of Zion Software, LLC. AIM, ICQ and AOL Instant Messenger Service are service marks of America Online, Inc. MSN Messenger is a registered trademark of Microsoft Corporation. Yahoo Messenger is a registered trademark of Yahoo! Inc. All other trademarks are the property of their respective owners.