Salesforce

Servers Settings (Magic xpa 3.x)

« Go Back

Information

 
Created ByKnowledge Migration User
Approval Process StatusPublished
Objective
Description

Servers Settings (Magic xpa 3.x)

Magic servers are the basis for the Client/Server capabilities built into Magic xpa. The Magic server is a File Management and Server Type program, capable of performing Database and File I/O for remote Magic xpa applications. Any Magic xpa installation can access many such servers, residing on various hardware platforms and operating systems, via different communication protocols. From the Server repository you can define the remote Magic servers accessible for database and file I/O services to the current installation. The Server repository also defines the means by which the local Magic xpa software communicates with its host Server.

Server repository information is contained in the [MAGIC_SERVERS] section of the Magic.ini file.

The Server repository includes the following columns:

Column

Description

#

The server identifier (#) used in the project. Magic xpa sets this column automatically.

Name

Defines the server name for the local Magic xpa. The Server Name, when used within parentheses in any file name, will cause automatic redirection of any input or output request for the file to the Server.

Server Type

Identifies the server types available to transfer and receive data from the host Server.

The server types in the list are only those loaded before Magic xpa itself was loaded. The local Magic xpa and the Server must use the same communication protocol. If a previously defined server has a type that is not recognized, the server type setting is “Unknown”. Trying to open a server without first loading its proper communication driver will fail.

The available server types are:

  • Magic Requests Broker: The Magic Requests Broker (MRB) implements a Requester-Broker connection. The MRB appears in the Server Type list only if the MRB is defined in the appropriate Magic.ini section, and communication support is installed.

  • Magic xpa space Since version: 3.0

  • Magic xpi space Since version: 3.0

Server Address

For the broker middleware:

The host and port of the server, in the following syntax: host/port, for example: MyServer/1500.


For the Magic xpa space middleware:

The address of one or more lookup locators in the format of: host[:port][^host:[port] ...].

Default value: 127.0.0.1

Examples:

  • ServerA – One lookup locator in ServerA, on the default port.

  • ServerA:4175 – One lookup locator in ServerA, on a non-default port.

  • ServerA^ServerB – Two lookup locators, in two servers, both on the default port.

  • ServerA^ServerB:4175 – Two lookup locators, in two servers, the second of which is on a non-default port.

Note: When Magic xpa servers are started from the grid (projectsStartup.xml), this field is ignored and the XAP_LOOKUP_LOCATORS= set in the GigaSpaces-xpa\bin\setenv.bat file is used instead. Since version: 3.1

For the Magic xpi space middleware:

The address for a Magic xpi server in the format of: SpaceName=MAGIC_SPACE&LookupGroupName=<name>&LookupLocators=<host:[port]>.

Related Topics

Reference
Attachment 
Attachment