B1if setup for SAP B1 9.1 HANA version

[Former Member]

Hello Experts,

I am unable to do B1if setup in SAP B1 9.1 HANA verion. If any body share with me the complete setup manual, it will be really helpful for me.

Thanks,

Tapojyoti

[thiago]

Hi Tapojyoti Das,

Try to change your B1i user password on Business One: Administration > Setup > General > Users and set the same password on B1if SLD > B1i Server > [database] > [B1i password].

Regards,

Thiago.

[bastian_schaefer]

Hi,

isn't there a setup guide included in the installer package of the integration framework?

At the moment the Integration Framework of SAP Business One needs to be installed on a separate windows server. The Integration Framework uses the HANA database remotely for its own data.

The reason is the following: At the moment the DI API - which is a prerequisite for the automated scenario and landscape setup - is running on windows only.

Best regards

Bastian

P.S.:

Optionally you can think about the standalone versions "Integration Framework for SMEs" or "SAP Business One Integration for SAP Netweaver (B1iSN)" for a complete installation on Linux.

The DI API still needs to be installed on a separate windows machine.

[Former Member]

Hi Bastian,

I have done the setup on separate windows machine only. But when doing test connection of B1DI getting the following error.

Do you have any idea how to resolve it?

Thanks.

[bastian_schaefer]

Hi,

please first check if a local and correct DI API version is installed on the B1i/Windows server.

In the DI Proxy, there need to be a reference to the locally installed DI API version: Please edit file \SAP\SAP Business One Integration\DIProxy\diproxyserver.properties and check parameter JCOPATH.

In SLD the parameters diProxyhost and diProxyport need to be maintained.

Is your JDBC test connection successful?

Best regards

P.S.:

The HANA server is case-sensitive, please enter the exact name of the sever in SLD Parameter b1Server or switch if possible to the HANA server's IP address.

If the connection can be tested successfully after these changes, please also align the EventSender setup.

[Former Member]

Hi,

I have checked DI API version and it is perfect.

I have also mentioned the diProxyhost and diProxyport.

JDBC test connection is successful. But getting the same error again and again.

Thanks.

[bastian_schaefer]

Hi,

is the DIProxy component installed and the service running as well?

Is default port 2099 free and not blocked by any firewall?

Please attach a screenshot of your SLD entries and also one from your settings in DIProxy configuration file (..\SAP\SAP Business One Integration\DIProxy\diproxyserver.properties).

Best regards

Bastian

[Former Member]

Hi,

DIProxy component is installed and service is running. Port 2099 is free and firewall is off.

SLD screen shot

DIProxy Configuration file

# Specify the TCP listening port used by DI-Proxy, 1099 will be used by default if not value provided.

# BACKWARD-COMPATIBILITY FALLBACK ONLY IF HTTPS_PORT IS MISSING, OTHERWISE, IT GETS IGNORED !!!

#RMI_PORT=2099

# The HTTPS-Port used for the server

HTTPS_PORT=2099

# If this property exists and is set to a value > 0, the value depicts the count of DI-errors that may happen until the

# DI-Proxy will be restarted for the sake of potential memory leaking. The default is 0(no restart).

MAXDIERRORS=50

# If this property exists and is set to a value > 0, the value depicts the time in minutes when the DI-proxy will be

# restarted for the sake of potential memory leaking. The default is 0(no restart).

RESTARTPERIOD=60

# The value in minutes when a pendig and not yet completed DI-transaction is deemed as orphaned and therefore will

# be cleant out of the internal transaction-list.

# If this property is not specified or has not a positive value, a default of 20 is taken.

ORPHANED=20

# The upper count of granted simultaneous pending accesses to the adapter (0 = no limit).

MAXACCESSES=0

# The upper count of DI-connections in maximum kept open at the same time (0 = no limit).

# Note that there happens an adjustment of the maximal granted simultaneous accesses so that it does not exceed the maximal granted connections!

MAXCONNECTIONS=0

# If this property exists and is set to 'false', overlapping / parallel transaction(-sequence) processing-requests to one company database are allowed.

# If omitted or set to 'true', only one transaction(-sequence) may be pending at a given point in time. Additional ones in turn will be rejected.

SINGLECOMPANY=true

# If this property exists and is not empty, it specifies the path the DI-proxy uses to search for the JCO installation.

# In this case, a potentially sent over value from B1iP on an adapter-request will be ignored then.

# Otherwise, if the property is not specified, the value sent over from B1iP on an adapter-request will be used, what

# can get ambigious if distinct requests contain distinct settings.

# Note that Using '/' or '\\' instead of '\' as seperator in the value of JCOPATH, otherwise an error will encounter

# e.g. C:\\Program Files\\SAP\\SAP Business One DI API\\JCO\\LIB

JCOPATH=C:\\Program Files\\SAP\\SAP Business One DI API\\JCO\\LIB

# If this property exists and is not empty, it specifies the version the DI-proxy uses to search for the JCO installation.

# In this case, a potentially sent over value from B1iP on an adapter-request will be ignored then.

# Otherwise, if the property is not specified, the value sent over from B1iP on an adapter-request will be used, what

# can get ambigious if distinct requests contain distinct settings.

# If no value at all is specified here or sent over on an adapter-request, the default of 'jcov2005' is taken.

JCOVERSION=

# Registers external, loadable DI-JCO implementations, where the single components mean

#

# <jarfile>   := the name of the implementation's .jar-file w/o extention

# <classname> := The class that supplies the particular implementation

#

# DIJCO.<jarfile>=<classname>

#

# Note that the whole key / value pair is case-sensitive!

# E.g. the example below depicts the syntax that would be used for the inbuilt (and inreplacable) DI-JCO implementation:

# DIJCO.B1iPDIAdapter=com.sap.b1i.adapter.dia.ConcreteDIJCO

#

# There can be registered as many distinct implementations as required.

# Note that the particular .jar-files have to exist in the DI-Proxy's base-directory in order to get found!

Thanks.

[bastian_schaefer]

Hi,

please leave SLD parameter jcoPath empty; the value will be read from file diproxyserver.properties.

I assume 192.168.0.82 is the correct ip address of your B1i/Windows server, where the DI API and the DI Proxy are installed.

Did you check your b1server "TAPOJYOTI-PC" for case-sensivity?

Is this exactly the name of the HANA database server?

Best regards
Bastian

[Former Member]

Hi,

The ip is correct. I have shared with you all the details of SQL DB not HANA. But I am getting same error in SQL and as well as HANA.

b1server "TAPOJYOTI-PC" is correct.

Thanks.

[bastian_schaefer]

... please carefully check the following SAPNote step-by-step: 2029714 - Troubleshooting integration framework SLD DI connection (http://service.sap.com/sap/support/notes/2029714)

Best regards

Bastian

[Former Member]

Hi,

Follow all the steps but still the same error coming.

Thanks.

[Former Member]

Hi there,

I'am confronted with the same problem, could anybody describe how to setup B1if for SAP B1 9.1 Hana and what requirements are necessary?

Thank you,

Patrick