Nakamura-san,
You are correct. You do not need either gemfire.jar or sqlfabric.jar when you use the client jar.
There are some other changes I have made to that document for Alpha5 - the URLs no longer have 'gemfire:' in them.

Dave

David-san,

Thanks for your answer. It's clear.

I have a new question.
How can I get a logwriter of SQLF in my procedure?
I can get a logger by DistributedSystem.getLogWriter() when I use GemFire.
But I don't know how to get it in SQLF.

I'd appreciate it when you would answer to them in your free time.

Best Regards,
So

Your observation is correct. All you need is 'sqlfabricclient.jar' when connecting using the thin client driver.

There is currently no support for a LogWriter in SQLFabric user code. There is discussion about adding support for a logging interface in the context object that is supplied to the procedure as well as other Java callbacks as a java.util.logging.Logger.

Also, we are hoping to unify the sqlf log with the gemfire system log so there is only one log file.

I solved them by using "com.gemstone.gemfire.cache.CacheFactory.getAnyInstance().getLogger()" for now.
Thanks for your supports.