Java J2ee Planet

The WebLogic Workshop IDE builds enterprise-class applications that run in the WebLogic Workshop runtime. The applications you build in WebLogic Workshop typically expose systems and data within or between enterprises, typically via web applications and/or web services. As an example, considering an express shipping company. Such a company might want to expose shipment scheduling, tracking and billing data to its business partners via web services so that partners' applications can access the data directly. The company also might want to expose tracking information via one or more web applications so that shipment originators and recipients can check the status of shipments from a web browser. WebLogic Workshop makes it easy to construct common functionality for both applications and then expose that functionality with appropriate interfaces.

In WebLogic Workshop you create and build an application . A WebLogic Workshop application is a J2EE Enterprise Application and ultimately produces a J2EE Enterprise Application Archive (EAR) file. An application may contain: one or more projects libraries and modules security roles This topic introduces applications and their contents. Applications An application in WebLogic Workshop is the collection of all resources and components that are deployed as a unit to an instance of WebLogic Server. It is also the top-level unit of work that you manipulate with WebLogic Workshop IDE. In the IDE, you may have at most one application open at a time.

This topic lists the file types you will encounter in your use of WebLogic Workshop. WebLogic Workshop Application Developer Edition File Types You may use a variety of files to create your application in WebLogic Workshop, some of which you may not be familiar with. The key file types you may encounter in WebLogic Workshop Application Developer Edition are: EJB file, or Enterprise Java Bean. An EJB file contains the Java implementation class for an EJB, with Javadoc annotations that configure the EJB. To learn more about building EJBs in WebLogic Workshop, see Developing Enterprise Java Beans. JCS file, or Java Control Source. A JCS file contains the Java implementation class for a Java control type. There is only one JCS file per Java control. If the Java control is extensible, there may be many JCX files that extend the Java control.

I was doing my environment setup for my current project. The following error was bugged my dev environment. Ofcourse it's solved finally with the solution given below. Error Description: <BEA-001512> <Data Source hifTxDataSource has been successfully created.> <25-Oct-2011 12:22:37 o'clock BST> <Error> <Deployer> <BEA-149205> <Failed to initialize the application ' T***r .ear' due to error weblogic.management.DeploymentException : The application T***r .ear contains a SubDeploymentMBean with a name H******t .jar however there is no module in the application with that URI or context-root.. weblogic.management.DeploymentException : The application T***r .ear contains a SubDeploymentMBean with a name BtChaps.jar however there is no module in the application with that URI or context-root. at weblogic.application.internal.flow.CreateModulesFlow.validateTargets( CreateModulesFlow.java:104 ) Solution: Just go to a...

Domain • A domain is an interrelated set of WebLogic Server resources that are managed as a unit. • A domain contains the application components deployed in the domain, and the resources and services required by those application components and the server instances in the domain • A domain can include multiple clusters. Admin server • In each domain, only one WebLogic Server instance acts as the Administration Server. • This server instance which configures, manages, and monitors all other server instances and resources in the domain. • Each Administration Server manages one domain only. If a domain contains multiple clusters, each cluster in the domain has the same Administration Server. Managed server It is also a weblogic server instance. A domain includes one or more WebLogic Server instances, which can be clustered, non-clustered, or a combination of clustered and non-clustered instances. Cluster Cluster can run ...

These topics show how to develop Enterprise JavaBeans. WebLogic Workshop provides you with the tools to make EJB development much easier, taking care of many implementation details for you and allowing you to focus on design. Note . WebLogic Workshop 8.1 supports the development, importing, and building of EJB2.0 compliant Enterprise JavaBeans. In addition, the WebLogic Platform supports the deployment only of EJB1.1 compliant Enterprise JavaBeans. Getting Started with EJB Project When you are building WebLogic platform applications, EJB project is the development environment for Enterprise JavaBeans. EJB project provides a number of tools that facilitate the development of the EJBs which encompass the business logic for your enterprise application. This topic provides an overview of EJBs and EJB project in platform applications. It includes the following sections: What is an Enterprise JavaBean? What is EJB Project? EJB Project and ejbgen Tags Building and Deploying E...

Interactions between software components can be synchronous or asynchronous . An interaction is synchronous if the caller of a method must wait for the method's work to complete before the caller can continue its processing. An interaction is asynchronous if the called method returns immediately, allowing the caller to continue its processing without delay. An asynchronous interaction typically initiates a computation but does not wait for the result to be available, which means it must provide some way for the caller to obtain the results of the computation at a later time. The distributed nature of web applications introduces unpredictable and sometimes very long latencies, which means it may take an operation a long time to complete. If a business process executing over the network involves human interaction at the back end, an operation can take on the order of days. If all interactions over the web were synchronous, clients with pending operations could consume resources ...

The link below provides you complete knowledge about Understanding WebLogic Server J2EE Applications, Developing WebLogic Server J2EE Applications, WebLogic Server Application Classloading, WebLogic Server Packaging, WebLogic Server Deployment. You can download all the pages in a pdf format with the link provided on the page. Encyclopedia of WebLogic Server and It’s Application

  The following overview sets out the aims of security and the security technologies available in WebLogic Workshop.   Security Goals   All security technologies are designed to achieve three basic goals. 1.     Authentication of participants When a participant is authenticated it means that there is some assurance that the participant really is who they say they are. Different scenarios call for different levels of authentication. In some cases, only the web resource needs to be authenticated, while the client can remain anonymous. For example, if your web resource takes customer credit card numbers, you want your customers to have peace of mind that they are providing their card numbers to you, and not some malicious third party. But your customers may remain anonymous. In other cases, the web resource will want proof of identity from its clients. For example, if a bank provided online access to its customer's checking accounts, the bank s...

Welcome to portal development. This section of the help system provides overview information, reference topics, and procedures that guide you through the portal development process using the WebLogic Workshop Portal Extensions. The WebLogic Workshop Portal Extensions provide more than a powerful, flexible, extensible framework for surfacing applications in portals. They also provide personalization, campaign, and behavior tracking services, a rules engine, JSP tags, integration services, intelligent administration, reusable samples, and a complete API. Choose from the following subsections to learn more about WebLogic Portal, explore the power of the product with tutorials and samples, start developing or integrating your own portal applications, or access reference information. Overview Introduces portals and the WebLogic Portal architecture and provides guidance on getting started with WebLogic Portal. Developing Portal Applications Provides instructions on ad...