RPC HELP Historical Info

RPC Broker Help Home

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):

Properties

The following properties were introduced with the 32-bit version of the RPC Broker:

Property

• RPCTimeLimit
• RPCVersion

Obsolete Properties

The following properties were previously included with the Broker component distributed with the BDK preview version. These properties were removed from the 32-bit version of the Broker, because they were obsolete:

Property Disposition

• ConnectMode Removed from the RPC Broker component (i.e., TRPCBroker)
• DisconnectMode Removed from the RPC Broker component (i.e., TRPCBroker)
• Protocol Removed from the RPC Broker component (i.e., TRPCBroker)
• Result Removed from the RPC Broker component (i.e., TRPCBroker)
• ServerJob Removed from the RPC Broker component (i.e., TRPCBroker)

Method

The following method was introduced with the 32-bit version of the RPC Broker:

• CreateContext

Obsolete PType Parameters

The following properties were previously included with the Broker component distributed with the BDK preview version. These properties were removed from the 32-bit version of the Broker because they were obsolete:

PType Parameter -- Disposition

• wordproc PType -- Removed (Not Supported) – The wordproc PType was used in the preview version of the RPC Broker BDK to pass text out of memo boxes, for example. However, the 32-bit version of the Broker uses list instead of wordproc.
• null PType -- Removed (Not Supported) – The null PType was used in the preview version of the RPC Broker BDK. It has also been removed. If your RPC has no input parameters, you should not use the Param property.

Client Manager (obsolete)

As of Version 1.1 of the RPC Broker, the Client Manager is no longer used. The Client Manager that was originally distributed with version 1.0 of the Broker provided two types of services:

1. It was used to invoke the RPCBI.DLL.
2. It was used by developers to set programmer preferences for using the TRPCBroker component.

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 Editor.

WARNING: 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).

VA FileMan Delphi Components (FMDC)

Sample 16-bit VA FileMan Delphi Components (FMDC) were originally distributed with the preview version of the RPC Broker Developer Kit (BDK) released in October of 1995. The 32-bit RPC Broker V. 1.1 is not compatible with the 16-bit FMDC. However, the 32-bit FileMan Delphi V. 1.0 Components (i.e., available on the Intranet in January 1997) are compatible with version 1.1 of the Broker.

Please be advised that the VA FileMan Delphi Components are not distributed with the RPC Broker. For more information on VA FileMan Delphi components (FMDC), please go to the following Web address: http://vista.med.va.gov/fmdc/index.asp