• Download Microsoft .NET Framework 4 (Standalone Installer ...
• Standalone Client Required
• Dayz Standalone Client Side Modding
• More Videos For Standalone Client »
• Vcenter Converter Standalone Client

Version Repository Usages Date; 2.0.x. 2.0.0: Central: 1: Dec, 2020: 2.0.0-RC1: Central: 0 Dec, 2020. An easy to use launcher for DayZ Standalone. with unofficial mod support. Portable Version. The standalone client, like many things made by Atelier 801 initially centered around Transformice (which was their only game at the time). In more recent times, the official standalone client allows players to choose from multiple games to play. The standalone client can be downloaded from the login screen of any game that uses it (only Windows and Mac supported currently). While many people. Once you've done this, you should be able to log into the stand-alone client using your email address and password. If you have any difficulty setting up your email address, please let us know which address you tried to use, and we'll be happy to assist further. Kind regards, Ben.

Note:

The WebLogic Full client and thin IIOP clients are removed in WebLogic Server 14.1.1.0.0. Oracle recommends using the thin T3 client or the Install client instead.

Distributing Client JAR Files

Learn about license requirements when using client JARs and other resources provided in Oracle WebLogic Server for creating standalone clients.

See Standalone WebLogic Clients.

WebLogic T3 Clients

The WebLogic T3 clients are Java RMI clients that use Oracle T3 protocol to communicate with WebLogic Server. T3 clients outperform other client types and are the most recommended type of client.

WebLogic Thin T3 Client

The WebLogic Thin T3 Java client provides a light-weight alternative to the WebLogic Install client. This client provides the same performance as an install client, but uses a much smaller JAR file. The thin T3 client supports most of the use cases for which the install client can be used.

Note:

The WebLogic Full client and thin IIOP client are removed in WebLogic Server 14.1.1.0.0. Oracle recommends using the thin T3 client or the Install client instead.

The thin T3 client can be used in standalone applications, and is also designed for applications running on foreign (non-WebLogic) servers. One common use case is integration with WebLogic JMS destinations.

• Using WebLogic RMI with T3 Protocol in Developing RMI Applications for Oracle WebLogic Server

WebLogic Install Client

The WebLogic Install client is available in a full WebLogic Server installation. It uses the weblogic.jar file located at WL_HOME/server/lib and provides client-side support for all WebLogic Server-specific value-added features. It is the only client that supports server-side operations, such as:

• Operations necessary for development purposes, such as the ejbc compiler.

• Administrative operations, such as deployment.

• WLST and client-side JSR 88 applications that invoke server-side operations.

Java IIOP

IIOP can be a transport protocol for distributed applications with interfaces written in Java RMI. When there is an option, Oracle recommends using T3 clients instead of IIOP clients.

An IIOP protocol Java client works with WebLogic Server 14.1.1.0.0 and later, only if all Java (remote and local) is at JDK8 or all Java is at JDK11, and also when:

• The Java client is another WebLogic Server at any version for which overall interoperability is supported.

• The Java client is a WebLogic Install client (weblogic.jar) at any version for which overall interoperability is supported.

• The Java client is a WebLogic Full client (wlfullclient.jar), as long as the client is an earlier version of WebLogic Server than WLS 14.1.1.0.0. Note that wlfullclient.jar is removed in WLS 14.1.1.0.0.

• The Java client with thin IIOP WebLogic client JARs (wlclient.jar), as long as the client is an earlier version of WebLogic Server than WLS 14.1.1.0.0. Note that wlclient.jar is removed in WLS 14.1.1.0.0.

For Java IIOP limitations, see Table 2-1.

For more information about interoperability, see Protocol Compatibility in Understanding Oracle WebLogic Server.

See also Using RMI over IIOP in Developing RMI Applications for Oracle WebLogic Server.

CORBA Clients

If you are not working in a Java-only environment, you can use IIOP to connect your Java programs with Common Object Request Broker Architecture (CORBA) clients and execute CORBA objects. IIOP can be a transport protocol for distributed applications with interfaces written in Interface Definition Language (IDL) or Java RMI. However, the two models are distinctly different approaches to creating an interoperable environment between heterogeneous systems.

When you program, you must decide to use either IDL or RMI interfaces; you cannot mix them. WebLogic Server supports the following CORBA client models:

JMX Clients

You can use a JMX client to access WebLogic Server MBeans.

See Accessing WebLogic Server MBeans With JMX in Developing Custom Management Utilities Using JMX for Oracle WebLogic Server.

JMS Clients

WebLogic Server provides a number of JMS clients that provide Java EE and WebLogic JMS functionality.

• WebLogic Thin T3 client, see Developing a WebLogic Thin T3 Client.

• WebLogic Install client, see WebLogic Install Client.

• JMS SAF client, see Reliably Sending Messages Using the JMS SAF Client.

• JMS C client, see WebLogic JMS C API in Developing JMS Applications for Oracle WebLogic Server.

• JMS .NET client, see Developing JMS .NET Client Applications for Oracle WebLogic Server.

• WebLogic AQ JMS client, see Standalone WebLogic AQ JMS Clients in Administering JMS Resources for Oracle WebLogic Server. The WebLogic AQ JMS client obtains destination information using WebLogic Server JNDI and provides direct access to Oracle database AQ JMS destinations using an embedded driver. It does not provide access to WebLogic Server JMS destinations.

Tip:

Oracle WebLogic JMS clients require using the T3 protocol in all cases.

Web Services Clients

A standalone web services client (wseeclient.jar) uses WebLogic client classes to invoke a web service hosted on WebLogic Server or on other application servers.

See Using a Standalone Client JAR File When Invoking Web Services in Developing JAX-RPC Web Services for Oracle WebLogic Server.

WebLogic Tuxedo Connector Clients

WebLogic Tuxedo Connector provides interoperability between WebLogic Server applications and Tuxedo services.

See:

Download Microsoft .NET Framework 4 (Standalone Installer ...

• Developing Oracle WebLogic Tuxedo Connector Client EJBs in the Developing Oracle WebLogic Tuxedo Connector Applications for Oracle WebLogic Server

• How to Develop RMI/IIOP Applications for the Oracle WebLogic Tuxedo Connector in the Developing Oracle WebLogic Tuxedo Connector Applications for Oracle WebLogic Server

• How to Develop Oracle WebLogic Tuxedo Connector Client Beans using the CORBA Java API in the Developing Oracle WebLogic Tuxedo Connector Applications for Oracle WebLogic Server

Standalone Client Required

Clients and Features

Learn about the types of clients and features supported in a WebLogic Server environment.

Dayz Standalone Client Side Modding

The following table lists the types of clients supported in a WebLogic Server environment, their characteristics, features, and limitations.

Note:

Oracle does not support combining clients to create extended feature sets. Select a client that best fits your environment and use only the client classes specified for that client type.

More Videos For Standalone Client »

Table 2-1 WebLogic Server Client Types and Features

Vcenter Converter Standalone Client

Client	Type	Language	Protocol	Client Class Requirements/Bundled Resources	Key Features
WL Thin T3 Client	RMI	Java	T3	wlthint3client.jar	Small Footprint. Oracle WebLogic Server T3/T3S protocol for Remote Method Invocation (RMI). Supports WebLogic Server clustering. Supports JSSE SSL, except with HTTP tunneling. Faster and more scalable than IIOP clients. Most WebLogic client JMS features, including the WebLogic Store-and-Forward (SAF) Service using the wlsaft3client.jar. Supports most Java EE features. See Developing a WebLogic Thin T3 Client.
Install Client	RMI	Java	IIOP	weblogic.jar	Supports JSSE SSL. Supports most of the Java EE features, but does not support WebLogic client JMS. Operations necessary for development purposes, such as the ejbc compiler. Supports administrative operations, such as deployment. Supports WLST and client-side JSR 88 applications that invoke server-side operations. See WebLogic Install Client.
Install Client	RMI	Java	T3	weblogic.jar	Supports Oracle WebLogic Server T3/T3S protocol for Remote Method Invocation (RMI), including HTTP Tunneling of T3/T3S. Supports WebLogic Server clustering. Supports JSSE SSL. Faster and more scalable than IIOP clients. All WebLogic client JMS features, including the WebLogic JMS client Store-and-Forward (SAF) Service. Supports most of the Java EE features. Supports operations necessary for development purposes, such as the ejbc compiler. Supports administrative operations, such as deployment. Supports WLST and client-side JSR 88 applications that invoke server-side operations. See WebLogic Install Client.
CORBA/IDL	CORBA	Languages that OMG IDL maps to, such as C++, C, Smalltalk, COBOL	IIOP	No WebLogic classes	Uses CORBA 2.3 ORB. Does not support WebLogic Server-specific features. Does not support Java. See Developing a CORBA/IDL Client.
JMS SAF Client (Introduced in WebLogic Server 9.2)	RMI	Java	T3	wlsaft3client.jar and wlthint3client.jar	Locally stores messages on the client and forwards them to server-side JMS destinations when the client is connected. Supports SSL. See Reliably Sending Messages Using the JMS SAF Client.
JMS C Client (Introduced in WebLogic Server 9.0)	JNI	C	T3	Any WebLogic JMS capable Java client, such as wlthint3client.jar	C client applications that can access WebLogic JMS applications and resources. Supports SSL. See WebLogic JMS C API
JMS .NET Client (Introduced in WebLogic Server 10.3)	T3	.NET	T3	WebLogic.Messaging.dll dynamic library	Microsoft .NET client applications, written in C#, that can access WebLogic JMS applications and resources. See Developing JMS .NET Client Applications for Oracle WebLogic Server.
WebLogic AQ JMS Client (Introduced in WebLogic Server 10.3.1)	JNDI	Java	IIOP/T3 +	aqapi.jar, o6.jar, and orai18n.jar are required, plus either the weblogic.jar (Install client) or the wlthint3client.jar.	See Standalone WebLogic AQ JMS Clients in Administering JMS Resources for Oracle WebLogic Server.
Web Services	SOAP	Java	HTTP/S	wseeclient.jar	See Invoking a Web Service from a Standalone Client in Developing JAX-WS Web Services for Oracle WebLogic Server.
C++ Client	CORBA	C++	IIOP	Tuxedo libraries	Interoperability between WebLogic Server applications and Tuxedo clients/services. Supports SSL. Uses CORBA 2.3 ORB. See Developing a WebLogic C++ Client for a Tuxedo ORB.
Tuxedo Server and Native CORBA client	CORBA or RMI	C++	Tuxedo-General-Inter-Orb-Protocol (TGIOP)	Tuxedo libraries	Interoperability between WebLogic Server applications and Tuxedo clients/services. Supports SSL and transactions. Uses CORBA 2.3 ORB. See Developing Clients for CORBA Objects.
RESTful Webservices Client	JAX-RS	Java	HTTP/S	jersey-client.jar	Supports JAX-RS client API.