This topic provides steps to install the Client Development Kit (CDK) for z/OS using command-line tools to configure and deploy client applications for WebSphere Application Server.
The clientConfig command is used to start the Application Client Resource Configuration Tool (ACRCT). The most common task that you perform with the ACRCT is opening and modifying the components of enterprise archive (EAR) files.
The clientUpgrade command migrates the V5.0.x and V6.0.x client resources to the V6.1 level resources.
The endptEnabler command enables a set of Web services within an EAR file.
The Java2WSDL command maps a Java class to a Web Services Description Language (WSDL) file by following the Java API for XML-based Remote Procedure Call (JAX-RPC) specification.
The WSDL2Java command is run against the WSDL file to create Java APIs and deployment descriptor templates according to the JAX-RPC and Web Services for Java 2 Platform, Enterprise Edition (J2EE) specifications.
The wsdeploy command adds WebSphere product-specific deployment classes to a Web services-compatible enterprise application EAR file or an application client Java archive (JAR) file.
The EJB deployment tool provides a command-line interface (ejbdeploy) that you can use to generate enterprise bean deployment code. To learn more about this command line refer to the Application Server Toolkit information center.
The UDDI Utility Tools is a suite of functions that can be used to migrate, move, and copy UDDI Version 2 entities, including child entities and their respective Version 2 entity keys, into a Version 3 UDDI Registry.
$WAS_HOME/downloads/ClientDevKit/setup.exeWhen the Client Development Kit is installed, the directory looks as if it is a Windows platform directory.
To install the Client Development Kit: