Creating a cube server

After InfoSphere™ Warehouse is installed, you need to create at least one cube server instance. You create cube servers in the Administration Console.

Before you begin

Start the Administration Console.

Procedure

To create a cube server:

Select the Cubing Services tab, and click Manage Cube Servers.
Click the Create icon to start the Create Cube Server Wizard.

Complete the Create Cube Server Wizard.

Page	Description
General	Specify a unique name for the cube server, select whether you want to start cubes when the cube server starts, and click Next.
Host detail	Specify information for the host. Do not use `localhost` or `127.0.0.1` as host names as they might be misinterpreted by the system. For host names, it is recommended that you use the 256 characters in the ASCII character set to name the cube server. If you need to use international characters in the cube server, you must make sure that these international characters are supported by the cube server host. For Linux or UNIX systems, you also need to ensure that the locale that supports the international characters is the default locale (before profiles are run) for the account which runs the cube server. For example, suppose that the Administration Console client or web browser supports Chinese characters, but the cube server host only recognizes ISO8859 European characters. Starting the cube server with a Chinese name will fail, because the cube server host is not able to process the name of the cube server that you want to start. The combination of host name and port number must be unique. The cube server uses three or four consecutive ports, depending on your options. For example, if your cube server port is 9000, then 9000 and 9001 are used, the default XMLA port is 9002, and the default XMLA HTTPS port is 9003. A port cannot be used by more than one process; if any of the ports are already in use, the cube server will not start. If the cube server you create is on a remote host, you need to select the connection type that the remote host uses.
Cube Server Java VM Properties	Specify the Cubing Services installation path, and the cube server JVM information such as the Java path, the start and maximum heap size, and additional JVM arguments. The JVM arguments that you specify will be appended to the JVM command argument string, which appears in the Start command arguments field. You can specify JVM parameters here to configure the cubes on the cube server to use predefined business names. See JVM parameters to configure cubes to use predefined business names for more information. You can control how result sets for the new cube are cached. For more information see Result set caching.
Performance and Security	Specify performance and security parameters for the cube server: Member cache file system location Specify a relative or absolute directory name for the location of the member cache on the host machine for the cube server. If member caching is enabled, this file system location will be used as a temporary storage for all cubes that are currently being made available by this cube server. If you change the location, new cache files and subdirectories will be created in the new directory after the cube server is restarted, but the cache files and subdirectories in the old directory will not be deleted. For more information about data caching, see Data and member caching. Data cache file system location Specify a relative or absolute directory name for the location of the data cache on the host machine for the cube server. The data cache of a cube is located on disk and in memory, and a cube will use the file system location to store the disk-based data cache. If you change the location, new cache files and subdirectories will be created in the new directory after the cube server is restarted, but the cache files and subdirectories in the old directory will not be deleted. Maximum concurrent cubes Specify the maximum number of cubes that can run concurrently. A running cube can consume a significant amount of resources, which can decrease system performance. When the limit is reached, no cube can be started. Maximum concurrent MDX queries Specify the maximum number of concurrently processed MDX queries. The amount of resources that are used depends on the types of queries that are being issued. Many queries use very little machine resources, but some long-running queries might consume significant resources. Each operating system limits the number of threads that can run concurrently. For example, on Windows, the value you specify must be less than 10,000. Security level Select one of the four security levels
Common Logging Properties	Specify the logging settings that are common to all the loggers. For the Using rolling log field, choose whether to retain previously generated logs. If you select Yes, specify the log file size and how many copies to retain. The changes to the logging configuration take effect after this cube server is restarted (if it is currently running) or when it is started. The Administration Console does not provide log viewing capabilities for cube server files. The log files are stored on the machine where the cube server is running. They are stored in \`CS_HOME`\Logs\, where `CS_HOME` = cubing services installation directory (a subdirectory under the DWE installation directory) .
Logging details	Specify properties for specific loggers if you need to. Logging properties such as log format, display on console, and using rolling log are common in the logger's settings, but the logging level is different among loggers. With Performance Log, you can filter and collect performance statistic records based on keywords, such as MDX, member_cache_local, and member_cache_global. For example, setting the log level to member_cache_local logs local member cache details. If you set the level to member_cache_global, both local and global member cache details are added to the logger. You can select multiple levels.

After a cube server is created, you can edit its properties, query the information and the running status, or start, stop or remove this cube server. You can also manage cubes or XMLA services for this cube server.