SLX Mobile Client

[LEsposito]

We are considering implementing SLX Mobile for about a dozen SLX users (some LAN, some remotes) with BBs on our BES server.
Is 5.6 the recommended version or should we go with 5.5?
Would it be unwise to add SLX Mobile Server to the same VM that our SLX Server and Sync Server are currently on?
Did I understand the Implementation Doc correctly that we will have to add a Mobile SQL database to our SQL Server?
Is implementation fairly straightforward or should we be prepared to engage some support? (p.s. we're pretty good - thanks to you, of course )
Is it more appropriate to look to Sage or to our BP for "free" mobile implementation support (i.e. answers to our questions)?
Is anyone familiar with a Mobile Resource Kit discussed in the Sage Journal?
Are there any gotcha's or mobile hassles that we should be on the lookout for?
Is the Mobile server fairly reliable or will our users be unable to sync every now and then?
Should we have done this a long time ago?

We are currently on SLX 7.2.2 and SQL 2000. We have about 80 LAN users, 40 remotes and a few dozen concurrent users, mostly Citrix. We run our SalesLogix and Sync servers on the same VM box. We don't have an overly active CRM community - our sync server runs every 2 hours for about 1 minute. While we have thousands of Accounts and ten thousand plus Contacts, only a few hundred are actively updated.

Thanks,
Larry Esposito

[RJLedger]

A - 5.6 w/HF1 - you have to go with this IF you want to use ANY BB's that use OS5.0 - or if you want to use Tour(s) and Storm2 (or Storm1 w/5.0)

B - You can mix them..

C - Yes, there is a mobile "DB" that contains some mobile info (config, etc) along with the fact it will also be modifying your production SalesLogix db (tables added, plus a SQL trigger).

D - "free" install setup !?! If you have M&S you can get normal Tech Support - don't know about your BP but we always charge extra to install/config/support mobile.

E -  Mobile Resource Kit ?

F - W/a BES (BB's only of course) - Synch is completely automatic - use does not have to do anything

G - There are a bunch of little gotcha's and you should work w/someone:

           1 - to help in installation planning - every install is unique

           2 - to help in actual installation

           3 - to tell you that you will probably run into an issue or two as you go thru it - and you will.

H - Otherwise - a piece of cake ;-)

FYI: There is an Mobile Engineer's course at SageU on Mobile.. It's something you should take. It has nothing to do w/Mobile customization - for that you will have to learn java (not JS - java). REad every bit of the supplied documentation forwards and backward before proceeding with anything - including any planning - then consult w/someone who has done installs.

[LEsposito]

Thanks RJ. Do you have many Clients that use the Mobile Technology? And on average, on a scale from 1 to 5 (best), how much would you say that they like it?

Thanks again,
Larry Esposito

[RJLedger]

We have a few. We have also implemented mobile for other BP's clients (not everyone has mobile certification.. nor wants to get into it).

On usage, we have a client really likes it. He has all his customers at his finger tips (he also uses Saleslogix Windows Remote) and that meets his needs 100%. Mobile fits into that place where you have people on the move that need that access all the time.

Every mobile install I've been involved with is BB based (some with BES, some without - Contrary to popular belief, you do NOT need a BES for BB - just for the auto-realtimesync). Not a single one is PPC or Smartphone.

Commercial: SalesLogix Mobile is a good buy - especially if you have SalesLogix Premier Edition ;-).

Message Edited by RJLedger on 03-15-2010 11:39 AM

[LEsposito]

That's valuable input and a promising commercial

Thanks again!
Larry Esposito

[LEsposito]

We will be implementing the SLX Mobile Enterprise Server (5.6) with our BES and wireless (only) BBs to communicate with our SLX 7.2.2 database (SQL 2000). Requirements demand additional resources and considerations from our IT support including:
1. Implement SLX Mobile Enterprise Server on a separate VM
2. Implement Mobile Deployment DB on SQL 2005 server
3. Upgrade our SLX 7.2.2 DB from SQL 2000 to SQL 2005
4. Implement Web Server (on the same box as the Mobile Enterprise Server?)

Because of our current internal server support model/budget these could potentially become show stoppers, especially the latter 2. Can anyone easily explain the need for the Web Server? Does BES only speak HTTP to BBs and our Intranet? My concern is that a Web Server may introduce security ramifications that stress our SLX needs from IT.

Thanks,
Larry Esposito

[RJLedger]

The BES only provides "Real-Time" data push TO the BB's - All else is via the Mobile Web server (including the Mobile App download/updates).

You have no choice on this. It's how it works.

[LEsposito]

Ugh! And with the upgrade to SQL 2005 we will probably migrate our 50 Global Remote Users from MSDE to SQL Express (actually I think we have to), not to mention getting another 50+ LAN Clients updated with SQL Native Client (I believe this is covered with the SQL Express install for remotes). Wow, we pull on this little mobile thread and the whole thing begins to unravel. Let me go back to the part where he said "Piece of cake" ;-)

Thanks again,
Larry

[LEsposito]

We are still trying mitigate additional internal costs mentioned earlier. As luck would have it, we are currently being moved to a SQL 2005 Server in SQL 2000 compatibility mode.

Is there any chance that this would meet the SQL 2005 requirement for SLX Mobile 5.6?
And, how much pain can be expected in making the needed changes to completely eliminate the need for the backward compatibility?

Thanks,
Larry

[RJLedger]

You will be fine.

SLX Mobile installs it's own db to hold config data, etc. This can be in a SQLExpress db or in the "main". It also creates tables IN the SalesLogix db that it needs as well.