Friday, February 14, 2014

Port Numbers Used in an OBIEE 11g Installation and Configuration

The goal of this post is to provide information regarding the ports used in an OBIEE installation and configuration; which include:
  • Default ports;
  • How to review the configuration files to list currently configured ports;
  • How to determine active ports on Windows and Unix\Linux;
  • Table that can be used as a reference; and
  • Documentation references.
Ports are used in a typical installation and configuration. You can use the default ports or set up custom ports to use whatever you want in your specific environment.
Below is some general information related to OBIEE Ports:

Default Ports:

According to the graphic below, please note that the port numbers shown are the default port numbers for a simple installation with one component of each component type on a single machine.

OBIEE Architcture

How to review the configuration files to list currently configured ports?

$OH/install/ports.properties:  This file will contain the list of OBIEE system component ports assigned at the time of installation; however, these ports may have been changed after installation.

The following configuration files will list your currently configured ports:

  • Weblogic Administration and Managed server, node manager: [middleware_home]/user_projects/domains/bifoundation_domain/config/config.xml
  • OPMN: [middleware_home]/instances/instance1/config/OPMN/opmn/opmn.xml
  • OBIEE System Components: [middleware_home]/user_projects/domains/bifoundation_domain/config/fmwconfig/biee-domain.xml

How to determine Active Ports?

  • Unix/Linux: 

    You can use the following command line:

    netstat -tulpn 
    or
    netstat --tcp --udp --listening --programs -n

    This will list tcp/udp protocols that are listening as  well as the process id and program.

    You may also use other filters as you desire, please see the netstat manual pages for details.

    Some additional examples:

    netstat -tuapn | grep <port>
    netstat -tuapn | grep 'nqs*'
    netstat -tuapn | grep 'sawserver'
    netstat -tuapn | grep 'java'  

    note for java, you may need to further refine by using ps -ef | grep <PID> to see what is running in java (i.e. weblogic adminserver, weblogic managed server, javahost)


  • Windows:

    You can use the following command line:

    nestat -bo

    or

    use Task Manager (for task manager it is helpful to click on the processes tab, then view > select columns and chose: 'command line' -- this allows you to see the executable as well as the Process ID)

    For example:


    Task Manager example



Port Number Reference Table

In addition, the table below also provides general information on port numbers; however; please use it as a reference and do not take the list below as the FULL list. 
Port Number:
In/Out
 Target:
 7
 I/O
 Necessary for TCP communications during scale-out
 80 (or 443)  
 I
 Standard HTTP Server (encrypted) access
 389 (or 636)
 I
 LDAP (SSL)
 1521
 I/O
 Oracle Database default OCI/TNS port
 9556
 I/O
 Node Manager
 7777
 I/O
 Oracle HTTP Server defaul port ( if used)
 7001
 I/O
 Weblogic AdminServer default port
 6021
 I
 Access Server
 6022
 I
 Identity Server
 6701
 O
 OPMN TCP port
 7779
 I
 OPMN HTTP port
 9700
 I/O
 Cluster Controller Monitor
 9701
 I/O
 OBIEE Server Monitor Client (only used when clustered)
 9703
 I/O
 OBIEE Server
 9704
 I
 Web server host port
 9705
 I
 Scheduler
 9706
 I/O
 Cluster Controller Client
 9707
 I
 Scheduler Script Engine (if used)
9708
I/O
Scheduler Cluster Monitor port
9710
I/O
Presentation Server
9810
I
(Presentation Server) Java Host
9991
I/O
JOC for OWSM
1521
I/O
Database access via SQL*Net

Documentation References:


No comments:

Post a Comment