Oracle Beehive

Beehive Transport Infrastructure (BTI)
The Beehive Transport Infrastructure (BTI) enables connectivity between the Client and Application Tiers by providing the network-level infrastructure for both client-to-server and server-to-server communications.Specifically, the BTI provides port and connection management for Microsoft Outlook (with Oracle Beehive Integration for Outlook) and non-HTTP, standard-based clients through its proprietary multiplexor protocol (MX).In a typical enterprise client/server deployment, clients connect through a series of networks to a known port on a known server.In many cases, the communication channels must traverse firewalls, load balancing routers, forward and reverse proxies, and demilitarized zones (DMZs).The BTI is designed for deployment in these complex network infrastructures, while providing optimal port and connection management.The BTI is a bundled component of the Oracle Beehive server so it is always provided whether we deploy Oracle Beehive in the Application Tier or in a DMZ(Demilitarized Zone).The latter case provides another layer of security between clients connecting to the system and internal components such as Oracle Database. This increased level of security and control over client connections is particularly beneficial when client connections are expected to originate from points outside of our network, such as from the Internet or from other private networks.Oracle Beehive also provides Oracle HTTP Server, which enables client connectivity over HTTP/HTTPS. This can be leveraged in cases where HTTP/HTTPS is the preferred method of enabling client connections that originate from external locations.
Posted by SAP BASIS ADMIN at 2:21 PM
Labels: Beehive Transport Infrastructure (BTI), beehivetransportinfrastructure

Oracle Beehive Architecture
Oracle beehive is built upon J2EE with a suite of Oracle Products including Oracle database,Oracle Application Server and has a multi-tier architecture.Four Major tiers of Oracle Beehive are :1) Client Tier2) Application Tier3) Data Tier4) Ancillary TierClient Tier :1) The Client Tier is the face of the system and includes all supported clients and devices,including integration with Microsoft Outlook and a command-line tool for system administration.2) Oracle Beehive also supports clients and devices that leverage the following standardized protocols:1.Calendaring Extensions for WebDAV (CalDAV)2. Extensible Messaging and Presence Protocol (XMPP)3. File Transfer Protocol (FTP)4. Internet Message Access Protocol (IMAP)5. Push Internet Message Access Protocol (P-IMAP)6. Open Mobile Alliance Data Synchronization (OMA-DS)7. Simple Mail Transfer Protocol (SMTP)8. Web-based Distributed Authoring and Versioning (WebDAV)3) The open nature of the Oracle Beehive platform also enables developers to build and implement custom clients in the Client Tier using Oracle Beehive Web services.Give Note On Oracle Beehive Web Services:-Oracle Beehive Web Services is built on the Oracle Beehive Java applicationprogramming interface (API) as an abstract representation of the Oracle Beehive object model. It provides Web Services Description Language (WSDL) files, enabling developers to invoke its services from custom applications through open standards such as Simple Object Access Protocol (SOAP) 1.2 and Web Services Security (WS-Security), which is based on SOAP and includes Security Assertions Markup Language (SAML).With Oracle Beehive Web Services, developers can build and integrate Webapplications with Oracle Beehive in any environment that can generate a proxyimplementation from WSDLs, including non-OC4J environments such as Microsoft .NET. To build such applications, developers can user whatever development toolsthat suit their needs, such as Oracle JDeveloper, Eclipse IDE, and Microsoft Visual Studio.Application Tier :1) The Application Tier is the core of the system and includes all Oracle Beehive server components, including interoperable, function-specific services that provide the system’s enterprise collaboration features.2) The Application Tier supports multiple Oracle Beehive server instances.3) Each Oracle Beehive server instance includes required components of Oracle Application Server 10g, which itself hosts the Oracle Beehive services, including:1. Oracle HTTP Server: The Web server component of Oracle Application Server 10g. Enables connections between supported clients over HyperText Transport Protocol (HTTP) and Secure HyperText Transport Protocol (HTTPS).2. Oracle Application Server Containers for J2EE (OC4J): J2EE v1.4 -compliant containers that provide an infrastructure for deploying, undeploying, and redeploying J2EE-compliant applications and modules. Oracle Beehive services are deployed in OC4J containers.At the time of Installation Oracle Application Server components are pre-bundled and installed by default.Each Oracle Beehive server instance also includes the Beehive Transport Infrastructure (BTI), which enables connectivity between supported clients and Oracle Beehive through its proprietary multiplexor protocol (MX).Data Tier (Database Tier) :1) The Data Tier is the information store for Oracle Beehive and contains Oracle Database, either as a single, standalone database instance or an Oracle RealApplication Cluster (Oracle RAC).2) All system configuration and collaborative data for Oracle Beehive is stored in Oracle Database.3) The Data Tier provides Oracle Database a layer of separation from the other tiers,ensuring, among other things, optimized security and system performance. 4) Only the Database Access Framework (provided by Oracle Beehive) can access the Data Tier.5) Oracle Beehive services cannot access the Data Tier directly and must make all connections through the schemas provided by the Database Access Framework.6) Database Access Framework in built on JDBC (Java Database Connectivity).7) Oracle ata tier is made of Beehive schemas.Oracle Beehive schemas logically segregate system, configuration, and collaborative data, and application code.Two types of schemas are :1. Code Schema2. Data SchemaAncillary Tier :1) The Ancillary Tier contains any optional servers and applications that are external to the Oracle Beehive server.2) Typically, components in this tier are optional because Oracle Beehive already provides many of these capabilities, such as user directories,e-mail, and time management.3) Oracle Beehive supports Ancillary Tier components to provide enterprises flexibility in their deployment choices, especially for those that want to leverage existing or specialized component investments.4) In either case, enterprises can choose to implement the components of this tier to coexist with or access key aspects of Oracle Beehive.Examples of supported Oracle and third-party components in the Ancillary Tierinclude:1. Oracle Internet Directory2. Oracle BPEL Process Manager3. Oracle Secure Enterprise Search4. IBM Tivoli5. Microsoft Active Directory Server6. Microsoft Exchange Server7. Sun Java Directory Server8. Symantec Scan Engine
Posted by SAP BASIS ADMIN at 2:05 PM
Labels: Oracle Beehive Architecture

Starting And Stopping Oracle Beehive
Oracle beehive needs to be started after starting the database instance. If the database instance is shutdown before oracle beehive all the Oracle beehive managed components and services,processes are terminated.The command-line utility beectl is used to administer the starting and stopping of Oracle beehive components.beectl can be invoked in Shell mode by executing $ORACL_HOME/beehive/bin/beectl.This shows the prompt:beectl>When the above prompt appears beectl is in shell mode. We don't have to specify the term "beectl" preceeding every command.Some major administrative tasks relevant to beectl are :Starting All Oracle Beehive Managed Components :To start all Oracle Beehive managed components using the beectl command-lineutility, use the start command with the --all option.The following example illustrates the command with the --all option, as well as the resulting output:beectl> start --allStarting all the beehive components ...Successfully started all the beehive components.Operation completed in <#> ms.Stopping all Oracle Beehive Managed Components :To stop all Oracle Beehive managed components using the beectl command-lineutility, use the stop command with the --all option.The following example illustrates the command with the --all option, as well as the resulting output:beectl> stop --allStopping all the beehive components ...Successfully stopped all the beehive components.Operation completed in <#> ms.Restarting All Oracle Beehive Managed Components :To restart all Oracle Beehive managed components using the beectl command-line utility, use the restart command with the --all option.The following example illustrates the command with the --all option, as well as the resulting output:beectl> restart --allStopping all the beehive components ...Successfully stopped all the beehive components.Operation completed in <#> ms.Starting all the beehive components ...Successfully started all the beehive components.Operation completed in <#> ms.Determine the component Identifiers:1. Determine the component identifiers of all managed components by running the status command:beectl> status--------------------------------------------+----------------+---------------Component identifier Component type Status --------------------------------------------+----------------+---------------BTI_redirector_instance1.host.domain.com Bti RUNNING--------------------------------------------+----------------+---------------BEEAPP_instance1.host.domain.com ManagedOc4j RUNNING--------------------------------------------+----------------+---------------BEECORE_instance1.host.domain.com ManagedOc4j RUNNING--------------------------------------------+----------------+---------------BEEMGMT_instance1.host.domain.com ManagedOc4j RUNNING--------------------------------------------+----------------+---------------oc4j_soa_instance1.host.domain.com ManagedOc4j RUNNING--------------------------------------------+----------------+---------------ohs_instance1.host.domain.com HttpServer RUNNING--------------------------------------------+----------------+---------------The component identifier is a string of characters, including the fully qualified host name preceded by a descriptive prefix.2. Take note of the managed component identifier.For example, from the output returned by the status command in step 1, we candetermine that the component identifier of the Oracle Beehive Applications is:BEEAPP_instance1.host.domain.com.Starting a Specific Managed Component :1. Determine the component identifier of the managed component to start.Use status command.2. Start a specific Oracle Beehive managed component using the beectlcommand-line utility, use the start command with the --component option andargument.For example to start BEEAPP_instance1.host.domain.combeectl> start --component BEEAPP_instance1.host.domain.comStarting beehive component "BEEAPP_instance1.host.domain.com" ...Successfully started beehive component "BEEAPP_instance1.host.domain.com".Operation completed in <#> ms.To start more than one managed component, specify the--component option multiple times: once before each argument.Forexample: start --component --component... --component Stop a specific Oracle Beehive managed component :1. Determine the ID of the managed component to stop.Use status command.2. Stop a specific Oracle Beehive managed component using the beectlcommand-line utility, use the stop command with the --component option andargument.For example to stop the component BEEAPP_instance1.host.domain.combeectl> stop --component BEEAPP_instance1.host.domain.comStopping beehive component "BEEAPP_instance1.host.domain.com" ...Successfully stopped beehive component "BEEAPP_instance1.host.domain.com".Operation completed in <#> ms.1 of 1 component(s) stopped successfully.To stop more than one managed component, specify the--component option multiple times: once before each argument.For example:stop --component --component... --component Restarting a Specific Managed Component :1. Determine the ID of the managed component to restart. Use "status command".2. Restart a specific Oracle Beehive managed component using the beectlcommand-line utility, use the restart command with the --component optionand argument.For example to restart a managed component BEEAPP_instance1.host.domain.combeectl> restart --component BEEAPP_instance1.host.domain.comStopping beehive component "BEEAPP_instance1.host.domain.com" ...Successfully stopped beehive component "BEEAPP_instance1.host.domain.com".Operation completed in <#> ms.Starting beehive component "BEEAPP_instance1.host.domain.com" ...Successfully started beehive component "BEEAPP_instance1.host.domain.com".Operation completed in <#> ms.1 of 1 component(s) restarted successfully.To restart more than one managed component, specify the--component option multiple times: once before each argument.For example: restart --component --component... --component Stopping all Oracle Beehive Processes :If the Oracle Database instance was stopped before stopping Oracle Beehive,we have to shutdown all of Oracle Beehive Processes. When this occurs, the stop command with the --all option may not be able to properly stop all of the managed components.In such a case,Oracle recommends using the shutdown command.To stop all Oracle Beehive processes, including all managed components and services,using the beectl command-line utility, use the shutdown command. No options are required.The following example illustrates the command to use, as well as the resulting output:beectl> shutdownShutting down all beehive components ...Successfully shutdown all beehive components.Operation completed in <#> ms.
Posted by SAP BASIS ADMIN at 6:18 AM
Labels: Starting And Stopping Oracle Beehive
Wednesday, May 14, 2008

Oracle Beehive Command-Line Utility - beectl utility/beectl
Oracle Beehive Command-line utility is beectl.This utility is installed in $ORACLE_HOME/beehive/bin directory.The Oracle Beehive beectl utility is always used in conjunction with a qualifying command.Syntax :beectl command --option where,command - represents the beectl command--option - represents an available option(s) to use with the command - represents a valid argument passed with an option
Posted by SAP BASIS ADMIN at 1:47 PM
Labels: beectl, Oracle Beehive Command-Line Utility - beectl utility

Oracle Beehive - Terms And Concepts
Few important terms and concepts of Oracle beehive are discussed below.Following are the important terms and concepts.1) Services2) Enterprises and Organizations3) Workspaces4) Entities, Actors, and ArtifactsServices :1) A service is a discrete implementation of specific functionality that users and other services can leverage to accomplish a task.2) The capabilities and interactions of services enable the full scope of functionality that Oracle Beehive provides.3) Through supported client devices and graphical user interfaces (GUIs), Oracle Beehive visually exposes to users the features and functions of some services. Other services operate in the background and play low-level roles within the system such as enabling key integrations with other systems. Examples of services whose features Oracle :Beehive exposes visually to users include the E-mail Service, the Time Management (Calendar) Service, and the Content Management Service.Examples of services whose roles enable underlying system functionality and are, therefore, mostly hidden from users include :the Authentication Service, the Policy Service, and the Coexistence Service.Enterprises and Organizations :1) An enterprise is a logical collection of the entities that comprise an Oracle Beehive deployment, such as organizations, workspaces, and users.2) Organizations are narrowly defined groups within an enterprise. Typically, an organization is defined by a department or line of business, but it can also be based on a project or other criteria.3) The hierarchical relationship between enterprises and organizations in Oracle Beehive provides a logical structure for organizing users, groups, and workspaces, while enabling many aspects of the collaborative functionality offered by the system.4) This structure also enables system administrators to more easily manage users and workspaces through their organizational associations.Workspaces :1) A workspace is a both a virtual location and a container that provides Oracle Beehive users a place to collaborate, and enables them to create, view, store, access, and manage the artifacts related to their collaborations.2) From the user perspective,workspaces appear in supported Oracle Beehive clients.3) Workspaces expose to users the many collaborative services that Oracle Beehive provides, enabling users to seamlessly perform a wide range of collaborative activities in a single, intuitive place. In workspaces, users can create, view, and manage e-mail messages, calendar appointments, meetings, tasks, contacts, instant messages, and documents, and so forth.Oracle Beehive provides two types of workspaces:1) Team workspaces2) Personal workspacesA team workspace is a workspace that is shared by a team or group, andthat supports the content and collaborative activities of its members.A personal workspace is a workspace that is primarily used by an individual user and that contains a mix of a user’s private content and content from the team workspaces in which the user is a member.Workspaces can be created for specific teams, projects, processes, or whatever criteria that makes sense. Based on this, workspaces are always in context for users and present only the features and content that are relevant to their particular activities.Entities, Actors, and Artifacts :1) An entity is a securable, identifiable object in Oracle Beehive, such as a service, user,workspace, and artifact. In essence, every object in Oracle Beehive is an entity.2) An actor is an entity, such as a user or service, that acts upon other entities.3) Artifacts are another entity sub-class and represent objects that users can view, create,modify, or delete. Artifacts are the results of communications and other collaborative activities, and include e-mail messages, appointments, meetings, tasks, online discussions, notes, and documents. Oracle Beehive stores artifacts in Oracle Database.
Posted by SAP BASIS ADMIN at 12:40 PM
Labels: Oracle Beehive - Terms And Concepts

Hardware Requirements - Beehive Installation
Following are the minimum hardware requirements that need to be met before installing Oracle Beehive :1) Disk Space: 2.6 GB2) Swap Space: 2,048 MB3) Memory:– Oracle Beehive: 2 GB RAM– Oracle Beehive for DMZ(Demilitarized Zone) : 1 GBThis disk space requirement includes Oracle Beehive binary alone. It doesn't include the target database.Memory estimate is for Oracle Beehive application and doesn't include Target database.
Posted by SAP BASIS ADMIN at 12:30 PM
Labels: Hardware Rrquirements - Beehive Installation

Oracle Enterprise Manager Grid Control Requirements - Oracle Beehive Installation
If we want to install the Oracle Beehive Provisioning Application, which allows us to install Oracle Beehive from Oracle Grid Control, we must have Oracle Enterprise Manager 10g Release 4 Grid Control (10.2.0.4).
Posted by SAP BASIS ADMIN at 12:25 PM
Labels: Oracle Enterprise Manager Grid Control Requirements - Oracle Beehive Installation