amps-python-client 5.3.4.1__zip

amps-python-client-5.3.4.1/samples/CompositeMessagePublisher.py

@@ -0,0 +1,84 @@
+#!/usr/bin/python
+
+#########################################################################
+# CompositeMessagePublisher 
+#
+# Simple example to demonstrate publish a composite message to a topic
+# in AMPS.
+#
+# The program flow is simple:
+#
+# * Connect to AMPS, using the transport configured for composite json-binary
+#   messages
+# * Logon
+# * Construct binary data for the message. For demonstration purposes,
+#   the sample uses the same binary data for each message.
+# * Publish a set of messages to AMPS. For each message:
+#   - Construct a josn part that the subscriber can filter on
+#   - Construct a composite message payload
+#   - Publish the message.
+#
+# This sample doesn't include error handling, high availability, or
+# connection retry logic.
+#########################################################################
+##
+## Copyright (c) 2010-2023 60East Technologies Inc., All Rights Reserved.
+##
+## This computer software is owned by 60East Technologies Inc. and is
+## protected by U.S. copyright laws and other laws and by international
+## treaties.  This computer software is furnished by 60East Technologies
+## Inc. pursuant to a written license agreement and may be used, copied,
+## transmitted, and stored only in accordance with the terms of such
+## license agreement and with the inclusion of the above copyright notice.
+## This computer software or any other copies thereof may not be provided
+## or otherwise made available to any other person.
+##
+## U.S. Government Restricted Rights.  This computer software: (a) was
+## developed at private expense and is in all respects the proprietary
+## information of 60East Technologies Inc.; (b) was not developed with
+## government funds; (c) is a trade secret of 60East Technologies Inc.
+## for all purposes of the Freedom of Information Act; and (d) is a
+## commercial item and thus, pursuant to Section 12.212 of the Federal
+## Acquisition Regulations (FAR) and DFAR Supplement Section 227.7202,
+## Government's use, duplication or disclosure of the computer software
+## is subject to the restrictions set forth by 60East Technologies Inc..
+##
+########################################################################
+
+import AMPS
+import array
+import os
+
+client = AMPS.HAClient("CompositePublisher-%s" % os.getpid())
+
+sc = AMPS.DefaultServerChooser()
+sc.add("tcp://127.0.0.1:9027/amps/composite-json-binary")
+
+client.set_server_chooser(sc)
+client.connect_and_logon()
+
+theData = array.array('d')
+theData.append(1.0)
+
+for d in range(1, 50):
+   if (d <= 1):
+       theData.append(float(1))
+       continue
+   theData.append(float(d + theData[d-2]) )
+
+for count in range(1,10):
+    # Construct a JSON part
+    json='{"binary_type":"double", "size":%d, "number":%d,' \
+            % (len(theData), count) + \
+           '"message":"Hi, world!"}' 
+
+    # Createa  builder and add the parts
+    builder=AMPS.CompositeMessageBuilder()
+    builder.append(json)
+    builder.append(theData.tostring())
+
+    # Send the message
+    client.publish("messages", builder.get_data())
+
+client.publish_flush(2000)
+client.close()

amps-python-client-5.3.4.1/samples/CompositeMessageSubscriber.py

@@ -0,0 +1,87 @@
+#!/usr/bin/python
+
+#########################################################################
+# CompositeMessageSubscriber
+#
+# Simple example to demonstrate subscribing to a composite message topic
+# in AMPS.
+#
+# The program flow is simple:
+#
+# * Connect to AMPS, specifying composite json-binary messages as the
+#   message type for the connection
+# * Logon
+# * Subscribe to the topic. As each message is received:
+#   - Parse the message
+#   - Print the contents of the message
+#
+# This sample doesn't include error handling, high availability, or
+# connection retry logic.
+#########################################################################
+##
+## Copyright (c) 2010-2023 60East Technologies Inc., All Rights Reserved.
+##
+## This computer software is owned by 60East Technologies Inc. and is
+## protected by U.S. copyright laws and other laws and by international
+## treaties.  This computer software is furnished by 60East Technologies
+## Inc. pursuant to a written license agreement and may be used, copied,
+## transmitted, and stored only in accordance with the terms of such
+## license agreement and with the inclusion of the above copyright notice.
+## This computer software or any other copies thereof may not be provided
+## or otherwise made available to any other person.
+##
+## U.S. Government Restricted Rights.  This computer software: (a) was
+## developed at private expense and is in all respects the proprietary
+## information of 60East Technologies Inc.; (b) was not developed with
+## government funds; (c) is a trade secret of 60East Technologies Inc.
+## for all purposes of the Freedom of Information Act; and (d) is a
+## commercial item and thus, pursuant to Section 12.212 of the Federal
+## Acquisition Regulations (FAR) and DFAR Supplement Section 227.7202,
+## Government's use, duplication or disclosure of the computer software
+## is subject to the restrictions set forth by 60East Technologies Inc..
+##
+########################################################################
+
+import AMPS
+import array
+import sys
+import os
+
+client = AMPS.HAClient("CompositeSubscriber-%s" % os.getpid() )
+
+# Add URIs and connect the client.
+sc = AMPS.DefaultServerChooser()
+sc.add("tcp://127.0.0.1:9027/amps/composite-json-binary")
+client.set_server_chooser(sc)
+
+try:
+  client.connect_and_logon()
+
+  # Construct the parser to use
+  parser = AMPS.CompositeMessageParser()
+
+  # Subscribe and process messages
+  for message in client.subscribe("messages", "/0/number % 3 == 0"):
+     # parse the message and get the number of parts
+     parts = parser.parse(message)  
+     if parts != 2:
+       print ("unknown message type")
+       continue
+
+     # Get the contents of the message 
+     json = parser.get_part(0)
+     theData = array.array('d')
+     theData.fromstring(parser.get_field_at(1))
+
+     # Print the message
+     print ("Received message with %d parts." % parts)
+     print (json)
+     datastring = ""
+     for d in theData:
+        datastring += "%f " % d
+     print (datastring)
+
+except Exception as e:
+  sys.stderr.write(str(e) + "\n")
+
+client.close()

amps-python-client-5.3.4.1/samples/RandomServerChooser.py

@@ -0,0 +1,41 @@
+from AMPS import DefaultAuthenticator, DisconnectedException
+import random
+
+class RandomServerChooser:
+
+  def __init__(self, seed = None):
+     self.servers = []
+     self.current_server = None
+     self.random = random.Random(seed)
+     self.authenticator = DefaultAuthenticator()
+
+  def add(self, server):
+     self.servers.append(server)
+
+  def get_current_uri(self):
+     if len(self.servers) == 0:
+        return None
+
+     if self.current_server == None:
+        self.set_current_server()
+ 
+     return self.current_server
+
+  def next(self):
+     self.set_current_server()  
+
+  def get_current_authenticator(self):
+    return self.authenticator
+
+  def report_failure(self, exception, info):
+    if ( (type(exception) is DisconnectedException) == False):
+       self.next() 
+
+  def report_success(self, info):
+      pass
+
+  def set_current_server(self):
+     if len(self.servers) == 0:
+        return None
+
+     self.current_server = self.random.choice(self.servers) 

amps-python-client-5.3.4.1/samples/sample.xml

@@ -0,0 +1,335 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<AMPSConfig>
+  <!-- The name of AMPS instance -->
+  <Name>AMPS</Name>
+
+  <!-- Configure the admin/stats HTTP server -->
+  <Admin>
+    <!-- To view AMPS monitoring information,
+         use http://localhost:8085/amps -->
+    <InetAddr>localhost:8085</InetAddr>
+    <SQLTransport>amps-any-type-websocket</SQLTransport>
+  </Admin>
+
+  <RequiredMinimumVersion>5.0</RequiredMinimumVersion>
+
+  <MessageTypes>
+    <MessageType>
+     <Name>composite-json-binary</Name>
+     <Module>composite-local</Module>
+     <MessageType>json</MessageType>
+     <MessageType>binary</MessageType>
+    </MessageType>
+  </MessageTypes>
+
+
+  <Transports>
+    <!-- fix messages using TCP -->
+    <Transport>
+      <Name>fix-tcp</Name>
+      <Type>tcp</Type>
+      <InetAddr>9004</InetAddr>
+      <ReuseAddr>true</ReuseAddr>
+      <MessageType>fix</MessageType>
+      <Protocol>fix</Protocol>
+    </Transport>
+
+    <!-- nvfix messages using TCP -->
+    <Transport>
+      <Name>nvfix-tcp</Name>
+      <Type>tcp</Type>
+      <InetAddr>9005</InetAddr>
+      <ReuseAddr>true</ReuseAddr>
+      <MessageType>nvfix</MessageType>
+      <Protocol>fix</Protocol>
+    </Transport>
+
+    <!-- xml messages using TCP -->
+    <Transport>
+      <Name>soap-tcp</Name>
+      <Type>tcp</Type>
+      <InetAddr>9006</InetAddr>
+      <ReuseAddr>true</ReuseAddr>
+      <MessageType>xml</MessageType>
+      <Protocol>xml</Protocol>
+    </Transport>
+
+    <!-- json messages using TCP -->
+    <Transport>
+      <Name>json-tcp</Name>
+      <Type>tcp</Type>
+      <InetAddr>9007</InetAddr>
+      <ReuseAddr>true</ReuseAddr>
+      <MessageType>json</MessageType>
+      <Protocol>amps</Protocol>
+    </Transport>
+
+    <!-- composite json/binary messages -->
+    <Transport>
+      <Name>composite-json-binary-tcp</Name>
+      <Type>tcp</Type>
+      <InetAddr>9017</InetAddr>
+      <MessageType>composite-json-binary</MessageType>
+      <Protocol>amps</Protocol>
+    </Transport>
+
+    <!-- transport that accepts all message types -->
+    <Transport>
+      <Name>amps-any-type-tcp</Name>
+      <Type>tcp</Type>
+      <InetAddr>9027</InetAddr>
+      <Protocol>amps</Protocol>
+    </Transport>
+
+    <!-- transport that accepts all message types -->
+    <Transport>
+      <Name>amps-any-type-websocket</Name>
+      <Type>tcp</Type>
+      <InetAddr>9028</InetAddr>
+      <Protocol>websocket</Protocol>
+    </Transport>
+
+
+  </Transports>
+
+  <Logging>
+    <Target>
+      <Protocol>file</Protocol>
+      <FileName>./logs/%Y%m%d%H%M%S-%n.log</FileName>
+      <!-- rotate the log file at 2GB of uncompressed log messages -->
+      <RotationThreshold>2G</RotationThreshold>
+      <!-- log all messages at 'trace' level and above -->
+      <Level>trace</Level>
+    </Target>
+
+    <!-- log everything at or above 'error' to stdout -->
+    <Target>
+      <Protocol>stdout</Protocol>
+      <Level>error</Level>
+      <IncludeErrors>00-0015</IncludeErrors>
+    </Target>
+  </Logging>
+
+  <!-- Topic definitions -->
+
+  <SOW>
+
+    <!-- Create a topic section for each topic that will maintain a
+         State of the World database -->
+
+   <Topic>
+	<!-- SOW database file name, relative to the directory
+             where AMPS is started. -->
+	<FileName>./sow/%n.sow</FileName>
+
+        <!-- Topic name. There are no special naming
+	     requirements for SOW topics. -->
+
+	<Topic>messages-sow</Topic>
+	<MessageType>json</MessageType>
+
+	<!-- Specify the key that AMPS will use to tell messages apart.
+             AMPS will store each unique message, as indicated by a
+	     unique key value. The first message with a key value is
+	     an INSERT into the SOW. Further messages with the same
+	     key UPDATE the contents of the message. --> 
+	<Key>/messageNumber</Key>
+        <!-- Specify an expiration. This sets the expiration to four hours. -->
+        <Expiration>4h</Expiration>
+    </Topic>
+
+    <!-- Topic definition for the topics used in the eval kit. -->
+
+    <Topic>
+	<!-- SOW database file name, relative to the directory
+             where AMPS is started. -->
+	<FileName>./sow/%n.sow</FileName>
+        <!-- Topic name. There are no special naming
+	     requirements for SOW topics. -->
+	<Topic>messages-sow</Topic>
+	<MessageType>xml</MessageType>
+
+	<!-- Specify the key that AMPS will use to tell messages apart.
+             AMPS will store each unique message, as indicated by a
+	     unique key value. The first message with a key value is
+	     an INSERT into the SOW. Further messages with the same
+	     key UPDATE the contents of the message. --> 
+	<Key>/hi/messageNumber</Key>
+        <!-- Specify an expiration. This sets the expiration to four hours. -->
+        <Expiration>4h</Expiration>
+    </Topic>
+
+    <Topic>
+	<!-- SOW database file name, relative to the directory
+             where AMPS is started. -->
+	<FileName>./sow/%n.sow</FileName>
+        <!-- Topic name. There are no special naming
+	     requirements for SOW topics. -->
+	<Topic>messages-sow</Topic>
+	<MessageType>nvfix</MessageType>
+
+	<!-- Specify the key that AMPS will use to tell messages apart.
+             AMPS will store each unique message, as indicated by a
+	     unique key value. The first message with a key value is
+	     an INSERT into the SOW. Further messages with the same
+	     key UPDATE the contents of the message. --> 
+	<Key>/messageNumber</Key>
+        <!-- Specify an expiration. This sets the expiration to four hours. -->
+        <Expiration>4h</Expiration>
+    </Topic>
+
+
+    <!-- Define a message queue. -->
+
+      <Queue>
+          <!-- Specify the name and message type of the queue topic --> 
+          <Topic>sample-queue</Topic>
+          <MessageType>json</MessageType>
+          <!-- Set the delivery semantics of the queue. This queue will
+               guarantee that a message is delivered and processed at least
+               once: to enforce this guarantee, a program receiving
+               messages from the queue must acknowledge that the message has
+               been received and processed. --> 
+          <Semantics>at-least-once</Semantics>
+ 
+          <!-- Set the source topic for messages in the the queue.
+               Queues receive their messages from an underlying topic defined
+               in the transaction log (or, if the UnderlyingTopic is a
+               regular expression, for all topics that match the regular
+               topics matching a regular expression).
+               If an UnderlyingTopic isn't specified, the topic name
+               of the queue is used as a default.
+          -->
+          <UnderlyingTopic>sample-queue-source</UnderlyingTopic>
+
+          <!-- Specify the delivery fairness model. In this case, deliver
+               messages to each subscriber to the queue in turn. 
+               The proportional model may offer better performance,
+               this file specifies round-robin for sample purposes. -->
+          <FairnessModel>round-robin</FairnessModel>
+
+          <!--Specify the maximum number of messages to lease to an individual
+              subscription at a time.
+
+              For sample purposes, and to provide familiar behavior
+              for a message queue, we set a maximum backlog of one 
+              message per subscription at a time. Applications typically
+              perform better when this is set to a higher value. (To
+              take advantage of a higher setting, each subscription must also
+              declare the number of messages at a time it is willing
+              to lease using the max_backlog option on  the subscription.)
+           -->
+
+          <MaxPerSubscriptionBacklog>1</MaxPerSubscriptionBacklog>
+
+      </Queue>
+
+      <!-- Define a view to use for sample evaluation. -->
+      <Topic>
+         <Name>orders</Name>
+         <MessageType>json</MessageType>
+         <FileName>./sow/%n.sow</FileName>
+         <Key>/orderId</Key>
+         <Key>/customer</Key>
+         <Key>/quantity</Key>
+         <Key>/price</Key>
+      </Topic>
+      <View>
+         <Name>customer-order-totals</Name>
+         <UnderlyingTopic>orders</UnderlyingTopic>
+         <MessageType>json</MessageType>
+         <Projection>
+           <Field>SUM(/quantity * /price) AS /total</Field>
+           <Field>/customer AS /customer</Field>
+        </Projection> 
+        <Grouping>
+           <Field>/customer</Field>
+        </Grouping>
+      </View>
+         
+  </SOW>
+
+
+  <!-- Create a transaction log to:
+       * Enable historical replay on the messages-history topics.
+       * Record the queue and the underlying topic for the queue.
+
+       Transaction log maintenance is configured in the Actions
+       section, below.
+      -->
+
+  <TransactionLog>
+
+    <JournalDirectory>./journal</JournalDirectory>
+    <!-- For sample purposes, this configuration assumes
+         access to a single file system, so there is
+         no point in archiving journals and the
+         configuration does not specify an archive directory. -->
+
+    <PreallocatedJournalFiles>1</PreallocatedJournalFiles>
+
+
+    <!-- A production instance would likely use a larger
+         journal size. Typically, a journal file would be
+         large enough to hold a few hours (or more) of
+         message traffic. -->
+    <JournalSize>10MB</JournalSize>
+
+    <Topic>
+       <Name>messages-history</Name>
+       <MessageType>nvfix</MessageType>
+    </Topic>
+    <Topic>
+       <Name>messages-history</Name>
+       <MessageType>json</MessageType>
+    </Topic>
+    <Topic>
+       <Name>sample-queue-source</Name>
+       <MessageType>json</MessageType>
+    </Topic>
+    <!--
+	Queue and their underlying topics (or a regex that covers
+	both) must be backed persisted to the transaction log.
+      -->
+    <Topic>
+       <Name>sample-queue.*</Name>
+       <MessageType>json</MessageType>
+    </Topic>
+    <FlushInterval>100ms</FlushInterval>
+  </TransactionLog>
+
+ <!--  Add an action to maintain the transaction log. This action automatically
+       cleans up journal files when the messages are no longer needed by
+       AMPS and the newest message in the file is more than 1 day old.  In
+       a production instance, this interval would be set according to the
+       data retention policy.
+
+       AMPS provides a wide variety of actions to help automate AMPS
+       administration and react to events. See the AMPS User Guide for
+       details.
+    -->
+
+
+  <Actions>
+    <!-- Maintain the transaction log. Each hour, check to see if there are
+         any unneeded journal files that are more than 1 day old. If so,
+         remove them. -->
+    <Action>
+        <On>
+            <Module>amps-action-on-schedule</Module>
+            <Options>
+               <Every>1h</Every>
+            </Options>
+        </On>
+        <Do>
+            <Module>amps-action-do-remove-journal</Module>
+            <Options>
+                <Age>1d</Age>
+            </Options>
+        </Do>
+     </Action>
+  </Actions>
+
+
+</AMPSConfig>
+