- Show Remaining Articles ( 36 ) Collapse Articles
BBj ODBC Driver
BASIS ODBC Driver (pre-BBj)
- Show Remaining Articles ( 31 ) Collapse Articles
- Show Remaining Articles ( 68 ) Collapse Articles
BBj Enterprise Manager
BASIC Web Utility
- Show Remaining Articles ( 41 ) Collapse Articles
- Show Remaining Articles ( 226 ) Collapse Articles
PRO/5 Data Server
- Show Remaining Articles ( 25 ) Collapse Articles
TAOS: The Developers Workbench
- Show Remaining Articles ( 101 ) Collapse Articles
Enterprise Manager Fails to Load
Since BBj 14.0, BBj’s Enterprise Manager conveniently runs directly in the browser or Eclipse EM Plugin of any system with network access to the server with the following URL:
For example, if you installed BBj on a server named bbjserver.example.com, with the default BBjServices Jetty port configured to 8888, then the Enterprise Manager URL would be the following:
If Enterprise Manager fails to load, below are some areas to check.
In order to connect to Enterprise Manager from a remote machine, the Jetty web server port 8888 and the BBj Admin port 2002* must be accessible to the connecting system.
A simple way to test port connectivity is to use the telnet client to connect to the remote server/port: telnet bbjserver.example.com 2002
*Note: Most BBj ports can be configured to different port numbers; 8888 and 2002 are the defaults for Jetty and Admin, respectively.
Any software package that runs on a port used by BBjServices will cause connectivity issues. LogMein, a remote connectivity service, often runs on port 2002.
Resolution 1: Configure LogMein to use a different port.
Resolution 2: Configure BBjServices to use a different port for the Admin server:
Edit <bbjhome>/cfg/BBj.properties; changing the port in this property to the desired port number: com.basis.server.admin.1.defaultPort=2002
Classpath Problems After Upgrade
In some upgrade cases, having a classpath that refers to a missing .jar file in BBj.properties can lead to problems in the upgrade process and an incomplete BBj.properties file.
For example, a BBj upgrade with the classpath property that references a .jar file that is not physically present in path specified, may cause the upgrade to fail and prevent Enterprise Manager from loading: