Broker help - Revision history

NeilArmstrong: Added a glossary link to Configuration~

2013-01-01T18:26:22Z

Added a glossary link to Configuration~

← Older revision		Revision as of 18:26, 1 January 2013
Line 565:		Line 565:


	By replacing the RPCBI.DLL that was distributed with the RPC Broker V. 1.0 with the BAPI32.DLL, the Client Manager is no longer required with the 32-bit version of the Broker. Configuration of programmer preferences is done via the Broker Programmer Preferences Program.		By replacing the RPCBI.DLL that was distributed with the RPC Broker V. 1.0 with the BAPI32.DLL, the Client Manager is no longer required with the 32-bit version of the Broker. [[Configuration~\|Configuration]] of programmer preferences is done via the Broker Programmer Preferences Program.

	The RPCBI.DLL and Client Manager (i.e., CLMAN.EXE) installed with Broker V. 1.0 must not be removed from the VISTA/Broker directory on the client workstation. They are still required for any 16-bit Broker-based applications created using version 1.0 of the Broker (e.g., PCMM).		The RPCBI.DLL and Client Manager (i.e., CLMAN.EXE) installed with Broker V. 1.0 must not be removed from the VISTA/Broker directory on the client workstation. They are still required for any 16-bit Broker-based applications created using version 1.0 of the Broker (e.g., PCMM).

NeilArmstrong: Added a glossary link to Business Rules~

2012-08-04T10:01:53Z

Added a glossary link to Business Rules~

← Older revision		Revision as of 10:01, 4 August 2012
Line 402:		Line 402:

	Broker Overview		Broker Overview
	The RPC Broker is a bridge connecting the client application front-end on the workstation (e.g., Delphi GUI applications) to the M-based data and business rules on the server.		The RPC Broker is a bridge connecting the client application front-end on the workstation (e.g., Delphi GUI applications) to the M-based data and [[business rules~\|Business Rules]] on the server.

NeilArmstrong: Added a glossary link to Action~

2012-07-29T22:28:07Z

Added a glossary link to Action~

← Older revision		Revision as of 22:28, 29 July 2012
Line 2,906:		Line 2,906:

	Creating RPCs		Creating RPCs
	You can create your own custom RPCs to perform ~~actions~~ on the M server and to retrieve data from the M server. Then you can call these RPCs from your client application. Creating an RPC requires you to perform the following two steps:		You can create your own custom RPCs to perform [[action~\|Action]]s on the M server and to retrieve data from the M server. Then you can call these RPCs from your client application. Creating an RPC requires you to perform the following two steps:
	· Write and test the M entry point that will be called by the RPC.		· Write and test the M entry point that will be called by the RPC.
	· Add the RPC entry that invokes the M entry point, in the REMOTE PROCEDURE file (#8994).		· Add the RPC entry that invokes the M entry point, in the REMOTE PROCEDURE file (#8994).
Line 4,822:		Line 4,822:
	20002		20002
	The server side of the application errored out. The Kernel error trap has recorded the error.		The server side of the application errored out. The Kernel error trap has recorded the error.
	Resolution: Examine the Kernel error trap for more information and specific corrective ~~actions~~.		Resolution: Examine the Kernel error trap for more information and specific corrective [[action~\|Action]]s.
	Signon was not completed		Signon was not completed
	XWB_BadSignOn		XWB_BadSignOn
Line 4,837:		Line 4,837:
	20006		20006
	This error occurs when an RPC does not have an associated version number. Each RPC must have a version number.		This error occurs when an RPC does not have an associated version number. Each RPC must have a version number.
	Resolution: Contact the developers responsible for the application software to take corrective action.		Resolution: Contact the developers responsible for the application software to take corrective [[action~\|Action]].
	Remote procedure not registered to application		Remote procedure not registered to application
	XWB_RpcNotReg		XWB_RpcNotReg
Line 5,123:		Line 5,123:

	Tutorial: Step 7 -- Associating IENs		Tutorial: Step 7 -- Associating IENs
	When a user selects a terminal type entry in the list box, a typical action would be to retrieve the corresponding record and display its fields. The key to retrieving any VA FileMan record is knowing the IEN of the record. Thus, when a user selects an entry in the list box, you need to know the IEN of the corresponding VA FileMan entry. However, the list box items themselves only contain the name of each entry, not the IEN.		When a user selects a terminal type entry in the list box, a typical [[action~\|Action]] would be to retrieve the corresponding record and display its fields. The key to retrieving any VA FileMan record is knowing the IEN of the record. Thus, when a user selects an entry in the list box, you need to know the IEN of the corresponding VA FileMan entry. However, the list box items themselves only contain the name of each entry, not the IEN.

	The subscripting of items in the list box still matches the original subscripting of items returned in brkrRPCBroker1's Results property, as performed by the following code in Button1Click event handler:		The subscripting of items in the list box still matches the original subscripting of items returned in brkrRPCBroker1's Results property, as performed by the following code in Button1Click event handler:

NeilArmstrong at 20:50, 6 April 2012

2012-04-06T20:50:44Z

← Older revision		Revision as of 20:50, 6 April 2012
Line 359:		Line 359:
	Connect		Connect

	The first time one of the Broker components in your application connects, it will establish an actual connection with the server. The connection record will be added to the list of all active connections for your application. This list is internal to the application and is completely under the control of the Broker component and is transparent to you. If another Broker component tries to connect to the same server/port, the existing connection record will be found in the list and its socket will be shared. The new connection will also be added to this list. This process is repeated with each connection request.		The first time one of the Broker components in your application connects, it will establish an actual connection with the server. The connection [[record~\|Record]] will be added to the list of all active connections for your application. This list is internal to the application and is completely under the control of the Broker component and is transparent to you. If another Broker component tries to connect to the same server/port, the existing connection [[record~\|Record]] will be found in the list and its socket will be shared. The new connection will also be added to this list. This process is repeated with each connection request.


	Disconnect		Disconnect

	When a Broker component disconnects, its connection record is removed from the internal list of active connections. If it happens to be the last record for the particular server/port combination, the connection is actually closed. This scheme provides the illusion of multiple connections without "clogging up" the server.		When a Broker component disconnects, its connection [[record~\|Record]] is removed from the internal list of active connections. If it happens to be the last record for the particular server/port combination, the connection is actually closed. This scheme provides the illusion of multiple connections without "clogging up" the server.

	Context-sensitive Help for the TRPCBroker Component		Context-sensitive Help for the TRPCBroker Component

NeilArmstrong: Added Glossary Link to Prompt~

2012-03-06T07:39:17Z

Added Glossary Link to Prompt~

← Older revision		Revision as of 07:39, 6 March 2012
Line 2,326:		Line 2,326:

	Description		Description
	The PromptDivision property is available at run-time only. It should be set to True, if the user should be prompted for Division during Silent Login. The prompt will only occur if the user has multi-division access. This property should be set to False, if the prompt should not be displayed due to the manner in which the application is running. However, if set to False and multi-division access is a possibility, then the application must handle it in another way. For example, the application developer would do the following:		The PromptDivision property is available at run-time only. It should be set to True, if the user should be prompted for Division during Silent Login. The [[prompt~\|Prompt]] will only occur if the user has multi-division access. This property should be set to False, if the [[prompt~\|Prompt]] should not be displayed due to the manner in which the application is running. However, if set to False and multi-division access is a possibility, then the application must handle it in another way. For example, the application developer would do the following:
	1. Set Login.PromptDivision to False.		1. Set Login.PromptDivision to False.
	2. Set the Connected property to True to signon.		2. Set the Connected property to True to signon.
Line 3,947:		Line 3,947:
	The functionality provided by GetServerInfo is not currently available through the RPC Broker 32-bit DLL interface. A future version of the RPC Broker will provide access to the GetServerInfo functionality for DLL users.		The functionality provided by GetServerInfo is not currently available through the RPC Broker 32-bit DLL interface. A future version of the RPC Broker will provide access to the GetServerInfo functionality for DLL users.

	To work around this for now, when using the RPC Broker 32-bit DLL, you should prompt the user directly for the server and port to connect to.		To work around this for now, when using the RPC Broker 32-bit DLL, you should ~\|Prompt]]prompt the user directly for the server and port to connect to.

	DLL Exported Functions		DLL Exported Functions

NeilArmstrong: Added Glossary link toHistorical~

2012-03-03T04:08:54Z

Added Glossary link toHistorical~

← Older revision		Revision as of 04:08, 3 March 2012
Line 238:		Line 238:


	See the "Historical Information Regarding the 16-Bit BDK vs. 32-Bit BDK" topic for properties and methods introduced with the RPC Broker 32-bit BDK. This topic also highlights disposition of the Client Manager and those properties and parameters that were obsolete and removed from the 32-bit version of the BDK.		See the "[[Historical~\|Historical]] Information Regarding the 16-Bit BDK vs. 32-Bit BDK" topic for properties and methods introduced with the RPC Broker 32-bit BDK. This topic also highlights disposition of the Client Manager and those properties and parameters that were obsolete and removed from the 32-bit version of the BDK.


Line 518:		Line 518:
	In special cases, applications can use one of two types of Silent Login to log in users without the RPC Broker prompting for login information.		In special cases, applications can use one of two types of Silent Login to log in users without the RPC Broker prompting for login information.

	Historical Information Regarding the 16-Bit BDK vs. 32-Bit BDK		[[Historical~\|Historical]] Information Regarding the 16-Bit BDK vs. 32-Bit BDK
	The following items should be noted when transitioning from the original 16-bit Broker Development Kit (BDK) V. 1T11 (i.e., Preview BDK released in October 1995) to the 32-bit BDK V. 1.1 (i.e., first released in September 1997):		The following items should be noted when transitioning from the original 16-bit Broker Development Kit (BDK) V. 1T11 (i.e., Preview BDK released in October 1995) to the 32-bit BDK V. 1.1 (i.e., first released in September 1997):

NeilArmstrong: Added glossary link to Data Types~

2012-02-28T18:13:15Z

Added glossary link to Data Types~

← Older revision		Revision as of 18:13, 28 February 2012
Line 444:		Line 444:

	Developers creating Delphi GUI applications can use the TRPCBroker Component to connect. For each transaction, the application must set parameters and execute a call. Issues include:		Developers creating Delphi GUI applications can use the TRPCBroker Component to connect. For each transaction, the application must set parameters and execute a call. Issues include:
	· Determine data types for input and return.		· Determine [[data types~\|Data Types]] for input and return.
	· Determine the kind of call to make.		· Determine the kind of call to make.

Ivaldes1 at 02:35, 21 December 2010

2010-12-21T02:35:50Z

← Older revision		Revision as of 02:35, 21 December 2010
Line 1:		Line 1:
	This is a conversion of the Broker.hlp file to mediawiki format using the helpdeco converter program converted to vistapedia.net by Ignacio Valdes of Astronaut, LLC The original formatting such as Table of Contents linking and screen shots is not present.		This is a conversion of the RPC Broker Developer's Guide Broker.hlp file to mediawiki format using the helpdeco converter program converted to vistapedia.net by Ignacio Valdes of Astronaut, LLC The original formatting such as Table of Contents linking and screen shots is not present.

	<pre>:Base broker.hlp>main		<pre>:Base broker.hlp>main

Ivaldes1 at 21:32, 20 December 2010

2010-12-20T21:32:46Z

← Older revision		Revision as of 21:32, 20 December 2010
Line 1:		Line 1:
	This is a conversion of the Broker.hlp file to mediawiki format using the helpdeco converter program converted to vistapedia.net by Ignacio Valdes of Astronaut, LLC The original formatting such as Table of Contents linking and screen shots is not present.		This is a conversion of the Broker.hlp file to mediawiki format using the helpdeco converter program converted to vistapedia.net by Ignacio Valdes of Astronaut, LLC The original formatting such as Table of Contents linking and screen shots is not present.

	:Base broker.hlp>main		<pre>:Base broker.hlp>main
	:Title RPC Broker Developer's Guide		:Title RPC Broker Developer's Guide

Line 148:		Line 148:
	4 Execute RPCs=dll_vb_execute		4 Execute RPCs=dll_vb_execute
	4 Destroy Broker Components=dll_vb_destroy		4 Destroy Broker Components=dll_vb_destroy
			</pre>

	Introduction: RPC Broker V. 1.1		Introduction: RPC Broker V. 1.1

Ivaldes1 at 21:26, 20 December 2010

2010-12-20T21:26:06Z

Show changes