WebLogic Server Command Reference
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
WebLogic Server provides a number of Java utilities and Ant tasks for performing administrative and programming tasks.
To use these utilities and tasks, you must set your CLASSPATH
correctly. For more information, see Modifying the Classpath.
WebLogic Server provides several Java programs that simplify installation and configuration tasks, provide services, and offer convenient shortcuts. The Java utilities provided with WebLogic Server are all described below. The command-line syntax is specified for all utilities and, for some, examples are provided.
WebLogic Server also provides a number of Ant tasks that automate common application server programming tasks. The Apache Web site provides other useful Ant tasks as well, including tasks for packaging EAR, WAR, and JAR files. For more information, see http://jakarta.apache.org/ant/manual/.
The appc compiler generates and compiles the classes needed to deploy EJBs and JSPs to WebLogic Server. It also validates the deployment descriptors for compliance with the current specifications at both the individual module level and the application level. See appc Reference in Programming WebLogic Server Enterprise JavaBeans.
The AppletArchiver
utility runs an applet in a separate frame, keeps a record of all of the downloaded classes and resources used by the applet, and packages these into either a .jar
file or a .cab
file. (The cabarc
utility is available from Microsoft.)
$ java utils.applet.archiver.AppletArchiver
URL
filename
Use the autotype
Ant task to generate non-built-in data type components, such as the serialization class, for Web Services. The fully qualified name for the autotype
Ant task is weblogic.ant.taskdefs.webservices.javaschema.JavaSchema
.
Web Services are now a J2EE standard, which has resulted in many changes between 8.1 and 9.0 WebLogic Web Services. For information about what has changed between 8.1 and 9.0 Web Services, and what has been deprecated, see "Differences Between 8.1 and 9.0 WebLogic Web Services" in Programming Web Services for WebLogic Server.
For a complete list of Web Services Ant tasks, see Ant Task Reference in Programming Web Services for WebLogic Server.
Use BuildXMLGen to generate a build.xml
file for enterprise applications in the split-directory structure. For complete documentation of this utility, see Building Applications in a Split Development Directory in Developing Applications with WebLogic Server.
The CertGen
utility generates certificates that should only be used for demonstration or testing purposes and not in a production environment.
$
java utils.CertGen
[-cacert <
ca_cert_file-
>] [-cakey <ca_key_file
>]
[-cakeypass <ca_key_password
>] [-selfsigned]
[-certfile <cert_file
>] [-keyfile <private_key_file
>]
[-keyfilepass <keyfile_pass
>] [-strength <key_strength
>]
[-cn <common_name
>] [-ou <org_unit
>] [-o <organization
>]
[-l <locality
>] [-s <state
>] [-c <country_code
>]
[-subjectkeyid <subject_key_identifier
>]
[-subjectkeyidformat UTF-8|BASE64]
By default, the CertGen utility looks for the CertGenCA.der
and CertGenCAKey.der
files in the current directory, or in the WL_HOME
directory, as specified in the weblogic.home
system property or the CLASSPATH
. Alternatively, you can specify CA files on the command line.
Enter the following command to generate certificate files named testcert
with private key files named testkey
:
$ java utils.CertGen -keyfilepass mykeypass
-certfile testcert -keyfile testkey
Generating a certificate with common name return and key strength 1024
issued by CA with certificate from CertGenCA.der file and key from CertGenCAKey.der file
You use weblogic.ClientDeployer
to extract the client-side JAR file from a J2EE EAR file, creating a deployable JAR file. The weblogic.ClientDeployer
class is executed on the Java command line with the following syntax:
java weblogic.ClientDeployer
ear-file
client
The ear-file
argument is an expanded directory (or Java archive file with a .ear extension) that contains one or more client application JAR files.
Once the client-side JAR file is extracted from the EAR file, use the weblogic.j2eeclient.Main
utility to bootstrap the client-side application and point it to a WebLogic Server instance as follows:
Use clientgen
to generate the client-side artifacts, such as the JAX-RPC stubs, needed to invoke a Web Service. See Ant Task Reference in Programming Web Services for WebLogic Server.
WebLogic Server 9.0 does not support conversion or upgrading from a pre-6.0 version of WebLogic Server. To upgrade from version 6.1 or later, see Upgrading WebLogic Application Environments.
The dbping
command-line utility tests the connection between a DBMS and your client machine via a JDBC driver. You must complete the installation of the driver before attempting to use this utility. For more information on how to install a driver, see the documentation from your driver vendor. Also see "Using Third-Party Drivers with WebLogic Server" in Programming WebLogic JDBC.
With the WebLogic Type 4 JDBC Driver for DB2, you can also use the dbping
utility to create a package on the DB2 server. When you ping the database with the dbping utility, the driver automatically creates the default package on the database server if it does not already exist. If the default package already exists on the database server, the dbping
utility uses the existing package.
The default DB2 package includes 200 dynamic sections. You can specify a different number of dynamic sections to create in the DB2 package with the -d
option. The -d
option also sets CreateDefaultPackage=true
and ReplacePackage=true
on the connection used in the connection test, which forces the DB2 driver to replace the DB2 package on the DB2 server. (See DB2 Connection Properties for more information.) You can use the -d
option with dynamic sections set at 200
to forcibly recreate a default package on the DB2 server.
Notes: When you specify the -d
option, the dbping
utility recreates the default package and uses the value you specify for the number of dynamic sections. It does not modify the existing package.
To create a DB2 package, the user that you specify must have CREATE PACKAGE privileges on the database.
$ java utils.dbping
DBMS
[-ddynamicSections
]user
password
DB
C:\>java utils.dbping ORACLE_THIN scott tiger dbserver1:1561:demo
**** Success!!! ****
You can connect to the database in your app using:
java.util.Properties props = new java.util.Properties();
props.put("user", "scott");
props.put("password", "tiger");
props.put("dll", "ocijdbc9");
props.put("protocol", "thin");
java.sql.Driver d =
Class.forName("oracle.jdbc.driver.OracleDriver").newInstance();
java.sql.Connection conn =
Driver.connect("jdbc:oracle:thin:@dbserver1:1561:demo", props);
This Ant task calls EARInit, which generates an application.xml
and a weblogic-application.xml
file for an EAR
. For more information, see
EarInit.
DDInit
is a utility for generating deployment descriptors for applications to be deployed on WebLogic Server. Target a module's archive or folder and DDInit
uses information from the module's class files to create appropriate deployment descriptor files.
In its command-line version, DDInit
writes new files that overwrite existing descriptor files. If META-INF
or WEB-INF
does not exist, DDInit
creates it.
Specify the type of J2EE deployable unit (either Web Application or Enteprise Application) for which you want deployment descriptors generated by using the DDInit
command specific to the type, as described below.
Target a WAR
file or a folder containing files that you intend to archive as a WAR
file, and WebInit
will create web.xml
and weblogic.xml
files for the module.
prompt> java weblogic.marathon.ddinit.WebInit <module>
Generate an application.xml
and a weblogic-application.xml
file for an EAR
using this command. Target an existing EAR
or a folder containing JAR
or WAR
files you intend to archive into an EAR
file.
prompt> java weblogic.marathon.ddinit.EarInit <module>
Using the weblogic.Deployer
tool, you can deploy J2EE applications and components to WebLogic Servers in a command-line or scripting environment. For detailed information on using this tool, see "weblogic.Deployer Command-Line Reference" in Deploying Applications to WebLogic Server
The weblogic.Deployer
utility replaces the weblogic.deploy
utility, which has been deprecated.
The der2pem
utility converts an X509 certificate from DER format to PEM format. The .pem
file is written in the same directory and has the same filename as the source .der
file.
$ java utils.
der2pem
derFile
[
headerFile
]
[
footerFile
]
$ java utils.
der2pem
graceland_org.der
Decoding
................................................................
See appc Reference in Programming Weblogic Server Enterprise JavaBeans.
EJBGen is an Enterprise JavaBeans 2.0 code generator. You can annotate your Bean class file with javadoc tags and then use EJBGen to generate the Remote and Home classes and the deployment descriptor files for an EJB application, reducing to one the number of EJB files you need to edit and maintain.
See EJBGen Reference in Programming WebLogic Server Enterprise JavaBeans.
The weblogic.security.Encrypt
utility encrypts cleartext strings for use with WebLogic Server. The utility uses the encryption service of the current directory, or the encryption service for a specified WebLogic Server domain root directory.
Note: An encrypted string must have been encrypted by the encryption service in the WebLogic Server domain where it will be used. If not, the server will not be able to decrypt the string.
You can only run the weblogic.security.Encrypt
utility on a machine that has at least one server instance in a WebLogic Server domain; it cannot be run from a client.
Note: BEA Systems recommends running the utility from the Administration Server domain directory or on the machine hosting the Administration Server and specifying a domain root directory.
java [ -Dweblogic.RootDirectory=
dirname
]
[ -Dweblogic.management.allowPasswordEcho=true ]
weblogic.security.Encrypt [password
]
The utility returns an encrypted string using the encryption service of the domain located in the current directory.
java weblogic.security.Encrypt xxxxxx
{3DES}Rd39isn4LLuF884Ns
The utility returns an encrypted string using the encryption service of the specified domain location.
java -Dweblogic.RootDirectory=./mydomain weblogic.security.Encrypt xxxxxx
{3DES}hsikci118SKFnnw
The utility returns an encrypted string in the current directory, without echoing the password.
java weblogic.security.Encrypt
Password:
{3DES}12hsIIn56KKKs3
The getProperty
utility gives you details about your Java setup and your system. It takes no arguments.
$ java utils.getProperty
$ java utils.
getProperty
-- listing properties --
user.language=en
java.home=c:\java11\bin\..
awt.toolkit=sun.awt.windows.WToolkit
file.encoding.pkg=sun.io
java.version=1.1_Final
file.separator=\
line.separator=
user.region=US
file.encoding=8859_1
java.vendor=Sun Microsystems Inc.
user.timezone=PST
user.name=mary
os.arch=x86
os.name=Windows NT
java.vendor.url=http://www.sun.com/
user.dir=C:\weblogic
java.class.path=c:\weblogic\classes;c:\java\lib\cla...
java.class.version=45.3
os.version=4.0
path.separator=;
user.home=C:\
The host2ior utility obtains the Interoperable Object Reference (IOR) of a WebLogic Server.
$ java utils.host2ior hostname port
The ImportPrivateKey
utility is used to load a private key into a private keystore file.
$
java utils.ImportPrivateKey
[-keystore <
keystore
>] [-storepass <
storepass
>]
[-storetype <storetype
>] [-keypass <
keypass
>] [-alias <
alias
>]
[-certfile <cert_file
>] [-keyfile <
keyfile
>]
[-keyfilepass <keyfile_pass
>]
CertGen
utilityImportPrivateKey
utilityNote: By default, the CertGen utility looks for the CertGenCA.der
and CertGenCAKey.der
files in the current directory, or in the WL_HOME
/server/lib
directory, as specified in the weblogic.home
system property or the CLASSPATH
.
Alternatively, you can specify CA files on the command line. If you want to use the default settings, there is no need to specify CA files on the command line.
$ java utils.CertGen -keyfilepass mykeypass
-certfile testcert -keyfile testkey
Generating a certificate with common name return and key strength 1024
issued by CA with certificate from CertGenCA.der file and key from CertGenCAKey.der file
$ java utils.der2pem CertGenCA.der
$ cat testcert.pem CertGenCA.pem >> newcerts.pem
$ java utils.ImportPrivateKey -keystore mykeystore -storepass mypasswd
-keyfile mykey -keyfilepass mykeypass -certfile newcerts.pem -keyfile
testkey.pem -alias passalias
No password was specified for the key entry
Key file password will be used
Imported private key testkey.pem and certificate newcerts.pem
into a new keystore mykeystore of type jks under alias passalias
Converts JHTML files to JSP files. Be sure to inspect the results carefully. Given the unpredictability of the JHTML code, jhtml2jsp
will not necessarily produce flawless translations.
The output is a new JSP file named after the original file.
The HTTP servlets auto-generated from JSP pages differ from the regular HTTP servlets generated from JHTML. JSP servlets extend weblogic.servlet.jsp.JspBase
, and so do not have access to the methods available to a regular HTTP servlet.
If your JHTML pages reference these methods to access the servlet context
or config
objects, you must substitute these methods with the reserved words in JSP that represent these implicit objects.
If your JHTML uses variables that have the same name as the reserved words in JSP, the tool will output a warning. You must edit your Java code in the generated JSP page to change the variable name to something other than a reserved word.
$ java weblogic.utils.jhtml2jsp -d <directory> filename.jhtml
$ java weblogic.utils.jhtml2jsp filename.jhtml
JSP-specific compiler task. Use appc.
The logToZip
utility searches an HTTP server log file, finds the Java classes loaded into it by the server, and creates an uncompressed .zip
file that contains those Java classes. It is executed from the document root directory of your HTTP server.
To use this utility, you must have access to the log files created by the HTTP server.
$ java utils.
logToZip
logfile
codebase
zipfile
The following example shows how a .zip
file is created for an applet that resides in the document root itself, that is, with no code base:
$ cd /HTTP/Serv/docs
$ java utils.logToZip /HTTP/Serv/logs/access "" app2.zip
The following example shows how a .zip
file is created for an applet that resides in a subdirectory of the document root:
C:\>cd \HTTP\Serv
C:\HTTP\Serv>java utils.logToZip \logs\applets\classes app3.zip
Use the MBean commands (CREATE
, DELETE
, GET
, INVOKE
, and SET
) to administer MBeans. See "Editing Commands" in WebLogic Scripting Tool.
The MulticastTest
utility helps you debug multicast problems when configuring a WebLogic Cluster. The utility sends out multicast packets and returns information about how effectively multicast is working on your network. Specifically, MulticastTest
displays the following types of information via standard output:
To use MulticastTest
, start one copy of the utility on each node on which you want to test multicast traffic.
Warning: Do NOT run the MulticastTest
utility by specifying the same multicast address (the -a
parameter) as that of a currently running WebLogic Cluster. The utility is intended to verify that multicast is functioning properly before starting your clustered WebLogic Servers.
For information about setting up multicast, see the configuration documentation for the operating system and hardware of the WebLogic Server host machine. For more information about configuring a cluster, see Using WebLogic Server Clusters.
$ java utils.MulticastTest -n
name
-aaddress
[-pportnumber
]
[-ttimeout
] [-ssend
]
$ java utils.MulticastTest -N server100 -A 237.155.155.1
Set up to send and receive on Multicast on Address 237.155.155.1 on port 7001
Will send a sequenced message under the name server100 every 2 seconds.
Received message 506 from server100
Received message 533 from server200
I (server100) sent message num 507
Received message 507 from server100
Received message 534 from server200
I (server100) sent message num 508
Received message 508 from server100
Received message 535 from server200
I (server100) sent message num 509
Received message 509 from server100
Received message 536 from server200
I (server100) sent message num 510
Received message 510 from server100
Received message 537 from server200
I (server100) sent message num 511
Received message 511 from server100
Received message 538 from server200
I (server100) sent message num 512
Received message 512 from server100
Received message 539 from server200
I (server100) sent message num 513
Received message 513 from server100
The myip
utility returns the IP address of the host.
$ java utils.
myip
$ java utils.myip
Host toyboat.toybox.com is assigned IP address: 192.0.0.1
The pem2der
utility converts an X509 certificate from PEM format to DER format. The .der
file is written in the same directory as the source .pem
file.
$ java utils.
pem2der
pemFile
The name of the file to be converted. The filename must end with a |
$ java utils.
pem2der
graceland_org.pem
Decoding
................................................................
................................................................
................................................................
................................................................
................................................................
PointBase is bundled with WebLogic Server as a sample database. Its documentation is also included at WL_HOME\common\eval\pointbase\docs
, where WL_HOME
is the WebLogic Server installation directory, typically C:\bea\weblogic90
.
The PointBase documentation is also on the PointBase site, at http://www.pointbase.com/support/docs/overview.html.
The WebLogic RMI compiler is a command-line utility for generating and compiling remote objects. Use weblogic.rmic
to generate dynamic proxies on the client-side for custom remote object interfaces in your application, and to provide hot code generation for server-side objects. See "Using the WebLogic RMI Compiler" in Programming WebLogic RMI.
The Schema
utility lets you upload SQL statements to a database using the WebLogic JDBC drivers. For additional information about database connections, see Programming WebLogic JDBC.
$ java utils.
Schema
driverURL
driverClass
[-u
username
]
[-p
password
] [-verbose
]SQLfile
The following code shows a Schema
command line for the examples.utils
package:
$ java utils.Schema
"jdbc:pointbase:server://localhost/demo"
"com.pointbase.jdbc.jdbcUniversalDriver" -u "examples"
-p "examples" examples/utils/ddl/demo.ddl
utils.Schema will use these parameters:
url: jdbc:pointbase:server://localhost/demo
driver: com.pointbase.jdbc.jdbcUniversalDriver
dbserver: null
user: examples
password: examples
SQL file: examples/utils/ddl/demo.ddl
The servicegen
Ant task takes as input an EJB JAR file or a list of Java classes, and creates all the needed Web Service components and packages them into a deployable EAR file.
Web Services are now a J2EE standard, which has resulted in many changes between 8.1 and 9.0 WebLogic Web Services. For information about what has changed between 8.1 and 9.0 Web Services, and what has been deprecated, see "Differences Between 8.1 and 9.0 WebLogic Web Services" in Programming Web Services for Weblogic Server.
For a complete list of Web Services Ant tasks, see Ant Task Reference in Programming Web Services for Weblogic Server.
This Ant task executes build.xml
files that are included within the FileSet
. The task assumes that all of the files defined in FileSet
are valid build files, and executes the Ant
task of each of them.
Make certain that your FileSet
filtering is correct. If you include the build.xml
file that SearchAndBuildTask
is being called from, you will be stuck in an infinite loop as this task will execute the top level build file—itself—forever. See FileSet.
<project name="all_modules" default="all" basedir=".">
<taskdef name="buildAll"
classname="weblogic.ant.taskdefs.build.SearchAndBuildTask"/>
<target name="all">
<buildAll>
<fileset dir="${basedir}">
<include name="**\build.xml"/>
<exclude name="build.xml"/>
</fileset>
</buildAll>
</target>
</project>
The showLicenses
utility displays license information about BEA products installed in this machine.
$ java -Dbea.home=license_location utils.
showLicenses
$ java -Dbea.home=d:\bea utils.showLicense
Generates a web-services.xml
deployment descriptor file from the Java source file for a Java class-implemented WebLogic Web Service.
Web Services are now a J2EE standard, which has resulted in many changes between 8.1 and 9.0 WebLogic Web Services. For information about what has changed between 8.1 and 9.0 Web Services, and what has been deprecated, see "Differences Between 8.1 and 9.0 WebLogic Web Services" in Programming Web Services for Weblogic Server.
For a complete list of Web Services Ant tasks, see Ant Task Reference in Programming Web Services for Weblogic Server.
The system
utility displays basic information about your computer's operating environment, including the manufacturer and version of your JDK, your CLASSPATH
, and details about your operating system.
$ java utils.
system
$ java utils.
system
* * * * * * * java.version * * * * * * *
1.5.0_03
* * * * * * * java.vendor * * * * * * *
BEA Systems, Inc.
* * * * * * * java.class.path * * * * * * *
C:\src_15003jr\bea\weblogic90\server\classes;
C:\dev\src\build\JROCKI~2.0_0\lib\tools.jar;
...
* * * * * * * os.name * * * * * * *
Windows 2000
* * * * * * * os.arch * * * * * * *
x86
* * * * * * * os.version * * * * * * *
5.0
WebLogic Server provides the ValidateCertChain
utility to check whether or not an existing certificate chain will be rejected by WebLogic Server. The utility uses certificate chains from PEM files, PKCS-12 files, PKCS-12 keystores, and JKS keystores. A complete certificate chain must be used with the utility. The following is the syntax for the ValidateCertChain
utility:
java utils.ValidateCertChain -file pemcertificatefilenamejava utils.ValidateCertChain -pem pemcertificatefilenamejava utils.ValidateCertChain -pkcs12store pkcs12storefilenamejava utils.ValidateCertChain -pkcs12file pkcs12filename passwordjava utils.ValidateCertChain -jks alias storefilename [storePass]
Example of valid certificate chain:
Example of invalid certificate chain:
java utils.ValidateCertChain -jks mykey mykeystoreCert[0]: CN=corba1,OU=FOR TESTING ONLY, O=MyOrganization,L=MyTown,ST=MyState,C=US
CA cert not marked with critical BasicConstraint indicating it is a CACert[1]: CN=CACERT,OU=FOR TESTING ONLY, O=MyOrganization,L=MyTown,ST=MyState,C=USCertificate chain is invalid
When executed from the document root directory of your HTTP server, verboseToZip
takes the standard output from a Java application run in verbose mode, finds the Java classes referenced, and creates an uncompressed.zip
file that contains those Java classes.
$ java utils.
verboseToZip
inputFile
zipFileToCreate
$ java -verbose myapplication > & classList.tmp
$ java utils.verboseToZip
classList.tmp app2.zip
This utility compiles and validates a J2EE EAR file, an EJB JAR file, or a WAR file for deployment.
For more information, see "Building Modules and Applications Using wlappc" in Developing Applications with WebLogic Server.
Use the wlcompile
Ant task to invoke the javac
compiler to compile your application's Java files in a split development directory structure. See "Building Applications in a Split Development Directory" in Developing Applications with WebLogic Server.
The wlconfig Ant task enables you to configure a WebLogic Server domain by creating, querying, or modifying configuration MBeans on a running Administration Server instance. For complete documentation on this Ant task, see "Using Ant Tasks to Configure a WebLogic Server Domain" in Developing Applications with WebLogic Server.
The wldeploy
Ant task enables you to perform Deployer
functions using attributes specified in an Ant task. See "Deploying and Packaging from a Split Development Directory" in Developing Applications with WebLogic Server.
You use the wlpackage
Ant task to package your split development directory application as a traditional EAR file that can be deployed to WebLogic Server. See "Deploying and Packaging from a Split Development Directory" in Developing Applications with WebLogic Server.
The wlserver
Ant task enables you to start, reboot, shutdown, or connect to a WebLogic Server instance. The server instance may already exist in a configured WebLogic Server domain, or you can create a new single-server domain for development by using the generateconfig=true
attribute. For complete documentation on this Ant task, see "Starting Servers and Creating Domains Using the wlserver Ant Task" in Developing Applications with WebLogic Server.
The writeLicense
utility writes information about all your WebLogic licenses in a file called writeLicense.txt
, located in the current directory. This file can then be emailed, for example, to WebLogic technical support.
$ java utils.
writeLicense
-nowrite -Dbea.home=path
Optional. Sends the output to |
|
Required. Sets WebLogic system home (the root directory of your WebLogic Server installation). |
$ java utils.writeLicense -nowrite
* * * * * * System properties * * * * * *
* * * * * * * java.version * * * * * * *
1.1.7
* * * * * * * java.vendor * * * * * * *
Sun Microsystems Inc.
* * * * * * * java.class.path * * * * * * *
c:\weblogic\classes;c:\weblogic\lib\weblogicaux.jar;
c:\java117\lib\classes.zip;c:\weblogic\license
...
* * * * * * System properties * * * * * *
* * * * * * java.version * * * * * * *
1.5.0_03
* * * * * * java.vendor * * * * * * *
BEA Systems, Inc.
* * * * * * java.class.path * * * * * * *
C:\src_15003jr\bea\weblogic90\server\classes;
C:\dev\src\build\JROCKI~2.0_0\lib\tools.jar;
...
* * * * * * os.name * * * * * * *
Windows 2000
* * * * * * os.arch * * * * * * *
x86
* * * * * * os.version * * * * * * *
5.0
* * * * * IP * * * * * *
Host myserver is assigned IP address: 192.1.1.0
* * * * * * Location of WebLogic license files * * * * * *
No WebLogicLicense.class found
No license.bea license found in
weblogic.system.home or current directory
Found in the classpath: c:/weblogic/license/license.bea
Last Modified: 08/22/2005 at 12:32:12
* * * * * * Valid license keys * * * * * *
Contents:
Product Name : WebLogic
IP Address : 192.1.1.0-255
Expiration Date: never
Units : unlimited
key : b2fcf3a8b8d6839d4a252b1781513b9
...
* * * * * * All license keys * * * * * *
Contents:
Product Name : WebLogic
IP Address : 192.1.1.0-255
Expiration Date: never
Units : unlimited
key : b2fcf3a8b8d6839d4a252b1781513b9
...
* * * * * * WebLogic version * * * * * *
WebLogic Build: 4.0.x xx/xx/1999 10:34:35 #xxxxx
The wsdl2Service
Ant task is a Web Services tool that takes as input an existing WSDL file and generates the Java interface that represents the implementation of your Web Service and the web-services.xml
file that describes the Web Service. See "Iterative Development of WebLogic Web Services Starting From a WSDL File: Main Steps" in Programming Web Services for Weblogic Server.
The wsdlgen
Ant task is a Web Services tool that generates a WSDL file from the EAR and WAR files that implement your Web Service.
Web Services are now a J2EE standard, which has resulted in many changes between 8.1 and 9.0 WebLogic Web Services. For information about what has changed between 8.1 and 9.0 Web Services, and what has been deprecated, see "Differences Between 8.1 and 9.0 WebLogic Web Services" in Programming Web Services for Weblogic Server.
For a complete list of Web Services Ant tasks, see Ant Task Reference in Programming Web Services for Weblogic Server.
Use the Web Services wspackage
Ant task to package the various components of a WebLogic Web Service into a new deployable EAR file and add extra components to an already existing EAR file.
Web Services are now a J2EE standard, which has resulted in many changes between 8.1 and 9.0 WebLogic Web Services. For information about what has changed between 8.1 and 9.0 Web Services, and what has been deprecated, see "Differences Between 8.1 and 9.0 WebLogic Web Services" in Programming Web Services for Weblogic Server.
For a complete list of Web Services Ant tasks, see Ant Task Reference in Programming Web Services for Weblogic Server.
![]() ![]() |
![]() |
![]() |