cancel
Showing results for 
Search instead for 
Did you mean: 

SAP BODS 4.1 Designer port issue

Former Member
0 Kudos

Dear experts,


While trying to connect from Designer getting Logon failed issue. Job server has been running on Linux and there is some firewall between client and server.


After installation, Designer connected success fully(First time) and executed some jobs; then re-started the job server and try to connecting from Designer but it got failed. Then we identified designer port has blocked by firewall; we opened the port with the help of network team and added same port in designer ( tools --> options as attached), initially it was working fine; today again re-started the job server but getting same issue.


Version : BODS 4.1 SP2

Any ideas what I can do to get this to work?

Thanks in advance

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Thank you so much to all,

The issue got fixed; here the dynamic port is nothing but the CMS request port (default, the port will change after re-starting the BO services). We identified the request port with below steps:

i) Identified the port which was trying to connect from client (with the help of network team)

ii)Identified the  application, which is running on particular port ($ netstat -tulpn | grep : <port>)

Need to make this as a static port by using <%IPS installation dir %> / sap_bobj/serverconfig.sh or

CMC (Servers  -->  Core Services  -->  right click on CMS  -->  properties -->  Request port(Common Settings) -->   Un check auto assign --> enter unused port and same port need to be open on firewall)

Restart the Services.

Thank You,
Tirupal

DayaJha
Active Contributor
0 Kudos

Hi Tirupal,

Can you please share the screen shot of CMC properties page where you changed the common setting configuration i am facing the same issue in few server. Already i checked all SNotes still same issue.

Thanks,

Daya

Former Member
0 Kudos

Hi Daya,

I have trailed couple of times to attach the screenshot but was unable to upload image (.png) and will attach later.

Anyhow, the option is available in CMC --- >Servers -- > Core Services -- > CMS --> Right click-- > Request port (Common Settings) --> uncheck Auto Assign --> use some unused port as a Request port.

Regards,
Tirupal

Former Member
0 Kudos

Hi Daya,

   Sorry for delay reply(went on leave). I hope ur issue got resolved.

   PFA

Regards,

Tirupal

0 Kudos

Hi,

I have done above configuration for my Development server to sort out Designer Issues. After changing configuration as per above I restarted the services, After that CMC was not started. It gives below error.

Message was edited by: Rajesh Sanwatsarkar Account information not recognized: Could not reach CMS 'Servername:6400'. Specify the correct host and port and check for network issues. (FWM 20030)

0 Kudos

On Common Settings --> I uncheck Auto Assign and there Request Port - 6400 I mentioned.

Also On Name Server Port -- 6400 : I mentioned same Value..

It Happens By Mistake. So Please guide me How can I Revert back the settings ?

Thanks in Advance..

Best Regards,

Rajesh

Former Member
0 Kudos

Hi Sasidhar,

There is a different way to change the CMS port number.

refer to the following KBA for the same:

http://service.sap.com/sap/support/notes/1785724 - BI 4.0 - CMS does not start up after setting the request port

"The solution is to manually edit the bootstrap file and modify the requestport for one which is free on the Operating System."

Regards,

Dwi

Answers (5)

Answers (5)

Former Member
0 Kudos

Hi Tirupal,

Use TELNET to test that combination of host (name) and port number is actually accessible from the Data Services Designer Windows machine. If host (name) does not resolve to a correct IP address, it may be necessary to update the computer's hosts file. On Windows NT machines, this is found in the %SystemRoot%\system32\drivers\etc\hosts directory.

Also try the below steps:

1) From the Designer machine open a command-line prompt and type 'telnet <jobserver_machine> <jobserver_port>'. You should be able to open a telnet session successfully (basically a blank/black screen). If you get booted out that means that there is something on your network that is preventing the communication.


2) If the test above is successful and you can connect successfully then the next step is to ensure that from your Job Server machine you can successfully connect to the machine and ports that the Designer is listening to. By default the Designer determines it's own port (any port above 1024 can be grabbed), so to be able to test this you need to:

  1. In the Designer click on 'Tools - Options', then select 'Designer - Environment.
  2. Un-check 'Allow Designer to set the port for Job Server communication' and set a specific port (i.e. 3510 - the same port in both range-start and range-end slots).
  3. Hit OK, restart Designer.
  4. On the machine where your Job Server is installed open a command-line/shell prompt and type in 'telnet <Desginer_machine_name> <Designer_port>'. Can you establish a telnet session in this direction (Job Server machine to Designer machine)?

One of these two tests will likely fail. Once you know which one, then you can continue to work with your IT department or network team to resolve this issue.


Thanks,

M.Sumesh

Former Member
0 Kudos

Try creating a new "Inbound Rule" in the Windows Firewall Advanced Security Screen.

Navigate to the Control Panel > Windows Firewall and choose the "Advanced Settings" option on the left pane.

You should see this screen when you open.

On the right pane, follow the the "New Rule" Wizard to create an Inbound Rule for the Data Services Designer exe.

Thanks,

John

Former Member
0 Kudos

Hi John,

Thanks for reply, I hope above setting need to apply  in client side(windows), what about job server (Linux) settings as same port  should be in listening status in server.

Thank you,

Tirupal

DayaJha
Active Contributor
0 Kudos

Please share the jobserver serverevent logs generated in your job server directory.

For logs path please refer below thread.

Link:

http://scn.sap.com/thread/3457272

Thanks,

Daya

Former Member
0 Kudos

Hi Daya,

I did not find anything about Client-server port info in server event log ;Please find below :

(14.1) 11-21-13 00:12:50 (1919:1211758912) JobServer:  Cleaning job server log files older than 30 days. (BODI-850278)

(14.1) 11-21-13 01:12:50 (1919:1211758912) JobServer:  Cleaning job server log files older than 30 days. (BODI-850278)

(14.1) 11-21-13 02:12:50 (1919:1211758912) JobServer:  Cleaning job server log files older than 30 days. (BODI-850278)

(14.1) 11-21-13 03:12:50 (1919:1211758912) JobServer:  Cleaning job server log files older than 30 days. (BODI-850278)

(14.1) 11-21-13 04:12:50 (1919:1211758912) JobServer:  Cleaning job server log files older than 30 days. (BODI-850278)

(14.1) 11-21-13 05:12:50 (1919:1211758912) JobServer:  Cleaning job server log files older than 30 days. (BODI-850278)

(14.1) 11-21-13 06:12:50 (1919:1211758912) JobServer:  Cleaning job server log files older than 30 days. (BODI-850278)

(14.1) 11-21-13 07:12:50 (1919:1211758912) JobServer:  Cleaning job server log files older than 30 days. (BODI-850278)

(14.1) 11-21-13 08:12:49 (1919:1211758912) JobServer:  Cleaning job server log files older than 30 days. (BODI-850278)

(14.1) 11-21-13 09:12:50 (1919:1211758912) JobServer:  Cleaning job server log files older than 30 days. (BODI-850278)

(14.1) 11-21-13 09:42:52 (1919:1132304912) JobServer:  JobServer shutting down... (BODI-850006)

(14.1) 11-21-13 09:42:52 (1919:1132304912) JobServer:  Stopping jobs... (BODI-850007)

(14.1) 11-21-13 09:42:52 (1919:1132304912) JobServer:  AdapterManager stopped (BODI-850020)

(14.1) 11-21-13 09:42:52 (1919:1132304912) JobServer:  MessageBroker stopped (BODI-850021)

(14.1) 11-21-13 09:42:52 (1919:1132304912) JobServer:  Waiting to process all pending requests <0>. (BODI-850262)

(14.1) 11-21-13 09:42:52 (1919:1132304912) JobServer:  Completed processing all pending requests. (BODI-850263)

(14.1) 11-21-13 09:43:01 (4936:3584891408) JobServer:  -------------------------------------------------- (BODI-850035)

(14.1) 11-21-13 09:43:01 (4936:3584891408) JobServer:  Job Server Started... (BODI-850036)

(14.1) 11-21-13 09:43:01 (4936:3584891408) JobServer:  Job server uses <300+3> threads for processing and can handle requests from only <50> Data Integrator Designer applications.

                                                      The number of threads does not include threads necessary for adapter, SNMP and load balance processing. (BODI-850277)

(14.1) 11-21-13 09:43:01 (4936:3584891408) JobServer:  WARNING:  This JS will therefore NOT support SNMP (BODI-850038)

(14.1) 11-21-13 09:43:01 (4936:3584891408) JobServer:  Binding server to address inet:3500. (BODI-850044)

(14.1) 11-21-13 09:43:01 (4936:3661064512) JobServer:  Thread pool size for processing log file requests set to <100>. (BODI-850271)

(14.1) 11-21-13 09:43:01 (4936:3584891408) JobServer:  Listening on ANY:3500. (BODI-850157)

(14.1) 11-21-13 09:43:01 (4936:3584891408) JobServer:  Thread pool size for processing incoming requests set to <100>. (BODI-850276)

(14.1) 11-21-13 09:43:01 (4936:3584891408) JobServer:  Neither Message Broker, Adapter Manager, nor SNMP MB Server started. (BODI-850043)

(14.1) 11-21-13 09:43:02 (4936:3695814976) JobServer:  End Reading ServerGroup Information from Repository <odsuat__BODS>. (BODI-850154)

(14.1) 11-21-13 09:43:02 (4936:3695814976) JobServer:  Job Server is not part of Server Group. Server Group functionalities are disabled (BODI-850211)

(14.1) 11-21-13 09:43:12 (1919:1132304912) JobServer:  JobServer stopped (BODI-850005)

(14.1) 11-21-13 09:45:12 (4936:3664345408) JobServer:  Cleaning job server log files older than 30 days. (BODI-850278)

(14.1) 11-21-13 09:46:04 (4936:3584891408) JobServer:  JobServer shutting down... (BODI-850006)

(14.1) 11-21-13 09:46:04 (4936:3584891408) JobServer:  Stopping jobs... (BODI-850007)

(14.1) 11-21-13 09:46:04 (4936:3584891408) JobServer:  AdapterManager stopped (BODI-850020)

(14.1) 11-21-13 09:46:04 (4936:3584891408) JobServer:  MessageBroker stopped (BODI-850021)

(14.1) 11-21-13 09:46:04 (4936:3584891408) JobServer:  Waiting to process all pending requests <0>. (BODI-850262)

(14.1) 11-21-13 09:46:04 (4936:3584891408) JobServer:  Completed processing all pending requests. (BODI-850263)

(14.1) 11-21-13 09:46:08 (6627:51943952) JobServer:  -------------------------------------------------- (BODI-850035)

(14.1) 11-21-13 09:46:08 (6627:51943952) JobServer:  Job Server Started... (BODI-850036)

(14.1) 11-21-13 09:46:08 (6627:51943952) JobServer:  Job server uses <300+3> threads for processing and can handle requests from only <50> Data Integrator Designer applications.

                                                    The number of threads does not include threads necessary for adapter, SNMP and load balance processing. (BODI-850277)

(14.1) 11-21-13 09:46:08 (6627:51943952) JobServer:  WARNING:  This JS will therefore NOT support SNMP (BODI-850038)

(14.1) 11-21-13 09:46:08 (6627:51943952) JobServer:  Binding server to address inet:3500. (BODI-850044)

(14.1) 11-21-13 09:46:08 (6627:128117056) JobServer:  Thread pool size for processing log file requests set to <100>. (BODI-850271)

(14.1) 11-21-13 09:46:08 (6627:51943952) JobServer:  Listening on ANY:3500. (BODI-850157)

(14.1) 11-21-13 09:46:08 (6627:51943952) JobServer:  Thread pool size for processing incoming requests set to <100>. (BODI-850276)

(14.1) 11-21-13 09:46:08 (6627:51943952) JobServer:  Neither Message Broker, Adapter Manager, nor SNMP MB Server started. (BODI-850043)

(14.1) 11-21-13 09:46:09 (6627:162859328) JobServer:  End Reading ServerGroup Information from Repository <XXXX__BODS>. (BODI-850154)

(14.1) 11-21-13 09:46:09 (6627:162859328) JobServer:  Job Server is not part of Server Group. Server Group functionalities are disabled (BODI-850211)

(14.1) 11-21-13 09:46:31 (4936:3584891408) JobServer:  JobServer stopped (BODI-850005)

(14.1) 11-21-13 10:32:21 (6627:131389760) JobServer:  Cleaning job server log files older than 30 days. (BODI-850278)

(14.1) 11-21-13 10:39:18 (6627:131389760) JobServer:  Cleaning job server log files older than 30 days. (BODI-850278)

(14.1) 11-21-13 11:39:16 (6627:131389760) JobServer:  Cleaning job server log files older than 30 days. (BODI-850278)

Please let me know,  from where we can get the information about Designer ports info in Job Server.

Thank you,

Tirupal

DayaJha
Active Contributor
0 Kudos

In logs nothing was mentioned about Job server issue.

Can you please check below points in your server and client machine:

  • Ports needs to open for BODS:
    • 2.4.1.1 Port requirements for Data Services server components

This section lists the communication ports used by Data Services server components. If you deploy

Data Services with firewalls, you can use this information to open the minimum number of ports in those firewalls.

    • 2.4.1.2 Port requirements for Data Services client applications

This section lists the communication ports used by Data Services client applications and web applications.

If you deploy Data Services with firewalls, you can use this information to open the minimum number of ports in those firewalls.

  

Note:

• Use the Central Management Console (CMC) to configure a fixed CMS request port.

For more information, see “Server Administration, Configuring server network settings, configuring port numbers” the BI platform Administrator Guide or the Information platform services Administrator Guide.

• Use the Designer to configure fixed debugger and Job Server request ports.

Please refer below link for more details

Links:

https://help.sap.com/businessobject/product_guides/sbods42/en/ds_42_install_win_en.pdf

  • Share the Job server configuration status and BODS Designer Job server status.
  • Change the Designer communication port to 3500 to 3510, And check these ports should be open.

For more details about Job server Issue please refer below SNotes and Links

Notification Server Error BODI-1241023:

1817745 - Can not Submit Job at DS Designer 4.1
Link:

https://service.sap.com/sap/support/notes/1817745

1182587 - Error: The job server you selected is not working - Data Services
Link:

https://service.sap.com/sap/support/notes/1817745

Notification server error (BODI-1241023)
Link:

http://www.forumtopics.com/busobj/viewtopic.php?p=922987

1416303 - Can't reach Job Server from DS Designer
Link:

https://service.sap.com/sap/support/notes/1416303

Thanks,

Daya

Former Member
0 Kudos

Thank you so much for valuable information.

We already opened required ports (CMC – 6400, Tomcat – 28080, Job Server – 3500) in firewall; even we were able to execute the jobs before re-start the job server from Designer and now able to connect CMC and management console only problem with designer.

The Designer was connecting with port: 49429 and opened same port in firewall, then we re-started the job server the designer trying to connect with some other port: 11546, Now the port 11546 in listening status in Linux but not 49429 (now the designer will work if we open the port: 11546 in firewall).

It seems  every time the listening port is changing; instead of dynamic port   how we can make it as a static port (this static port will be opened in firewall to make a connection between designer and server)

Thank You,
Tirupal

DayaJha
Active Contributor
0 Kudos

Please refer the below thread.

Link:
http://scn.sap.com/thread/3413670

http://scn.sap.com/thread/2069028

Thanks,
Daya

former_member211387
Contributor
0 Kudos

Hi Tirupal,

Is your BOE cmc on SQL Server using the SQL Server Express set-up? The dynamic port issue occurs with the CMC SQL Server installation listener port. Assuming that you are using SQL Server for the repository, set the TCP Dynamic Ports to blank in the SQL configuration editor.

The same applies to other database applications too. Depending on the database application the tool you select to disable dynamic ports will change but the concept is the same.

Raghu

Former Member
0 Kudos

Hi Raghu,

Thanks for reply,  CMS and BODS  local repositories in Oracle and  we are using same data base server with different schema   in BODI 11.5 and BOE R2; Both the  applications are working  fine.

Thank You,

Tirupal

former_member211387
Contributor
0 Kudos

Hi Tirupal,

Please can you confirm what exactly the error is?

Are you are having problem login to the SAP BODS designer 14.1 from your client machine?  or

Are you able to login to the SAP BODS Designer 14.1 from you client computer but unable to execute jobs?

Please let me know which one and I will let you know how to get over it.

kind regards

Raghu

Former Member
0 Kudos

Hi

I understand that every time you restart the server, the port has been changed automatically and then you cannot login into CMC from DS Designer?

Former Member
0 Kudos

Dear Raghu , Francisco

Yes, we are facing DS Designer  logon  issue, every time the request port has been changing because of this  the port is blocking by firewall(Job server in Linux  and Designer in Windows)

Thank You,

Tirupal

former_member211387
Contributor
0 Kudos

Hi Tirupal,

To resolve this create system DSN for the ORACLE database on your client pc/laptop. In the system DSN assign the port you prefer in the client configuration/Network Library Configuration and it will resolve the issue.

The document below provides information on a similar issue involving MS SQL Server.

http://scn.sap.com/docs/DOC-48886 This is an example you can use to create an ORACLE system DSN. Steps 6 and 7 show the network configuration and assigning the port.

There are numerous online resources explaining how to create ORACLE system dsn. One such link is http://kb.iu.edu/data/awqf.html

Also, check the tnsnames.ora file on your client computer. Make ensure that the port mentioned for the ORACLE database is the one you need.

kind regards

Raghu

Former Member
0 Kudos

You may need to add the IP addresses of your ETL server to the windows HOSTS file.

HOSTS file location is "C:\Windows\System32\drivers\etc".

aasavaribhave
Advisor
Advisor
0 Kudos

you get the SDK failure error when connecting to CMS , before it can load list of repositories for you to select 1.

make sure that from you can telnet to cms host on port 6400 or whatever port cms listens to from designer box.

try adding cms hostname, ip in hosts file on designer box.

Former Member
0 Kudos

Hi,

Added ip and host name in host file but no use

Thanks,

Tirupal