eDesigner: deploy to Sun AS 8.1

Hello,

Documented in \repository\server\webapps\eGate_Sys_Admin_Guide.pdf

P.44,

4.1 Prerequisites

Before you start the deployment process, perform the following steps:

1 Install Sun Java System Application Server Enterprise Edition 8.1 from the Sun Java

Enterprise System 4 installer.

2 Apply the appropriate patch to Sun Java System Application Server. The patch that

you need depends on the operating system. You can obtain the patch from SunSolve

Online.

The patch IDs for the package-based patches are:

􀂌 Sun Solaris (SPARC): 119166-15

Chapter 4 Section 4.1

Deploying Applications to Sun Java?System Application Server Prerequisites

eGate Integrator System Administration Guide 45 Sun Microsystems, Inc.

􀂌 Sun Solaris (Intel x86): 119167-15

􀂌 Linux: 119168-15

􀂌 Windows: 122848-01

The patch IDs for the file-based patches are:

􀂌 Sun Solaris (SPARC): 119169-07

􀂌 Sun Solaris (Intel x86): 119170-07

􀂌 Linux: 119171-07

􀂌 Windows: 119172-07

3 Open the server.policy file in the

Sun_JES_install_dir\ApplicationServer\domains\domain_name\config

directory and add the following permissions to the end:

grant {

// Java CAPS needs access to the class loader

permission java.lang.RuntimePermission "getClassLoader";

// Java CAPS needs custom classloaders in some cases

permission java.lang.RuntimePermission "createClassLoader";

// Java CAPS policy requirement

permission java.security.SecurityPermission "setPolicy";

permission java.security.SecurityPermission "getPolicy";

permission java.security.SecurityPermission "getProperty.policy.url.*";

permission java.security.SecurityPermission "setProperty.policy.url.*";

// Java CAPS for the SAP eway

permission java.lang.RuntimePermission "setContextClassLoader";

// Java CAPS uses the MBeanServer

permission javax.management.MBeanServerPermission "*";

permission javax.management.MBeanPermission "*", "*";

permission javax.management.MBeanTrustPermission "register";

//

// Java CAPS Log4J support (obsolete) (log4j file roll-over needs delete)

permission java.io.FilePermission "<<ALL FILES>>", "delete";

// Java CAPS Odette eWay support requires execute permission

permission java.io.FilePermission "<<ALL FILES>>", "execute";

// Java CAPS HTTP eWay

permission java.lang.RuntimePermission "setFactory";

// Java CAPS tcpip inbound eway added "accept,resolve" to SocketPermission

// Java CAPS BPEL debugger added "listen" to SocketPermission

permission java.net.SocketPermission "*", "connect,listen,accept,resolve";

// Java CAPS needs these permissions so the Bouncy Castle provider can be used

permission java.security.SecurityPermission "insertProvider.BC";

permission java.security.SecurityPermission "removeProvider.BC";

permission java.security.SecurityPermission "putProviderProperty.BC";

// Java CAPS needs this permission so the JMX remote connector can be used

permission javax.security.auth.AuthPermission "getSubject";

// Java CAPS: Hessian connector for JMX4J for EM; also for BPEL debugger

permission java.lang.reflect.ReflectPermission "suppressAccessChecks";

// Java CAPS: for BPEL debugger

permission java.io.SerializablePermission "enableSubstitution";

Chapter 4 Section 4.1

Deploying Applications to Sun Java?System Application Server Prerequisites

eGate Integrator System Administration Guide 46 Sun Microsystems, Inc.

// Java CAPS: for EM to use SSL

permission javax.net.ssl.SSLPermission "setHostnameVerifier";

permission javax.net.ssl.SSLPermission "getSSLSessionContext";

};

4.1.1 Prerequisites for Enterprise Designer

If you want to use Sun SeeBeyond Enterprise Designer for deployment, then perform

the following steps:

1 Copy the following from the Sun_JES_install_dir\ApplicationServer\lib

directory to the Sun_JavaCAPS_install_dir\edesigner\plugins\SunoneServer

directory:

􀂊 appserv-admin.jar

􀂊 appserv-rt.jar

􀂊 jmxremote.jar

􀂊 jmxremote_optional.jar

􀂊 deployment folder (which contains the sun-as-jsr88-dm.jar file)

2 Go to the

Sun_JES_install_dir\ApplicationServer\domains\domain_name\config

directory and open the domain.xml file.

3 Set the security-enabled attribute for the appropriate HTTP listener to false. This

action is performed depending on the HTTP port you are going to use for

deployment. In the following example, the user is using HTTP port 4850 for

deployment, and therefore has to enable the security attribute to the related port.

<http-listener

acceptor-threads="1"

address="0.0.0.0"

blocking-enabled="false"

default-virtual-server="__asadmin"

enabled="true"

family="inet"

id="admin-listener"

port="4850"

security-enabled="false"

server-name=""

xpowered-by="true">

</http-listener>

JavaCKa at 2007-7-8 23:07:16 >