Hi
I struggled for a long time to get my B1Mobile app working with our SAP environment iPad. We run our SQL server on an instance (MachineName\Instance).
I also had the SQL server on a different port than 1433. If your SQL server is on a different port to 1433, I suggest that you change to be on the default 1433 port. Although you can get it working on a port other than 1433 there may be further issues that you will have to spend time on at a later stage of your implementation.
Here is my check list based on a working system after a few days of struggling.
- Forget about setting up the B1Mobile solution over an unsecured connection. I think it cannot be done. Why would you want to in any case if you can get it working securely without needing a certificate or anything else.
Ensure the following is correctly setup in the “Integration solution for SAP Business One”.- Open the “Integration solution for SAP Business One” in Internet Explorer (There are problems with other browsers) and login with B1iadmin.
- Go to Scenarios and then to Authentication. Your “Enforce Secure Transport” should be set to “True”.
- To check what ports you are running on, go to Maintenance and then to Cfg Runtime. My settings here are 8080 for Http, 8443 for Https and my MachineName (not ip) for B1iServer.
- Go to SLD, WSforMobile. I configured both WSAN and WSAS with “http” for destProtocol, “MachineName” for destHost and “basic” for authentication. The rest is blank. When I test the connection it returns a success. I am not sure if this makes a difference, but I far prefer success messages to error messages.
- VERY Important: At the bottom of the WSforMobile screen there is a setting that kept me busy for some time. It is called “associatedSrvIP”. I set mine to “MachineName\Instance”. In other words, this need to be your SQL server. I did not specify a database here, unlike many other documentation. Imagine a name for this setting that made sense.
- Then lastly you can see authentication logging under Monitoring, Authent. Monitor. It will not reach this log if the connection to your previous settings are incorrect.
- Some time ago, I also had issues with setting up my SLD for the company that I want to connect to from my mobile device. So just make sure these setting are right as well.
- Open the “Integration solution for SAP Business One” in Internet Explorer (There are problems with other browsers) and login with B1iadmin.
- Go to SLD. Your SBO company DB should be on the left. Click on it.
- The b1Server should be your SQL Server. If you have an instance, specify the “MachineName\Instance” here.
- Next enter your LicenceServer and port: “MachineName:30000”.
- Next enter the SBO Database name in “Company”.
- Enter the DB user and password (I normally setup a separate SQL user for this). I always test this SQL logon again before I enter it. Especially if you deploy on someone else’s machine.
- Next enter “B1i” in the username field and its password in the password field. I always test this details as well by logging into SAP with it. You cannot do mush, but it is a good test to see if the credentials are correct.
- Next I entered my MachineName into diProxyhost and 2099 in the diProxyport. This is the default. Yours might be different if you changed it during installation.
- The JDBC also need to be configured and need to test successful. My setting here is:
- driver: “com.microsoft.sqlserver.jdbc.SQLServerDriver”
- url: ‘jdbc:sqlserver://MachineName\Instance:1433;integratedSecurity=false;databaseName=SBODatabseName;selectMethod=cursor’
- username: SQL User name (could be ‘sa’)
- password: SQL password.
- Now there are some settings to check in your SAP Business One.
- Login with a super user account.
- Go to Administration, Setup, General, Users. Navigate to the user you are going to login with from your mobile device.
- Ensure that both the “Superuser” and “Mobile user” checkboxes are checked.
- In Mobile Phone, enter the full mobile number including the country code. No spaces. Example: “+27831231234”. If you use an iPad with no sim card, just enter any mobile number here. It must match later on when you enter it on you Mobile device. You also need to enter you Mac address in the “Mobile Device ID” field. Version 1.6.0 of the mobile application will tell you what to enter into this fields if you entered it wrong. Save the user’s details and OK out of the user screen.
- Go to, Administration, Licence, Licence Administration. Go to the user you want to use as the mobile user, and make sure he’s got the “Professional User”, and “B1i” License Types checked.
- Next we need to ensure that we have no network or blocked ports issues. On some wireless networks they block traffic on some ports. So ensure that the following works.
- I made sure my network connections are not the problem by pinging the mobile device’s IP address as well as opening a browser on the mobile device and typed in the following: https://IPaddressOfSAPServer:8443
- The browser will complain about the certificate. Just say continue. If you do not get the logon screen you know that you have communication issues that you need to solve before continuing. For a test you can switch of you local firewall. If your firewall is the problem, then add an exception rule on it.
- If you are able to ping your mobile device as well as get the login screen in the previous steps, go to settings, and then to “Business One” on your mobile device.
- Enter the same address as above but without the https:// Exsample: “10.10.10.145:8443”. Don’t forget the port. It has to be your secure port. I could not get it working on the non-secure port. Save yourself the time.
- Next, set SSL to ON.
- Specify the SBO SQL database name in Company DB, and enter the user that you configured in SBO earlier.
- Now enter the full mobile number including the country code. No spaces. Example: “+27831231234”. If you use an iPad with no sim card, just enter the same number here that you entered earlier in SBO.
- Set Demo System to OFF.
You should now be able to log into the mobile application with the password of the configured super user account.
Thanks,
Karl Basson (Genville Systems Development)
