Bug 781135 (SOA-3634) - Document which ports are used by the SOA platform
Summary: Document which ports are used by the SOA platform
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: SOA-3634
Product: JBoss Enterprise SOA Platform 5
Classification: JBoss
Component: Documentation
Version: 5.0.2
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: FUTURE
Assignee: David Le Sage
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-11-29 17:04 UTC by Len DiMaggio
Modified: 2014-01-31 05:30 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-01-31 05:30:03 UTC
Type: Task


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 779963 1 None None None 2021-01-20 06:05:38 UTC
Red Hat Issue Tracker SOA-3634 0 Major Closed Document which ports are used by the SOA platform 2014-01-31 05:30:09 UTC

Internal Links: 779963

Description Len DiMaggio 2011-11-29 17:04:49 UTC
Help Desk Ticket Reference: https://na7.salesforce.com/500A0000003jwJT
project_key: SOA

EAP already provides a list of open ports in the docs:
4.3 -> http://docs.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/4.3/html/Server_Configuration_Guide/Security_on_JBoss-Configuring_JBoss_for_use_Behind_a_Firewall.html
5.0 -> not documented (see https://jira.jboss.org/browse/JBPAPP-3460)
5.1 -> Security Guide (staging: http://documentation-stage.bne.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/5/html/Security_Guide/chap-Firewalls.html)

Any ports additionally used by the SOA platform should be documented. At least jUDDI adds one (which is currently random), see the following JIRAs:
4.3 -> https://jira.jboss.org/browse/SOA-2047
5.0 -> https://issues.apache.org/jira/browse/JUDDI-386 (fixed in JBossESB 4.9 which is the foundation of SOA-P 5.1)

Comment 1 Len DiMaggio 2011-11-29 17:04:49 UTC
Link: Added: This issue Cloned from SOA-2323



Note You need to log in before you can comment on or make changes to this bug.