es2 reference deployment architecture

1
BlueCoat Reverse Proxy Inner Firewall Outer Firewall STORAGE TIER DATABASE MANAGEMENT SYSTEM TIER MIDDLEWARE TIER DMZ WEB TIER The reverse proxy is configured so that LiveCycle ES Rights Management policy-applied documents can contain a public URL that this device can translate into the virtual IP address of the LiveCycle ES appserver cluster. REST/SOAP and AMF3 work over HTTP/HTTPS This device keeps track of the health of the members of the LiveCycle ES cluster and distributes load among the healthy members. Servers in the web server farm (optional) caches static HTML pages, images etc so that requests for these do not hit the LiveCycle ES2 cluster members. LiveCycle ES2 business applications live on this tier. Members of this cluster have a virtual IP address configured with an associated name in the corporate DNS server LiveCycle ES2 configuration metadata, Content Services ES2 metadata as well as the LiveCycle repository are managed by this tier. LiveCycle connects to this tier via multiple JDBC connection pools maintained by the appserver cluster. Final persistence of all data happens in this layer. This includes storage of the structured data belonging to the DBMS, as well as unstructured file data belonging to Content Services ES2 Storage HTTP/HTTPS HTTP/HTTPS HTTP/HTTPS JDBC SMB/NFS F5 Networks BIG-IP 3600 Adobe LiveCycle ES2 – Reference Architecture for Cluster Deployment Jayan Kandathil

Upload: smitasamrat

Post on 13-Sep-2015

221 views

Category:

Documents


6 download

DESCRIPTION

Deployment Architecture

TRANSCRIPT

  • UID

    1

    2UID

    1

    2

    UID

    1

    2 UID

    1

    2

    BlueCoat Reverse Proxy

    Inner Firewall

    Outer Firewall

    STORAGE TIER

    DATABASE MANAGEMENT SYSTEM TIER

    MIDDLEWARE TIER

    DMZ

    WEB TIER

    The reverse proxy is configured so that LiveCycle ES Rights Management policy-applied documents can contain a public URL

    that this device can translate into the virtual IP address of the LiveCycle ES appserver cluster. REST/SOAP and AMF3 work

    over HTTP/HTTPS

    This device keeps track of the health of the members of the LiveCycle ES cluster and distributes load among the healthy

    members.

    Servers in the web server farm (optional) caches static HTML pages, images etc so that requests for these do not hit the

    LiveCycle ES2 cluster members.

    LiveCycle ES2 business applications live on this tier. Members of this cluster have a virtual IP address configured with an

    associated name in the corporate DNS server

    LiveCycle ES2 configuration metadata, Content Services ES2 metadata as well as the LiveCycle repository are managed by

    this tier. LiveCycle connects to this tier via multiple JDBC connection pools maintained by the appserver cluster.

    Final persistence of all data happens in this layer. This includes storage of the structured data belonging to the DBMS, as well as unstructured file data belonging to Content Services ES2 Storage

    H

    T

    T

    P

    /

    H

    T

    T

    P

    S

    H

    T

    T

    P

    /

    H

    T

    T

    P

    S

    H

    T

    T

    P

    /

    H

    T

    T

    P

    S

    J

    D

    B

    C

    S

    M

    B

    /

    N

    F

    S

    F5 Networks BIG-IP 3600

    Adobe LiveCycle ES2 Reference Architecture for Cluster Deployment

    Jayan Kandathil

    Page-1