Contents

1	Supported Platforms........................................................................................................................................		1
2	AIX Platforms....................................................................................................................................................		3
	2.1	Multicast Support ...................................................................................................................................	6
	2.2	Supported Transports ............................................................................................................................	6
	2.3	Monotonic Clock Support .....................................................................................................................	6
	2.4	Thread Configuration ............................................................................................................................	6
	2.5	Durable Writer History and Durable Reader State Features............................................................	8
3	INTEGRITY Platforms ....................................................................................................................................		8
	3.1	Patch Required for INTEGRITY 10.02 Platform.................................................................................	8
	3.2	Support for Request-Reply Communication Pattern ........................................................................	8
	3.3	Diagnostics on INTEGRITY Systems.................................................................................................	10
	3.4	Running over IP Backplane on a Dy4 Champ-AVII Board.............................................................	10
	3.5	Multi-NIC Support on INTEGRITY 5.0.............................................................................................	10
	3.6	Multicast Support .................................................................................................................................	10
	3.7	Supported Transports ..........................................................................................................................	10
	3.8	Out-of-the-box Transport Compatibility with Other Connext Platforms ....................................	10
	3.9	Using rtiddsping and rtiddsspy on PowerPC INTEGRITY Systems............................................	12
	3.10	Monotonic Clock Support ...................................................................................................................	12
	3.11	Thread Configuration ..........................................................................................................................	12
	3.12	Durable Writer History and Durable Reader State Features..........................................................	14
	3.13	Issues with INTEGRITY Systems.......................................................................................................	14
4 Linux and Fedora Platforms .........................................................................................................................			15
	4.1	Multicast Support .................................................................................................................................	17
	4.2	Supported Transports ..........................................................................................................................	17
	4.3	Monotonic Clock Support ...................................................................................................................	18
	4.4	Thread Configuration ..........................................................................................................................	18
	4.5	Durable Writer History and Durable Reader State Features..........................................................	19
	4.6	Libraries Required for Using RTI Secure WAN Transport APIs....................................................	19
	4.7	Libraries Required for Using RTI TCP Transport APIs...................................................................	19

iii

5 LynxOS Platforms...........................................................................................................................................		26
5.1	Multicast Support .................................................................................................................................	29
5.2	Supported Transports ..........................................................................................................................	29
5.3	IP Fragmentation Issues ......................................................................................................................	30
5.4	Monotonic Clock Support ...................................................................................................................	30
5.5	Thread Configuration ..........................................................................................................................	30
5.6	Durable Writer History and Durable Reader State Features..........................................................	31

6 Mac OS Platforms...........................................................................................................................................		31
6.1	Multicast Support .................................................................................................................................	34
6.2	Supported Transports ..........................................................................................................................	34
6.3	Monotonic Clock Support ...................................................................................................................	34
6.4	Thread Configuration ..........................................................................................................................	34
6.5	Durable Writer History and Durable Reader State Features..........................................................	35

7 QNX Platforms................................................................................................................................................		35
7.1	Required Change for Building with C++ Libraries for QNX Platforms.......................................	37
7.2	Multicast Support .................................................................................................................................	37
7.3	Supported Transports ..........................................................................................................................	37
7.4	Monotonic Clock Support ...................................................................................................................	38
7.5	Thread Configuration ..........................................................................................................................	38
7.6	Durable Writer History and Durable Reader State Features..........................................................	39
7.7	Restarting Applications on QNX Systems ........................................................................................	39

8 Solaris Platforms ............................................................................................................................................		40
8.1	Support for Request-Reply Communication Pattern ......................................................................	42
8.2	Multicast Support .................................................................................................................................	43
8.3	Supported Transports ..........................................................................................................................	43
8.4	Monotonic Clock Support ...................................................................................................................	44
8.5	Libraries Required for using RTI Secure WAN Transport APIs ....................................................	44
8.6	Thread Configuration ..........................................................................................................................	44
8.7	Durable Writer History and Durable Reader State Features..........................................................	44

9 VxWorks Platforms ........................................................................................................................................		46
9.1	Support for Request-Reply Communication Pattern ......................................................................	48
9.2	Increasing the Stack Size......................................................................................................................	48
9.3	Libraries for RTP Mode on VxWorks 6.3 and Higher Systems......................................................	48
9.4	Requirement for Restarting Applications .........................................................................................	49
9.5	Multicast Support .................................................................................................................................	49
9.6	Supported Transports ..........................................................................................................................	49
9.7	Monotonic Clock Support ...................................................................................................................	50
9.8	Thread Configuration ..........................................................................................................................	50
9.9	Durable Writer History and Durable Reader State Features..........................................................	51
9.10	Increasing the Receive Socket Buffer Size .........................................................................................	51

iv

10 Windows Platforms........................................................................................................................................		64
10.1	Use Dynamic MFC Library, Not Static ..............................................................................................	67
10.2	Visual Studio 2005 Required when Using RTI ‘Debug’ Libraries for Java or .NET APIs ..........	67
10.3	.NET API Requires Thread Affinity...................................................................................................	67
10.4	Multicast Support .................................................................................................................................	68
10.5	Supported Transports ..........................................................................................................................	68
10.6	Monotonic Clock Support ...................................................................................................................	68
10.7	Thread Configuration ..........................................................................................................................	68
10.8	ODBC Database Compatibility...........................................................................................................	69
10.9	PPP Link Support for Windows XP Systems....................................................................................	70
10.10	Libraries Required for Using RTI Secure WAN Transport APIs....................................................	70
10.11	Libraries Required for Using RTI TCP Transport APIs...................................................................	70

v

Platform Notes

This document provides platform-specific instructions on how to compile, link, and run RTI® Connext™ (formerly RTI Data Distribution Service) applications.

1	Supported Platforms
	Table 1.1 lists the platforms available with Connext 5.1.0.
Table 1.1 Platforms Available with Release 5.1.0
		Operating System	Reference
	AIX®	AIX 5.3, 7.1	Table 2.1 on page 3
	INTEGRITY®	INTEGRITY 5.0.11, 10.0.2	Table 3.1 on page 8
	Linux®	Raspbian Wheezy 7.0 (3.x kernel)	Table 4.1 on page 15
	(ARM® CPU)
	Linux®
	(Cell BE™	Fedora® 12 (2.6.32 kernel)	Table 4.2 on page 16
	CPU)
		CentOS 5.4, 5.5, 6.0, 6.2 - 6.4 (2.6 kernel)
		Fedora 12 (2.6.32 kernel)
		Fedora 12 (2.6.32 kernel) with gcc 4.5.1
	Linux	Red Hat® Enterprise Linux 4.0, 5.0-5.2, 5.4, 5.5, 6.0 - 6.4 (2.6 kernel)
		Red Hat Enterprise Linux 5.2 with Real-Time Extensions	Table 4.3 on page 16
	(Intel® CPU)
		(2.6 kernel)
		SUSE® Linux Enterprise Server 11 SP2 (2.6 and 3.x kernel)
		Ubuntu® Server 12.04 LTS (3.x kernel)
		Wind River® Linux 4 (2.6 kernel)
	Linux	Freescale P2020RDB (2.6.32 kernel)
		SELinux (2.6.32 kernel)
	(PowerPC®		Table 4.4 on page 17
		Wind River Linux 3
	CPU)
		Yellow Dog™ Linux 4.0
	LynxOS®a	LynxOS 4.0, 4.2, 5.0	Table 5.1 on page 26
	Mac OS®	Mac OS X 10.8	Table 6.1 on page 31
	QNX®	QNX Neutrino® 6.4.1, 6.5	Table 7.1 on page 35
	Solaris™	Solaris 2.9, 2.10	Table 8.1 on page 40

1

			Supported Platforms
Table 1.1 Platforms Available with Release 5.1.0
		Operating System		Reference
		VxWorks 5.5, 6.3 - 6.9
	VxWorks®	VxWorks 653 2.3		Table 9.1 on page 46
		VxWorks MILS 2.1.1
		Windows 7 (32-bit and 64-bit Editions)
		Windows 8 (32-bit and 64-bit Editions)
		Windows Server 2003 (32-bit and 64-bit Editions)		Table 10.1 on
	Windows®	Windows Server 2008 R2 (64-bit Edition)
				page 64
		Windows Server 2012 R2 (64-bit Edition)
		Windows Vista® (32-bit and 64-bit Editions)
		Windows XP Professional SP2 (32-bit and 64-bit Editions)

a.The Java API is not supported on LynxOS platforms in 5.1.0. If your application requires support for Java on LynxOS, please contact your RTI account manager.

For each platform, this document provides information on:

❏Supported operating systems and compilers

❏Required Connext and system libraries

❏Required compiler and linker flags

❏Required environment variables for running the application (if any)

❏Details on how the Connext libraries were built

❏Multicast support

❏Supported transports

❏Monotonic clock support

❏Thread configuration

❏Durable Writer History and Durable Reader State features support

Table 1.2 lists additional target libraries available with Connext 5.1.0, for which RTI offers custom support. If you are interested in using one of these platforms, please contact your local RTI rep- resentative or email sales@rti.com. These custom platforms are not described in this document, each has separate documentation that is provided with the custom library distribution.

Table 1.2 Custom Supported Platforms

	Operating System		CPU	Compiler	RTI Architecture
					Abbreviation
INTEGRITY		INTEGRITY 5.0.11	PPC8349	GHnet2 TCP/IP stack	ppc8349Inty5.0.11.mds8349

2

						AIX Platforms
Table 1.2 Custom Supported Platforms
		Operating System		CPU	Compiler	RTI Architecture
						Abbreviation
			NI Linux Real-Time	ARMv7	gcc 4.4.1	armv7AngstromLinux3.2
			3.2a			gcc4.4.1.cortex-a9
			Red Hat Enterprise		gcc 4.2.1	i86Linux2.6gcc4.2.1
				x86
					Java Platform, Stan-
			Linux 5.2 (2.6 kernel)			i86Linux2.6gcc4.2.1jdk
					dard Edition JDK 1.7
	Linux
			Linux 6 for IBM
			Red Hat Enterprise
			POWER7 Servers	POWER7	gcc 4.4.4	power7Linux2.6gcc4.4.4
			(2.6.32-70.el.ppc64)
			RedHawk Linux 6.0	x64	gcc 4.4.5	x64Linux2.6gcc4.4.5
			Wind River Linux	Pentium class	gcc 4.3.2	i86WRLinux2.6gcc4.3.2
			3.0.3 (2.6 kernel)
			VxWorks 6.7	Any PowerPC CPU		For Kernel Modules:
	VxWorks			with floating-point		ppc604Vx6.7gcc4.1.2jdk
			VxWorks 6.8
				hardware that is back-	JamaicaVM 6.2.1 with
				wards-compatible	gcc 4.1.2	For Kernel Modules:
				with 32-bit PowerPC		ppc604Vx6.8gcc4.1.2jdk
				604b

a.Requires NI-RIO 13.1 release or a patch from NI for NI-RIO 13.0

b.Some PowerPC cores such as e500v1 and e500v2 are not fully backwards-compatible with PPC 604.

2 AIX Platforms

Table 2.1 lists the architectures supported on the IBM® AIX operating system.

Table 2.1 Supported AIX Target Platforms

	Operating	CPU	Compiler	RTI Architecture
	System			Abbreviation
	AIX 5.3	POWER5 (32-bit mode)	IBM XLC for AIX v9.0	p5AIX5.3xlc9.0
		POWER5 (64-bit mode)	IBM XLC for AIX v9.0	64p5AIX5.3xlc9.0
	AIX 7.1	POWER class (64-bit mode)	IBM xlC_r for AIX v12.1	64p7AIX7.1xlc12.1
			IBM Java 1.7	64p7AIX7.1xlc12.1jdk

Table 2.2 lists the compiler flags and the libraries you will need to link into your application.

Table 2.3 provides details on the environment variables that must be set at run time for an AIX architecture.

3

AIX Platforms

Table 2.4 provides details on how the libraries were built. This table is provided strictly for infor- mational purposes; you do not need to use these parameters to compile your application. You may find this information useful if you are involved in any in-depth debugging.

Table 2.2 Building Instructions for AIX Architectures

	API	Library	Required RTI Librariesa	Required System	Required Compiler
		Format		Librariesb	Flags
			libnddscppz.a
			libnddscz.a
		Static Release	libnddscorez.a
			For Connext Messaging, also include:
			librticonnextmsgcppz.a	-ldl -lnsl -lm
			libnddscppzd.a	-pthread
			libnddsczd.a
		Static Debug	libnddscorezd.a
			For Connext Messaging, also include:		-DRTI_AIX
	C++		librticonnextmsgcppzd.a		-DRTI_UNIX
			libnddscpp.so		-q[32|64] c
		Dynamic	libnddsc.so		-qlongdouble
			libnddscore.so
		Release
			For Connext Messaging, also include:
			librticonnextmsgcpp.so	-ldl -lnsl -lm
			libnddscppd.so	-pthread -brtl
		Dynamic	libnddscd.so
			libnddscored.so
		Debug
			For Connext Messaging, also include:
			librticonnextmsgcppd.so
			libnddscz.a
		Static Release	libnddscorez.a
			For Connext Messaging, also include:
			librticonnextmsgcz.a	-ldl -lnsl -lm
			libnddsczd.a	-pthread
		Static Debug	libnddscorezd.a		-DRTI_AIX
			For Connext Messaging, also include:
					-DRTI_UNIX
			librticonnextmsgczd.a
	C				-q[32|64] c
			libnddsc.so
					-qlongdouble
		Dynamic	libnddscore.so
					-qthreaded d
		Release	For Connext Messaging, also include:
			librticonnextmsgc.so	-ldl -lnsl -lm
			libnddscd.so	-pthread -brtl
		Dynamic	libnddscored.so
		Debug	For Connext Messaging, also include:
			librticonnextmsgcd.so
			nddsjava.jar
		Release	For Connext Messaging, also include:
	Java		rticonnextmsg.jar	N/A	N/A
			nddsjavad.jar
		Debug	For Connext Messaging, also include:
			rticonnextmsgd.jar

a.The Connext C/C++ libraries are located in $(NDDSHOME)/lib/<architecture>/. (where $(NDDSHOME) is where Connext is installed, such as /local/rti/ndds.5.x.y)

4

AIX Platforms

b.Transports (other than the default IP transport) such as StarFabric may require linking in additional libraries. For fur- ther details, see the online documentation or contact support@rti.com.

c.Use '-q32' if you build 32-bit code or '-q64' for 64-bit code.

d.The '-qthreaded' option is automatically set if you use one of the compilers that ends with ‘_r’, such as cc_r, xlc_r, xlC_r. See the IBM XLC reference manual for more information.

Table 2.3 Running Instructions for AIX Architectures

		Library
	RTI Architecture	Format	Required Environment Variables
		(Release
		& Debug)
	64p7AIX7.1xlc12.1jdk	N/A	LIBPATH=$(NDDSHOME)/lib/<arch>: $(LIBPATH)a EXTSHM=ONb
	All other supported	Static	EXTSHM=ONb
	architectures	Dynamic	LIBPATH=$(NDDSHOME)/lib/<arch>: $(LIBPATH) EXTSHM=ONb

a.${NDDSHOME} represents the root directory of your Connext installation. ${LIBPATH} represents the value of the LIB- PATH variable prior to changing it to support Connext. When using nddsjava.jar, the Java virtual machine (JVM) will attempt to load release versions of the native libraries (nddsjava.so, nddscore.so, nddsc.so). When using nddsja- vad.jar, the JVM will attempt to load debug versions of the native libraries (nddsjava.so, nddscore.so, nddsc.so).

b.See Notes for Using Shared Memory (Section 2.2.1).

Table 2.4 Library-Creation Details for AIX Architectures

		Library
	RTI Architecture	Format	Compiler Flags Used by RTI a
		(Static &
		Dynamic)
			-q32 -qlongdouble -qalias=noansi -qpic=large -qthreaded
		Release	-D_POSIX_C_SOURCE=199506L -D__EXTENSIONS__ -O -qflag=i:i
			-DPtrIntType=long -DCSREAL_IS_FLOAT -DCPU=Power5+
	p5AIX5.3xlc9.0		-DNDEBUG
			-q32 -qlongdouble -qalias=noansi -qpic=large -qthreaded
		Debug	-D_POSIX_C_SOURCE=199506L -D__EXTENSIONS__ -O -qflag=i:i
			-DPtrIntType=long -DCSREAL_IS_FLOAT -DCPU=Power5+ -g
			-q64 -qwarn64 -qlongdouble -qalias=noansi -qpic=large -qthreaded
		Release	-D_POSIX_C_SOURCE=199506L -D__EXTENSIONS__ -O -qflag=i:i
			-DPtrIntType=long -DCSREAL_IS_FLOAT -DCPU=Power5+
	64p5AIX5.3xlc9.0		-DNDEBUG
			-q64 -qwarn64 -qlongdouble -qalias=noansi -qpic=large -qthreaded
		Debug	-D_POSIX_C_SOURCE=199506L -D__EXTENSIONS__ -O -qflag=i:i
			-DPtrIntType=long -DCSREAL_IS_FLOAT -DCPU=Power5+ -g
			-q64 -qwarn64 -qlongdouble -qalias=noansi -qpic=large -qthreaded
		Release	-D_POSIX_C_SOURCE=199506L -D EXTENSIONS -O -qflag=i:i
			-DPtrIntType=long -DCSREAL_IS_FLOAT -DCPU=Power7+
	64p7AIX7.1xlc12.1		-DNDEBUG
			-q64 -qwarn64 qlongdouble -qalias=noansi -qpic=large -qthreaded
		Debug	-D_POSIX_C_SOURCE=199506L -D EXTENSIONS -O -qflag=i:i
			-DPtrIntType=long -DCSREAL_IS_FLOAT -DCPU=Power7+ -g
	All supported AIX	Release	-target 1.4 -source 1.4
	architectures for
		Debug	-target 1.4 -source 1.4 -g
	Java

a.Connext was built using the 'xlC_r' compiler. See IBM's XLC reference manual for a description of the different compil- ers. For a list of the additional settings (defined by default) for the 'xlC_r' compiler, see the file /etc/vac.cfg.53.

5

AIX Platforms

2.1Multicast Support

Multicast is supported on all AIX platforms and is configured out of the box. That is, the default value for the initial peers list (NDDS_DISCOVERY_PEERS) includes a multicast address. See the online documentation for more information.

2.2Supported Transports

Shared memory: Supported and enabled by default.

UDPv4: Supported and enabled by default.

UDPv6: Not supported.

TCP/IPv4: Not supported.

2.2.1Notes for Using Shared Memory

By default, the maximum number of shared memory segments you can use with AIX is quite small and limits the capability of Connext applications to work properly over shared memory. To increase the maximum number of shared memory segments an application can use, set the fol- lowing environment variable before invoking your Connext application:

EXTSHM=ON

This environment variable is not required if your application does not use the shared memory transport.

To see a list of shared memory resources in use, please use the 'ipcs' command. To clean up shared memory and shared semaphore resources, please use the 'ipcrm' command.

The shared memory keys used by Connext are in the range of 0x400000. For example:

ipcs -m | grep 0x004

The shared semaphore keys used by Connext are in the range of 0x800000; the shared mutex keys are in the range of 0xb00000. For example:

ipcs -s | grep 0x008 ipcs -s | grep 0x00b

Please refer to the shared-memory transport online documentation for details on the shared memory and semaphore keys used by Connext.

2.3Monotonic Clock Support

The monotonic clock (described in Section 8.6 in the RTI Core Libraries and Utilities User’s Manual) is not supported on AIX platforms.

2.4Thread Configuration

Table 2.5 lists the thread settings for AIX platforms.

Table 2.6 lists the thread-priority definitions for AIX platforms.

Table 2.5 Thread Settings for AIX Platforms

	Applicable Thread	DDS_ThreadSettings_t	Platform-Specific Setting
		mask	OS default thread type
	Asynchronous Publisher,	priority	OS default thread priority
	Asynchronous flushing	stack_size	4*192*1024
	thread
		cpu_list	CPU core affinity not supported
		cpu_rotation	CPU core affinity not supported

6

				AIX Platforms
Table 2.5 Thread Settings for AIX Platforms
	Applicable Thread	DDS_ThreadSettings_t		Platform-Specific Setting
		mask		DDS_THREAD_SETTINGS_STDIO
		priority		OS default thread priority
	Database thread
		stack_size		192*1024
		cpu_list		CPU core affinity not supported
		cpu_rotation		CPU core affinity not supported
		mask		DDS_THREAD_SETTINGS_STDIO |
				DDS_THREAD_SETTINGS_FLOATING_POINT
	Event thread	priority		OS default thread priority
		stack_size		4*192*1024
		cpu_list		CPU core affinity not supported
		cpu_rotation		CPU core affinity not supported
		mask		DDS_THREAD_SETTINGS_STDIO |
				DDS_THREAD_SETTINGS_FLOATING_POINT
	ReceiverPool threads	priority		OS default thread priority
		stack_size		4*192*1024
		cpu_list		CPU core affinity not supported
		cpu_rotation		CPU core affinity not supported
Table 2.6 Thread-Priority Definitions for AIX Platforms
	Thread-Priority Definition			Operating-System Priority
	THREAD_PRIORITY_DEFAULT		-9999999
	THREAD_PRIORITY_HIGH		-9999999
	THREAD_PRIORITY_ABOVE_NORMAL		-9999999
	THREAD_PRIORITY_NORMAL		-9999999
	THREAD_PRIORITY_BELOW_NORMAL		-9999999
	THREAD_PRIORITY_LOW		-9999999

2.4.1Changing Thread Priority

Due to the AIX threading-model implementation, there are situations that require you to run your Connext application with root privileges:

❏For all APIs: Your application must have root privileges to use the thread option, DDS_THREAD_SETTINGS_REALTIME_PRIORITY, for the event and receiver pool thread QoS (DDS_DomainParticipantQos.event.thread, DDS_DomainParticipantQos.receiver- _pool.thread).

❏For the Java API only: Your application must have root privileges to change the event and receiver pool thread priorities (DDS_DomainParticipantQos.event.thread, DDS_DomainParticipantQos.receiver_pool.thread).

Table 2.7 Support for Controlling CPU Core Affinity for RTI Threads

Support for controlling CPU core affinity (described in Section 19.5 in the RTI Core Libraries and Utilities User’s Manual) is not available for AIX platforms.

7

INTEGRITY Platforms

2.5Durable Writer History and Durable Reader State Features

The Durable Writer History and Durable Reader State features are not supported on AIX plat- forms.

3	INTEGRITY Platforms
	Table 3.1 lists the architectures supported on the INTEGRITY® operating system.
Table 3.1 Supported INTEGRITY Target Platformsa
	Operating	CPU	Compiler	IP Stack	RTI Architecture Abbreviation
	System
	INTEGRITY 5.0.11	PPC 85XX	Multi 4.2.4	GHnet2 IP stackb	ppc85xxInty5.0.11.xes-p2020
		p4080			p4080Integrity10.0.2.xes-p4080-smpd
	c	(based on	Multi 6.1	GHNet2 v2
	INTEGRITY 10.0.2	e500mc core)
		x86	Multi 5.0.6	CHNet IPv4 stack	pentiumInty10.0.2.pcx86

a.For use with Windows and Solaris hosts, as supported by Green Hills Software.

b.Kernel must be built using -lip4 or -lip46.

c.Requires patch_6901.iff from Green Hills Software when building a Connext application. (Patch not required to run the application.)

d.Only C and C++ APIs are supported.

Table 3.3 lists the compiler flags and the libraries you will need to link into your application.

Table 3.2 provides details on the environment variables that must be set at run time for an INTEGRITY architecture.

Table 3.4 provides details on how the libraries were built. This table is provided strictly for infor- mational purposes; you do not need to use these parameters to compile your application. You may find this information useful if you are involved in any in-depth debugging.

Table 3.2 Running Instructions for INTEGRITY Architectures

RTI Architecture	Required Environment Variables
All INTEGRITY architectures	None

3.1Patch Required for INTEGRITY 10.02 Platform

To run a Connext application on an INTEGRITY 10.0.2 system, you must install patch_6901.iff from Green Hills Software. For more information, please contact your Green Hills Software rep- resentative.

3.2Support for Request-Reply Communication Pattern

RTI Connext Messaging includes support for the Request-Reply Communication Pattern for the platforms described in Table 3.1 and all programming languages, except as noted below.

When using C++, the following platform does not support the Request-Reply Communication Pattern:

❏ppc85xxInty5.0.11.xes-p2020

❏p4080Integrity10.0.2.xes-p4080-smp

8

INTEGRITY Platforms

Table 3.3 Building Instructions for INTEGRITY Architectures

API	Library	Required RTI Libraries	a	Required	Required
	Format			System Librariesb	Compiler Flags
		libnddscppz.a
		libnddscz.a
	Static Release	libnddscorez.a
		For Connext Messaging, also include:
		librticonnextmsgcppz.a
		libnddscppzd.a
C++		libnddsczd.a
		libnddscorezd.a
	Static Debug	(libnddscppzd.dba)c
		(libnddsczd.dba)c
		(libnddscorezd.dba)c		libsocket.a	RTI_INTY
		For Connext Messaging, also include:
				libnet.a
					--exceptions
		librticonnextmsgcppzd.a		libposix.a
		libnddscz.a
	Static Release	libnddscorez.a
		For Connext Messaging, also include:
		librticonnextmsgcz.a
C		libnddsczd.a
		libnddscorezd.a
	Static Debug	(libnddsczd.dba)c
		(libnddscorezd.dba)c
		For Connext Messaging, also include:
		librticonnextmsgczd.a

a.The Connext C/C++ libraries are located in $(NDDSHOME)/lib/<architecture>/. (where $(NDDSHOME) is where Connext is installed, such as /local/rti/ndds.5.x.y)

b.Transports (other than the default IP transport) such as StarFabric may require linking in additional libraries. For fur- ther details, see the online documentation or contact support@rti.com.

c.The *.dba files contain the debugging information. You can link without these, as long as they are located in the same directory as the matching *d.a file (so that the MULTI® IDE can find the debug information).

Table 3.4 Library-Creation Details for INTEGRITY Architectures

	RTI Architecture	Library	Compiler Flags Used by RTI
		Format
			-bsp=xes-p4080-smp -prefixed_msgs
		Static	--unknown_pragma_silent --link_once_templates
		Release	-fexceptions -O -DPtrIntType=long
	p4080Integrity10.0.2.xes-		-DCSREAL_IS_FLOAT -DCPU=p4080 -DNDEBUG
	p4080-smp		-bsp=xes-p4080-smp -prefixed_msgs
		Static	--unknown_pragma_silent --link_once_templates
		Debug	-fexceptions -G -DPtrIntType=long
			-DCSREAL_IS_FLOAT -DCPU=p4080
		Static	-bspname=pcx86 -prefixed_msgs --unknown_pragma_silent -G
			-DPtrIntType=long -DCSREAL_IS_FLOAT -DCPU=
		Release
			-DTARGET=\"pentiumInty10.0.2.pcx86\" -DNDEBUG -c
	pentiumInty10.0.2.pcx86
		Static	-bspname=pcx86 -prefixed_msgs --unknown_pragma_silent -G
			-DPtrIntType=long -DCSREAL_IS_FLOAT -DCPU=
		Debug
			-DTARGET=\"pentiumInty10.0.2.pcx86\" -c

9

			INTEGRITY Platforms
Table 3.4 Library-Creation Details for INTEGRITY Architectures
	RTI Architecture	Library	Compiler Flags Used by RTI
		Format
		Static	-bspname=xes-p2020 -prefixed_msgs --unknown_pragma_silent
			-G -DPtrIntType=long -DCSREAL_IS_FLOAT -DCPU=
		Release
			-DTARGET=\"ppc85xxInty5.0.11.xes-p2020\" -DNDEBUG -c
	ppc85xxInty5.0.11.xes-p2020
		Static	-bspname=xes-p2020 -prefixed_msgs --unknown_pragma_silent
			-G -DPtrIntType=long -DCSREAL_IS_FLOAT -DCPU=
		Debug
			-DTARGET=\"ppc85xxInty5.0.11.xes-p2020\" -c

3.3Diagnostics on INTEGRITY Systems

Connext libraries for the INTEGRITY platforms use consolestring(), which prints debugging information to the serial console when available. Using the serial console as opposed to the tar- get I/O window (host I/O) is generally recommended. Host I/O will affect the real-time perfor- mance of the target. For more information on consolestring(), please refer to the INTEGRITY Development Guide.

3.4Running over IP Backplane on a Dy4 Champ-AVII Board

Connext can run on all four CPUs, provided the following hold true:

❏Connext applications on CPUs B, C and D only exchange data with applications on a dif- ferent CPU or off-board.

❏The IP backplane and associated routing has been properly configured. Connext has been tested with the following libraries built into the INTEGRITY kernel: debug, res, load, socket, itcpip, lbp, queue, ifbp, idb, bsl.

3.5Multi-NIC Support on INTEGRITY 5.0

Due to limitations with the API of the InterPeak stack for INTEGRITY 5.0, Connext only supports a single NIC when the InterPeak stack is used. This NIC must be called “eth0”. By default on an INTEGRITY system, this will correspond to the first network card, which can be changed by reconfiguring the kernel. This limitation does not affect the InterNiche stack.

3.6Multicast Support

Multicast is supported on all INTEGRITY 5.0 and 10.0 platforms.

3.7Supported Transports

Shared memory: Supported, enabled by default. To clean up shared memory resources, reboot the kernel.

UDPv4: Supported, enabled by default.

UDPv6: Not supported.

TCP/IPv4: Not supported.

3.8Out-of-the-box Transport Compatibility with Other Connext Platforms

Due to some default kernel parameters on INTEGRITY platforms, the default value for message_size_max for the UDPv4 transport, and the default values for message_size_max, received_message_count_max, and recv_buffer_size for the shared-memory transport, are dif- ferent than those for other platforms. This will cause out-of-the-box compatibility issues that may result in lack of communication. For more information on transport incompatibility, see Section 2.5, Transport Compatibility, in the RTI Core Libraries and Utilities Release Notes. The mis-

10

INTEGRITY Platforms

match in transport configuration between INTEGRITY and other platforms applies to Connext 5.1.0 and higher.

To address the compatibility issues, you can change the default transport settings of other plat- forms to match those of the INTEGRITY platform. Alternatively, you can update the INTEG- RITY kernel parameters as described below so that the INTEGRITY platform will support larger transport settings.

The directive, GM_IP_FRAG_ENTRY_MAX_SIZE, limits the size of UDP packets that can be sent and received by INTEGRITY platforms. For details on this directive, please see Section 5.4.2 in the networking.pdf manual provided with the INTEGRITY kernel. The default value of GM_IP_FRAG_ENTRY_MAX_SIZE is 9216 bytes (not 16,000 bytes as is stated in the INTEG- RITY documentation), which is why the default message_size_max for all transports supported for INTEGRITY is 9216 bytes.

If you want to send UDP messages larger than 9k, you must increase the value of GM_IP_FRAG_ENTRY_MAX_SIZE and rebuild the kernel. (You may also have to reconfigure other kernel parameters such as the socket, stack, and heap sizes to accommodate the larger value for GM_IP_FRAG_ENTRY_MAX_SIZE.) Failing to increase this value will cause failures when sending large UDP packets, and in some cases (for example with the 5.0.11 kernel) the sendto() call will fail silently.

3.8.1Smaller Shared-Memory Receive-Resource Queue Size

INTEGRITY's shared-memory pluggable transport uses the shared-memory POSIX API. This API is part of the standard INTEGRITY distribution and is shipped as a library. The current ver- sion (5.0.4) of this library uses a hard-coded value for the total amount of memory that can be shared with an address space. This limits the overall buffer space that can be used by the DomainParticipants within the same address space to communicate over shared memory with other DomainParticipants.

To allow more DomainParticipants to run within the same address space, we reduced the default size of the queue for each receive resource of the shared memory transport. The queue size is reduced to eight messages (the default for other platforms is 32). This change only applies to INTEGRITY architectures and this default value can be overwritten through the shared memory transport QoS.

3.8.2Using Shared Memory on INTEGRITY Systems

Connext uses the single address-space POSIX library to implement the shared-memory transport on INTEGRITY 10.0 operating systems.

To use shared-memory, you must configure your system to include the POSIX shared-memory library. The posix_shm_manager must be running in an "AddressSpace" solely dedicated to it. After building any Connext application that uses shared memory, you must use the intex utility (provided with the INTEGRITY development environment) to pack the application with multi- ple address-spaces: one (or more) to contain the Connext application(s), and another one to con- tain the posix_shm_manager.

Connext will run on a target without the posix_shm_manager, but the POSIX functions will fail and return ENOSYS, and the participants will fail to communicate through shared memory.

To include the POSIX Shared-Memory Manager in its own Address Space:

The project files generated by rtiddsgen for MULTI will create the shared-memory manager for you. Please follow these steps:

1.Specify the path to your INTEGRITY distribution in the _default.gpj top-level project file by adding the following line (modify it according to the path to your INTEGRITY distri- bution):

11

INTEGRITY Platforms

-os_dir=/local/applications/integrity/integrity-10.0.2

2.Build the project.

3.Before running your Connext application on a target, download the posix_shm_manager file (generated by the build) onto the target.

The POSIX Shared Memory Manager will start automatically after the download and your applications will be able to use shared memory.

Notes:

❏Only one posix_shm_manager is needed on a particular target. INTEGRITY offers the option of building this posix_shm_manager inside the kernel. Please refer to the INTEG- RITY documentation.

❏If you are already using shared memory through the POSIX library, there may be a possi- ble conflict.

❏INTEGRITY 5 has two different types of POSIX library: a single-address space one (or 'light') and another one (complete POSIX implementation). Connext uses the first one, but will work if you are using the complete POSIX implementation.

3.8.3Shared Memory Limitations on INTEGRITY Systems

If several applications are running on the same INTEGRITY node and are using shared memory, once an application is stopped, it cannot be restarted. When the application is stopped (grace- fully or ungracefully), any new application on the same domain index within the same domain will fail to start until the shared memory manager is also restarted.

Additionally, if the application is stopped ungracefully, the remaining applications will print several error messages such as the following until Connext purges the stopped application from its database:

Resource Manager send error = 0x9

This error message is logged from INTEGRITY’s POSIX shared memory manager, not from Con- next. The error message is benign and will not prevent the remaining applications from commu- nicating with each other or with application on other nodes.

The workaround is to either restart the stopped application with a different participant index or shut down all the other applications and the shared memory manager, then restart everything.

3.9Using rtiddsping and rtiddsspy on PowerPC INTEGRITY Systems

While the RTI libraries for INTEGRITY can be used with any BSP, providing the PowerPC pro- cessor falls under the same category (for example, the ppc7400... RTI libraries can be used on any target with a PPC74xx processor), rtiddsping and rtiddsspy are provided as executables, and therefore are BSP-dependent. You will not be able to run them successfully on your target if it is not compatible with the BSP listed in the architecture name (such as mvme5100-7400). Please refer to your hardware documentation for peripheral compatibility across BSPs.

3.10Monotonic Clock Support

The monotonic clock (described in Section 8.6 in the RTI Core Libraries and Utilities User’s Manual) is not supported.

3.11Thread Configuration

Table 3.5 lists the thread settings for INTEGRITY platforms.

Table 3.6 and Table 3.7 list the thread-priority definitions. Table 3.6 applies to all INTEGRITY platforms except INTEGRITY 10.02. Table 3.7 applies to INTEGRITY 10.02 only.

12

			INTEGRITY Platforms
Table 3.5 Thread Settings for INTEGRITY Platforms
	Applicable Thread	DDS_ThreadSettings_t	Platform-Specific Setting
		mask	OS default thread type
	Asynchronous Publisher,	priority	80
	Asynchronous flushing thread,	stack_size	4*20*1024
	ReceiverPool threads
		cpu_list	CPU core affinity not supported
		cpu_rotation	CPU core affinity not supported
		mask	DDS_THREAD_SETTINGS_STDIO
		priority	60
			1 (INTEGRITY 10.0.2 only)
	Database thread
		stack_size	20*1024
		cpu_list	CPU core affinity not supported
		cpu_rotation	CPU core affinity not supported
			DDS_THREAD_SETTINGS_STDIO |
		mask	DDS_THREAD_SETTINGS_FLOATING_PO
			INT
	Event thread	priority	80
		stack_size	4*20*1024
		cpu_list	CPU core affinity not supported
		cpu_rotation	CPU core affinity not supported
			DDS_THREAD_SETTINGS_STDIO |
		mask	DDS_THREAD_SETTINGS_FLOATING_PO
			INT
	ReceiverPool threads	priority	100
		stack_size	4*20*1024
		cpu_list	CPU core affinity not supported
		cpu_rotation	CPU core affinity not supported

Table 3.6 Thread-Priority Definitions for INTEGRITY Platforms (Except 10.02)

	Thread-Priority Definition	Operating-System Priority
	THREAD_PRIORITY_DEFAULT	16
	THREAD_PRIORITY_HIGH	120
	THREAD_PRIORITY_ABOVE_NORMAL	100
	THREAD_PRIORITY_NORMAL	90
	THREAD_PRIORITY_BELOW_NORMAL	80
	THREAD_PRIORITY_LOW	60
Table 3.7 Thread-Priority Definitions for INTEGRITY 10.02 Platforms
	Thread Priority Definitions	Operating System Priority
	THREAD_PRIORITY_DEFAULT	127
	THREAD_PRIORITY_HIGH	127
	THREAD_PRIORITY_ABOVE_NORMAL	100
	THREAD_PRIORITY_NORMAL	90
	THREAD_PRIORITY_BELOW_NORMAL	80

13

INTEGRITY Platforms

Table 3.7 Thread-Priority Definitions for INTEGRITY 10.02 Platforms

Thread Priority Definitions	Operating System Priority
THREAD_PRIORITY_LOW	1

3.11.1Socket-Enabled and POSIX-Enabled Threads are Required

On INTEGRITY platforms, Connext internally relies on the POSIX API for many of its system calls. As a result, any thread calling Connext must be POSIX-enabled. By default, the 'Initial' thread of an address space is POSIX-enabled, provided the address space has been linked with libposix.a. Additional user threads that call Connext must be spawned from the Initial thread using pthread_create. Only then is the created thread also POSIX-enabled. Note that tasks cre- ated at build time using the Integrate utility are not POSIX-enabled.

Furthermore, threads calling Connext must be socket-enabled. This can be achieved by calling InitLibSocket() before making any Connext calls and calling ShutdownLibSocket before the thread terminates. Note that an Initial thread is, by default, socket-enabled when the address space is linked with libsocket.a. Please refer to the INTEGRITY Development Guide for more information.

3.11.2Support for Controlling CPU Core Affinity for RTI Threads

Support for controlling CPU core affinity (described in Section 19.5 in the RTI Core Libraries and Utilities User’s Manual) is not available for INTEGRITY platforms.

3.12Durable Writer History and Durable Reader State Features

The Durable Writer History and Durable Reader State features are not supported on INTEG- RITY platforms.

3.13Issues with INTEGRITY Systems

3.13.1Delay When Writing to Unreachable Peers

On INTEGRITY systems, if a publishing application’s initial peers list includes a nonexistent (or simply unreachable) host, calls to write() may block for approximately 1 second.

This long block is caused by the stack trying to resolve the invalid/unreachable host. Most IP stacks do not block the sending thread because of this reason, and you may include invalid/ unreachable hosts in your initial-peers list. If you find that your stack does block the sending thread, please consult your IP stack vendor on how to change its behavior. [RTI Issue ID CORE- 1637, Bug # 10768]

3.13.2Linking with ‘libivfs.a’ without a File System

If you link your application with libivfs.a and are using a system that does not have a file sys- tem, you may notice the application blocks for 2 seconds at start-up.

14

Linux and Fedora Platforms

3.13.3Compiler Warnings Regarding Unrecognized #pragma Directives

Building Connext projects for INTEGRITY causes the compiler to produce several warnings about #pragma directives not recognized in some Connext header files. For example:

Building default.bld "C:/ndds/ndds.4.4x/include/ndds/dds_c/dds_c_infrastructure.h", line 926: warning: unrecognized #pragma

#pragma warning(push)

^

"C:/ndds/ndds.4.4x/include/ndds/dds_c/dds_c_infrastructure.h", line 927: warning: unrecognized #pragma

#pragma warning(disable:4190)

^

"C:/ndds/ndds.4.4x/include/ndds/dds_c/dds_c_infrastructure.h", line 945: warning: unrecognized #pragma

#pragma warning(pop)

^

These warnings do not compromise the final application produced and can be safely ignored.

3.13.4Warning when Loading Connext Applications on INTEGRITY Systems

When a Connext application compiled with the rtiddsgen-generated project files is loaded on an INTEGRITY 5.0.x target, the following warning appears:

"Warning: Program is linked with libc.so POSIX signals and cancellation will not work."

The Connext libraries do not use the additional features provided by the full POSIX implementa- tion, therefore the warning can safely be ignored. This warning is due to the fact that the rtidds- gen-generated project files use the Single AddressSpace POSIX library by default, not the full POSIX implementation on INTEGRITY (POSIX System). The Connext libraries only require Sin- gle AddressSpace POSIX to function correctly, but will still work if you are using the POSIX Sys- tem. The message indicates that items such as inter-process signaling or process-shared semaphores will not be available (more information can be found in the INTEGRITY Libraries and Utilities User's Guide, chapter "Introduction to POSIX on INTEGRITY").

4 Linux and Fedora Platforms

First, see the basic instructions for compiling on Linux platforms provided in Section 9.3 in the RTI Core Libraries and Utilities User’s Manual. The following tables provide supplemental infor- mation.

Table 4.1 through Table 4.4 list the supported Linux and Fedora architectures.

Table 4.1 Linux Platforms on ARM CPUs

	Operating System	CPU	Compiler	RTI Architecture
				Abbreviation
			gcc 4.7.2a	armv6vfphLinux3.xgcc4.7.2
	Raspbian Wheezy 7.0 (3.x kernel)	ARMv6	Java Platform, Standard Edition	armv6vfphLinux3.xgcc4.7.2jdk
			JDK 1.7
	a. Requires Linaro Gnueabihf Cross Compiler

15

Linux and Fedora Platforms

Table 4.2 Linux Platforms on Cell BE CPUs

	Operating System	CPU	Compiler	RTI Architecture
				Abbreviation
	Fedora 12 (2.6.32 kernel)	Cell BE	gcc 4.5.1a, glib 2.9	cell64Linux2.6gcc4.5.1
	Available upon request only.

a. Requires a custom version of gcc 4.5.1.

Table 4.3 Linux Platforms on Intel CPUs

	Operating System	CPU	Compiler	RTI Architecture
				Abbreviation
		x86	gcc 4.1.2	i86Linux2.6gcc4.1.2
	CentOS 5.4, 5.5 (2.6 kernel)		Java Platform, Standard Edition JDK 1.7	i86Linux2.6gcc4.1.2jdk
		x64	gcc 4.1.2	x64Linux2.6gcc4.1.2
			Java Platform, Standard Edition JDK 1.7	x64Linux2.6gcc4.1.2jdk
		x86	gcc 4.4.5	i86Linux2.6gcc4.4.5
	CentOS 6.0, 6.2-6.4 (2.6 kernel)		Java Platform, Standard Edition JDK 1.7	i86Linux2.6gcc4.4.5jdk
		x64	gcc 4.4.5	x64Linux2.6gcc4.4.5
			Java Platform, Standard Edition JDK 1.7	x64Linux2.6gcc4.4.5jdk
	Fedora 12 (2.6.32 kernel)	x64	gcc 4.4.4	x64Linux2.6gcc4.4.4
	Fedora 12 (2.6.32 kernel) with	x64	gcc 4.5.1a	x64Linux2.6gcc4.5.1
	gcc 4.5.1
	Red Hat Enterprise Linux 4.0	x86	gcc 3.4.3	i86Linux2.6gcc3.4.3
	(2.6 kernel)	x64	gcc 3.4.5	x64Linux2.6gcc3.4.5
		x86	gcc 4.1.1	i86Linux2.6gcc4.1.1
	Red Hat Enterprise Linux 5.0		Java Platform, Standard Edition JDK 1.7	i86Linux2.6gcc4.1.1jdk
	(2.6 kernel)	x64	gcc 4.1.1	x64Linux2.6gcc4.1.1
			Java Platform, Standard Edition JDK 1.7	x64Linux2.6gcc4.1.1jdk
		x86	gcc 4.1.2	i86Linux2.6gcc4.1.2
	Red Hat Enterprise Linux 5.1,		Java Platform, Standard Edition JDK 1.7	i86Linux2.6gcc4.1.2jdk
	5.2, 5.4, 5.5 (2.6 kernel)	x64	gcc 4.1.2	x64Linux2.6gcc4.1.2
			Java Platform, Standard Edition JDK 1.7	x64Linux2.6gcc4.1.2jdk
	Red Hat Enterprise Linux 5.2		gcc 4.1.2	i86Linux2.6gcc4.1.2
	with Real-Time Extensions (2.6	x86
			Java Platform, Standard Edition JDK 1.7	i86Linux2.6gcc4.1.2jdk
	kernel)
		x86	gcc 4.4.5	i86Linux2.6gcc4.4.5
	Red Hat Enterprise Linux 6.0-		Java Platform, Standard Edition JDK 1.7	i86Linux2.6gcc4.4.5jdk
	6.4 (2.6 kernel)	x64	gcc 4.4.5	x64Linux2.6gcc4.4.5
			Java Platform, Standard Edition JDK 1.7	x64Linux2.6gcc4.4.5jdk
	SUSE Linux Enterprise Server	x64	gcc 4.3.4	x64Linux2.6gcc4.3.4
	11 SP2 (2.6 kernel)		Java Platform, Standard Edition JDK 1.7	x64Linux2.6gcc4.3.4jdk
	SUSE Linux Enterprise Server	x86	gcc 4.3.4	i86Linux3gcc4.3.4
	11 SP2 (3.x kernel)		Java Platform, Standard Edition JDK 1.7	i86Linux3gcc4.3.4jdk

16

			Linux and Fedora Platforms
Table 4.3 Linux Platforms on Intel CPUs
	Operating System	CPU	Compiler	RTI Architecture
				Abbreviation
		x86	gcc 4.6.3	i86Linux3.xgcc4.4.3
	Ubuntu Server 12.04 LTS		Java Platform, Standard Edition JDK 1.7	i86Linux3.xgcc4.6.3jdk
		x64	gcc 4.6.3	x64Linux3.xgcc4.6.3
			Java Platform, Standard Edition JDK 1.7	x64Linux3.xgcc4.6.3jdk
	Wind River Linux 4 (2.6 kernel)	x64	gcc 4.4.1	x64WRLinux2.6gcc4.4.1

a. Requires a custom version of gcc 4.5.1.

Table 4.4 Linux Platforms on PowerPC CPUs

	Operating System	CPU	Compiler	RTI Architecture
				Abbreviation
	Freescale P2020RDB	PPC 85xx	Freescale gcc.4.3.74 based	ppc85xxLinux2.6gcc4.3.2
	(2.6.32 kernel)		on gcc.4.3.2
	SELinux (2.6.32 kernel)	PPC 4xxFP	gcc 4.5.1, glibc 2.9	ppc4xxFPLinux2.6gcc4.5.1
	Wind River Linux 3	PPC 85xx	gcc 4.3.2	ppc85xxWRLinux2.6gcc4.3.2
	Yellow Dog® Linux 4.0	PPC 74xx (such	gcc 3.3.3	ppc7400Linux2.6gcc3.3.3
	(2.6 kernel)	as 7410)

Table 4.5 lists the compiler flags and libraries you will need to link into your application. See also: Monotonic Clock Support (Section 4.3).

Table 4.6 provides details on the environment variables that must be set at run time for a Linux architecture. When running on 64-bit Java architectures (x64Linux2.6...jdk), use the -d64 flag on the command-line.

Table 4.7 provides details on how the Linux libraries were built. This table is provided strictly for informational purposes; you do not need to use these parameters to compile your applica- tion. You may find this information useful if you are involved in any in-depth debugging.

Table 4.8 through Table 4.10 list additional libraries required when using the optional RTI Secure WAN Transport and RTI TCP Transport, respectively.

4.1Multicast Support

Multicast is supported on all Linux and Fedora platforms and is configured out of the box. That is, the default value for the initial peers list (NDDS_DISCOVERY_PEERS) includes a multicast address. See the online documentation for more information.

4.2Supported Transports

Shared memory: Supported and enabled by default. To clean up shared memory resources, reboot the kernel.

UDPv4: Supported and enabled by default.

UDPv6: Supported for all platforms listed in Table 4.2 through Table 4.4 except SELinux 2.6.32 kernel (ppc4xxFPLinux2.6gcc4.5.1) and Raspbian Wheezy 7.0 (armv6vfphLinux3.xgcc4.7.2).

The UDPv6 transport is not enabled by default, and the peers list must be modified to sup- port IPv6.

Note: Traffic Class support is only provided on architectures with gcc 4.1.0 or later that sup- port the UDPv6 transport.

17

Linux and Fedora Platforms

TCP/IPv4: Supported on CentOS 5.4 and higher, Red Hat Enterprise Linux 5.0 and higher (except Red Hat Enterprise Linux 5.2 with Real-Time Extensions), and Ubuntu Server 10.04. (This is not a built-in transport.)

4.2.1Shared Memory Support

To see a list of shared memory resources in use, please use the 'ipcs' command. To clean up shared memory and shared semaphore resources, please use the 'ipcrm' command.

The shared memory keys used by Connext are in the range of 0x400000. For example:

ipcs -m | grep 0x004

The shared semaphore keys used by Connext are in the range of 0x800000; the shared mutex keys are in the range of 0xb00000. For example:

ipcs -s | grep 0x008 ipcs -s | grep 0x00b

Please refer to the shared-memory transport online documentation for details on the shared memory and semaphore keys used by Connext.

4.3Monotonic Clock Support

The monotonic clock (described in Section 8.6 in the RTI Core Libraries and Utilities User’s Manual) is supported on platforms with all Linux 2.6 kernel or higher.

4.4Thread Configuration

Table 4.11 lists the thread settings for Linux and Fedora platforms.

Table 4.12 and Table 4.13 list the thread-priority definitions and thread kinds, respectively.

4.4.1Native POSIX Thread Library (NPTL) Requirements

This section applies only to these platforms:

❏Red Hat Enterprise Linux 4.0: i86Linux2.6gcc3.4.3 and x64Linux2.6gcc3.4.5

❏Yellow Dog Linux 4.0: ppc7400Linux2.6gcc3.3.3

To use the above platforms, you must have the development version of Native POSIX Thread Library (NPTL) installed on your host system and the NPTL libraries on your target system.

❏When you build the application, you must have the development NPTL library installed in /usr/lib/nptl. This library is not installed by default.

❏To see if your system has NPTL installed, look for this directory: /usr/lib/nptl. It should contain these files: libpthread.so and libpthread.a.

If NPTL is not installed, you will need to install a package that includes it, such as nptl- devel. This package is not typically part of a default installation. You can find it either in your original Linux installation media (CD/DVD) or, if you have upgraded your system, through the distribution's update site.

❏When you run the application, it will automatically use the default NPTL library in /lib/ nptl. You do not need the development library installed on the target system.

Note: Make sure the environment variable LD_ASSUME_KERNEL is either not defined at all, or is set to 2.4.20 or higher. The middleware will not run if it is set to less than 2.4.20.1

1.The dynamic loader (ld), is configured by default to load the NPTL library, as long as LD_ASSUME_KERNEL is NOT defined.

18

Linux and Fedora Platforms

4.4.2Support for Controlling CPU Core Affinity for RTI Threads

Support for controlling CPU core affinity (described in Section 19.5 in the RTI Core Libraries and Utilities User’s Manual) is available on all supported Linux, SUSE, and Fedora platforms.

Note: The API for controlling CPU core affinity may change in future releases.

4.5Durable Writer History and Durable Reader State Features

To use the Durable Writer History and Durable Reader State features, you must install a rela- tional database such as MySQL.

In principle, you can use any database that provides an ODBC driver, since ODBC is a standard. How- ever, not all ODBC databases support the same feature set. Therefore, there is no guarantee that the persistent durability features will work with an arbitrary ODBC driver.

We have tested the following driver: MySQL ODBC 5.1.44.

Note: Starting with 4.5e, support for the TimesTen database has been removed.

To use MySQL, you also need MySQL ODBC 5.1.6 (or higher) and UnixODBC 2.2.12 (or higher).

The Durable Writer History and Durable Reader State features have been tested with the follow- ing Linux architectures:

❏i86Linux2.6gcc4.1.1

❏i86Linux2.6gcc4.6.3

❏x64Linux2.6gcc4.1.1

❏x64Linux2.6gcc4.6.3

For more information on database setup, please see the Addendum for Database Setup1.

4.6Libraries Required for Using RTI Secure WAN Transport APIs

This section is only relevant if you have installed RTI Secure WAN Transport. This feature is not part of the RTI Core Libraries and Utilities. If you choose to use it, it must be downloaded and installed separately. It is only available on specific architectures. See the RTI Secure WAN Trans- port Release Notes and RTI Secure WAN Transport Release Notes Installation Guide for details.

To use the WAN or Secure Transport APIs, link against the additional libraries from Table 4.8 on page 24. (Select the files appropriate for your chosen library format.)

4.7Libraries Required for Using RTI TCP Transport APIs

To use the TCP Transport APIs, link against the additional libraries from Table 4.9 on page 24. If you are using RTI TLS Support, see Table 4.10 on page 25. (Select the files appropriate for your chosen library format.)

1. RTI_CoreLibrariesAndUtilities_GettingStarted_DatabaseAddendum.pdf

19

Linux and Fedora Platforms

Table 4.5 Building Instructions for Linux and Fedora Architectures

		Library	Required	Required	Required
	API		RTI Libraries or
		Format		System Libraries	Compiler Flags
			Jar Filesa
			libnddscppz.a
		Static	libnddscz.a
			libnddscorez.a
		Release
			For Connext Messaging, also include:
			librticonnextmsgcz.a
				For all *Linux2.6gcc3*
			libnddscppzd.a
		Static	libnddsczd.a	architectures:
			libnddscorezd.a	-ldl -lnsl -lm
		Debug			64-bit architectures:
			For Connext Messaging, also include:	-L/usr/lib/nptl
					-DRTI_UNIX -m64
			librticonnextmsgcppzd.a	-lpthread -lrt
	C++
			libnddscpp.so		32-bit architectures:
			libnddsc.so	All other Linux
		Dynamic			-DRTI_UNIX -m32
			libnddscore.so	architectures:
		Release
			For Connext Messaging, also include:	-ldl -lnsl -lm
			librticonnextmsgcpp.so	-lpthread -lrt
			libnddscppd.so
		Dynamic	libnddscd.so
			libnddscored.so
		Debug
			For Connext Messaging, also include:
			librticonnextmsgcppd.so
			libnddscz.a
		Static	libnddscorez.a
		Release	For Connext Messaging, also include:
			librticonnextmsgcz.a	For all *Linux2.6gcc3*
			libnddsczd.a	architectures:
		Static	libnddscorezd.a	-ldl -lnsl -lm	64-bit architectures:
		Debug	For Connext Messaging, also include:	-L/usr/lib/nptl
					-DRTI_UNIX -m64
			librticonnextmsgczd.a	-lpthread -lrt
	C
			libnddsc.so		32-bit architectures:
		Dynamic	libnddscore.so	All other Linux
					-DRTI_UNIX -m32
		Release	For Connext Messaging, also include:	architectures:
			librticonnextmsgc.so	-ldl -lnsl -lm
				-lpthread -lrt
			libnddscd.so
		Dynamic	libnddscored.so
		Debug	For Connext Messaging, also include:
			librticonnextmsgcd.so
			nddsjava.jar
		Release	For Connext Messaging, also include:
	Java		rticonnextmsg.jar	N/A	None required
			nddsjavad.jar
		Debug	For Connext Messaging, also include:
			rticonnextmsgd.jar

a.RTI C/C++ libraries are in $(NDDSHOME)/lib/<architecture>/. RTI Java files are in $(NDDSHOME)/class/ (where $(NDDSHOME) is where Connext is installed, such as /local/rti/ndds.5.x.y).