Difference between revisions of "FAQ:Installation and Configuration"

Revision as of 16:56, 12 February 2015

[edit]

General
Network
Database

General

Where is the license file stored?

C:\Users\{Your Name}\AppData\LocalUBIKLicense.xml

Where can I find some logging information and configure its destination?

Read the article about configure logging to get to know the destinations of log files and how to modify them.

What if license activation fails with HTTP status 417: Expectation Failed.?

If the activation of UBIK^® fails with an error The request failed with HTTP status 417: Expectation Failed. make sure that the system.net section in your local UBIK.Studio.config.xml contains a servicePointManager entry similar as

<system.net>
<settings>
<servicePointManager expect100Continue="false" />
</settings>
</system.net>

Network

Can I use UBIK^® via an Application-Delivery-Solution, e.g. Citrix Reveiver?

No, that is not possible as such applications are mostly clients accessing a server based application pool. UBIK^® is a stand-alone mobile application, which does not communicate via such virtualization client.

Which ports are used by default?

Communication between the Server and Client uses 443 (https) or 80 (http). The authentication requires https always!
Microsoft SQL Server uses 1433 by default

Database

Does UBIK^® support other databases than MS SQL?

No, since UBIK^® integrates quite deep into the database in order to be scalable.

What SQL Server should I use? What are the differences of the editions?

Please have a look at Microsoft SQL Server Library to check for limitations.

Can I use SQL Server Express?

Basically yes, but be aware of the limitations listed here.

@@ Line 21: / Line 21: @@
 ===Which ports are used by default? ===
-* Communication between the {{UBIK}} and {{UBIKCLIENT}} uses '''443''' (https) or '''80''' (http). The authentication requires '''https''' always!
+* Communication between the Server and Client uses '''443''' (https) or '''80''' (http). The authentication requires '''https''' always!
 * Microsoft SQL Server uses '''1433''' by default