/[gnumed]/gnumed/gnumed/test-area/corba/README.txt
ViewVC logotype

Contents of /gnumed/gnumed/test-area/corba/README.txt

Parent Directory Parent Directory | Revision Log Revision Log


Revision 1.4 - (show annotations) (download)
Tue Jan 27 17:00:38 2004 UTC (20 years, 3 months ago) by sjtan
Branch: MAIN
Changes since 1.3: +38 -3 lines
File MIME type: text/plain
returning to the new wxpython client, running McCoy test data showed up
a problem with getting valid id sequences. Sometimes , the sequencer falls behind the max id in identity table , so still kept the 'select max(id) from identity'.. but also iterate the sequencer so it is in sync with the max(id).

1
2 1.install gnumed
3 2.install omniORB
4 3.install omniORBpy
5
6 3. can be done using make , install and copying contents of ../{library for python}/site-packages recursively into /usr/lib/python2.2/site-packages, for those with demented distributions that want to foil default gnu configure/make/install for most unix packages.
7
8 2 + 3 can also be done by using rpm -ta on the omni tgz packages and installing the binary rpms ( for those with rpm based packaging systems ).
9
10
11 4.run omniidl -nc -I. on each of PersonIdService.idl, HL7Version2_3.idl and PersonIdTraits.idl
12
13 or sh gen_stubs.sh , to run omniidl on all the stubs here.
14
15
16
17 5.run a) omniNames -start 5002 -logdir /home/xxx/omnilog
18 where 5002 is port , and omnilog is a created directory.
19
20
21 or if already ran omniNames , then
22 b) omniNames -logdir /home/{user}/omnilog if omnilog is the directory
23 used to store the logs.
24
25 when troubleshooting , as omniNames isn't entirely failsafe for unexpected computer failures, ( or my debugging isn't good enough, take your pick),
26 delete the files in omnilog directory, and remember to put the port number
27 5002 as in a) again. Forgetting this and
28
29 omniNames -start -logdir /home/xxx/omnilog ( *** don't do this *** )
30
31 will start omniNames on a port
32 not known to either the default configuration for open-emeds or for
33 this gnumed pids wrapper , so trying to run python StartIdentificationComponent will get a transient Object error, which is a bit mysterious as omniNames seems to be running.
34
35
36
37 (FIXME note, may have problems if computer is a network computer and doesn't have
38 a localhost localdomain default name.
39 )
40
41 6. SERVER: Run the PersonIdService.
42 a. run the gnumed PersonIdServiceWrapper server.
43 Just run
44 python StartIdentificationComponent.py
45
46 run help.py for parameters to server.
47
48 (optionally)
49 b. the open emeds PIDS service.
50 -
51 - the following should be in the PIDS server
52 log output.
53 INFO gov.lanl.Utility.NameService - us/nm/state/doh/Pilot Bound to NameService as us/nm/state/doh/Pilot
54
55 - may have problems when connected to internet.
56
57
58
59 7. TEST-SUITE CLIENT: run 'python ResolveIdComponent.py -gnumed'
60 to test the gnumed PersonIdService.
61 This will go through the component tests,
62 in Test... (SequentialAccess, IdentifyPerson, IdMgr, ProfileAccess so far done, except for IdMgr merge and unmerge ids function)
63
64
65 (optional) run 'python ResolveIdComponent.py' will attempt
66 to connect to the open-emeds PIDS service if it is running.
67
68
69 8. What does this show?
70
71 Gnumed is easily extensible and can be adapted to imitate standard protocols such
72 as corbamed.
73
74 Gnumed can be the backend for clients written in other languages which
75 call a corba med interface.
76
77
78 Important external parameters:
79 connection strings are :
80
81 a. the dsn for the dbapi is in PlainConnectionProvider.py.
82 I've set up database gnumed, user gm-dbowner, password as pg.
83
84 b. the corbaloc NameService url is in ResolveIdComponent.py
85 corbaloc:iiop:localhost:5002/NameService
86 c. the NameService directory paths for gnumed and openemed is also there. 'gnumed' and 'us/blah..blah/Pilot'
87
88
89 Dependencies:
90
91 A.installation of gnumed database; setting the password of gm-dbowner to 'pg', or change the default dsn's password in PlainConnectionWrapper.py;
92 B. omniOrb installation; omniPy installation; successful running omniPy tests;
93 C. omniidl works and generates the stubs from the idl files in this directory
94 (omniidl -b python -nc ..) ;
95 D. starting the omniNames on port 5002;
96 E. starting the server component StartIdentiticationComponent.py ;
97 F. then any of the client tests should run.
98
99 A -------\
100 B -->C--->E-->F
101
102
103
104
105
106
107
108
109

savannah-hackers-public@gnu.org
ViewVC Help
Powered by ViewVC 1.1.26