File: README

package info (click to toggle)
zeroc-ice 3.3.1-12
  • links: PTS
  • area: main
  • in suites: squeeze
  • size: 40,720 kB
  • ctags: 46,971
  • sloc: cpp: 241,481; java: 104,729; cs: 66,568; python: 18,996; makefile: 5,797; xml: 5,397; ruby: 4,788; php: 3,172; yacc: 3,113; lex: 2,223; ansic: 1,249; perl: 1,200; sh: 182; sql: 73
file content (55 lines) | stat: -rw-r--r-- 1,871 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
To run the demo, first start the IceGrid service:

$ icegridnode --Ice.Config=config.grid

In a separate window:

$ icegridadmin --Ice.Config=config.grid -e \
    "application add 'application.xml'"
$ client

This will deploy the application described in the file
"application.xml" and start the client.

Messages will be displayed in the IceGrid service window.

You can also use the descriptors in the following files to deploy
the application:

- application_with_template.xml: These descriptors demonstrate the use
  of templates for the server definition. Templates make it easy to
  deploy multiple instances of the same server.

- application_with_replication.xml: These descriptors demonstrate the
  use of replication to balance the load of the application over
  several servers.

If you have already deployed the application, you can update it to try
a new set of descriptors, for example:

$ icegridadmin --Ice.Config=config.grid -e \
    "application update 'application_with_template.xml'"

When using the descriptors from 'application_with_template.xml' or
'application_with_replication.xml', you can easily deploy more servers
based on the `SimpleServer' template. For example, you can use the
following command to deploy a new server:

$ icegridadmin --Ice.Config=config.grid -e \
    "server template instantiate Simple localhost SimpleServer index=4"


Vista Note
----------

On Vista-derived operating systems, the IceGrid node may emit the
following warning:

  warning: Unable to lookup the performance counter name:
  Unable to connect to the specified computer or the computer is
  offline. This usually occurs when you do not have sufficient
  privileges.

This issue can be resolved by granting appropriate permissions to the
node's user account. Please refer to the Troubleshooting section of
Appendix H in the Ice manual for more information.