Can't we develop a BO Java sdk tool in a local machine which does not have BO installed in it?

[kamalessh]

Hi all,

     We are currently developing a tool using BO Java SDK. For the past one month we worked in the server in which BO and net beans were installed. We didn't face any issues. This week we have started our development  work from a local machine which doesn't have BO by copying the necessary jar files to our local machine. What happen was we are getting the following error and we couldn't rectify it till now.

     Could not reach CMS '10.152.140.145'. Specify the correct host and port and check for network issues. (FWM 20030)

Kindly need some help on this issue.

Thanks,

Kamalessh

[Former Member · Accepted solution]

Hi kamalesshwaren,

Its is possible.

Do host file entries on your local machine and specify BO server ip adress and hostname.

You would also need to consider if there is a firewall(also consider network firewall) blocking out requests to Bo server coming from your local machine.

Thanks,

Prithvi

[kamalessh · Accepted solution]

Hi Prithvi,

            Could you please tell me how to do host file entries in local machine.

Thanks,

Kamalessh

[Former Member · Accepted solution]

Asumming you local machine to be windows

C:\Windows\System32\drivers\etc\hosts

Edit the file and add the below entries

BOServerIP     BOServerHostName

Save the file and re-try connecting.

Thanks,

Prithvi

[kamalessh · Accepted solution]

Hi Prithvi,

     Thanks a lot. The issue has been resolved and it is working fine now

Thanks,

Kamalessh.

[Former Member]

Hi Kamalesh,

As suggested by Prthvi, the host file entry should resolve your issue. However, if somehow it doesn't work you can try adding the request port to each CMS server as follows:

- Open CCM. Stop the Server Intelligent Agent (SIA). Select SIA Properties. Go to Start-up tab. Select each CMS listed, local and remote. Select properties. Add the following to the command line of each CMS.

-requestport:<port>

Apply the changes. Start the SIA.

This will register the service provider with the service locator with its fully qualified domain name and will listen for requests on the specified port.

What basically happens is:

When you logon from your Java SDK application you specify the fully qualified domain name to the CMS server because the CMS server stands on different domain. The logon call immediately errors out but error shows that server lookup is done using server shortname.

The CMS has two main purposes: one is as a service locator, and the other as a service provider. The service locator (port 6400 by default) is there essentially to redirect requests to the appropriate server. The service provider actually provides the CMS service (such as InfoStore) and it is by default on a port selected randomly by the OS (You can force the service provider to use a specific port using -requestport in the CMS command line options).

When the logon call is made it is actually the CMS service locator that is passed in the logon method call. That goes through fine. CMS service locator then sends back a list of all CMS service providers available on the system. But the CMS service provider by default registers itself with the service locator using its shortname. So the service locator sends all the CMS service providers to the SDK but the host name is its shortname. The SDK receives the CMS shortnames. It randomly selects one of them to log on. But since it is shortname, it does a hostname lookup. The BO server is on a different domain therefore the DNS lookup fails, since shortname to a different domain is not registered.

Hope this helps.

Regards,
Rajarsh

[kamalessh]

Hi Rajarsh,

     I was able to technically understand the problem I faced. Thanks a lot.

Thanks,

Kamalessh.