NAC deployment on Remote Branch

Hello guys,
I need help for deploying Cisco NAC on remote branch. i did all the necesary steps & configs but still no luck, On main site we have OOB-Real IP Gateway deployment. all the campus is deployed but for remote branch it is not working, we have inbetween firewalls & routers(offcorse) i have allowed IP any to NAC Server & Manager. but still no luck.
Is there any point i am missing do i have to do some extra config for remote branch ?

Did you generate the certificate on the CAS so it resolved to the untrusted interface?
You can find the managed subnet configuration here:
http://www.cisco.com/en/US/docs/security/nac/appliance/configuration_guide/49/cas/s_addSrvr.html#wp1060206
Also keep in mind, any changes you make related to certificates or network settings, you must reboot the CAS for thoses changes to take into effect. Please reboot the CAS and see if that restore your issue.
I also wanted to verify how you were able to get the download page? The reason is that if you are not being automatically redirected to the page then most likely all the client traffic isnt being redirect either. For troubleshooting you may want to change the discovery host of the agent to the untrusted ip of the CAS and see if that causes the agent to pop up.
Thanks,
Tarik Admani

Similar Messages

Remote branch guest and Print services

We are deploying guest internet services in our remote branches, using a setup of WLC4402 and LAPs.
These guests require print services at the remote branch.
The DMZ will not be routed to the remote branches, and we prefer if the remote branch printer is not given a
permanent wireless guest account.
Is there a solution whereby we can connect the printer to these wireless guests.

Hi,
Sorry for delaying in reply.
Linux clients see page count. I've paused printing and checked some documents. Property page from a linux client document shows as this:
Documents sent from windows clients show same but they've document name and page count.
SPL archive copied from spooler printer on Windows server shows that info is present too:
%!PS-Adobe-3.0
%%Creator: cairo 1.9.5 (http://cairographics.org)
%%CreationDate: Thu Jun 19 14:15:48 2014
%%DocumentData: Clean7Bit
%%LanguageLevel: 2
%%DocumentMedia: Letter 612 792 0 () ()
%%Orientation: Portrait
%%For: (testuser)
%%Title: (Phaser 5500 Descarga del archivo)
%RBINumCopies: 1
%%Pages: (atend)
%%BoundingBox: (atend)
%%EndComments
%%BeginProlog
%%BeginFeature: *JobPatchFile 1
% Default Definitions
userdict /xerox$pagedevice <<
/MediaClass null
/MediaPosition null
/PageSize [612 792]
/TraySwitch true
/ManualFeed false
/ImagingBBox null
/ProcessColorModel /DeviceGray
/DeviceRenderingInfo currentpagedevice 1 index get 1 dict copy
/PostRenderingEnhance false
/Install {
xerox$old_install xerox$flip {
currentpagedevice /PageSize get aload pop translate 180 rotate
} if
>> put
<--- snip snip REMOVED FOR SIMPLICITY snip snip ------>
showpage
%%Trailer
%%Pages: 1
%%BoundingBox: 0 0 612 792
%%EOF
Linux client used official PPD file downloaded from xerox webpage for linux
cups. Windows server uses Xerox Global Print Driver PS 5347.600.0.0 type 3 with
Render print jobs on client computers as suggested by Alan before.
Any other idea?

Problem getting bindings in managed bean after deployment on remote weblogic

We have a Fusion Web application successfully running on Jdev 12c and its integrated wls server with Oracle 12c database configured as a DataSource. We created an ear file from JDev and deployed it on remote wls servers. The initial login .jspx page came up without any issues. Upon entering the login credentials in the browser and trying to enter the application, we are getting a Null Pointer exception. Looking at the logs, the null pointer is thrown when its trying to get the bindings in the managed bean.
       BindingContext bctx;
        bctx = BindingContext.getCurrent();
        DCBindingContainer bc =(DCBindingContainer)getBindings();
        DCBindingContainer bindings = (DCBindingContainer)bctx.getCurrentBindingsEntry();
        DCDataControl dataControl = bindings.findDataControl("LoginAMDataControl");
variable bindings is Null. What needs to be configured/changed while packaging the ear file for deployment on remote wls 12c? Please advise and appreciate your response.

try this...
      public String test() {
      DCIteratorBinding binding= getItrtBindings("findAdByNumberIterator");
      Row row = binding.getCurrentRow();
      String dn = (String)row.getAttribute("docNumber");
      System.out.println("docNumber " + dn);
      return dn;
       private BindingContainer bindings;
       public BindingContainer getBindings() {
          return this.bindings;
       public void setBindings(BindingContainer bindings) {
           this.bindings = bindings;
    protected DCIteratorBinding getItrtBindings(String binding){
        DCIteratorBinding outIterBinding = getBindingsForDCB().findIteratorBinding(binding);
        return outIterBinding;
    public DCBindingContainer getBindingsForDCB() {
        if (this.bindings == null) {
            FacesContext fc = FacesContext.getCurrentInstance();
            this.bindings =(DCBindingContainer)fc.getApplication().evaluateExpressionGet(fc,"#{bindings}",DCBindingContainer.class);
        return (DCBindingContainer)this.bindings;
    }

Can not deploy a remote storage node

Hello,
I have started successfully two SNA at two node, because we can ping to each other. But when I use admin console to to deploy the first remote storage node, it always shows the error "Connection refused to host: localhost". I use the command line to deploy a remote storage node. There is the same problem.
Dose some one know how to solve it? Thank you advanced.
Here is the error log:
in createPlan: Oracle NoSQL DB 11gR2.1.2.123 oracle.kv.impl.fault.OperationFaultException: Plan 16[Plan-16] finished in state ERROR. Problem during plan execution: Connection refused to host: localhost; nested exception is: java.net.ConnectException: Connection refused
caused by:
oracle.kv.impl.admin.AdminFaultException
Oracle NoSQL DB 11gR2.1.2.123 oracle.kv.impl.fault.OperationFaultException: Plan 16[Plan-16] finished in state ERROR. Problem during plan execution: Connection refused to host: localhost; nested exception is:
     java.net.ConnectException: Connection refused
Oracle NoSQL DB 11gR2.1.2.123 oracle.kv.impl.fault.OperationFaultException: Plan 16[Plan-16] finished in state ERROR. Problem during plan execution: Connection refused to host: localhost; nested exception is:
     java.net.ConnectException: Connection refused oracle.kv.impl.fault.OperationFaultException: Plan 16[Plan-16] finished in state ERROR. Problem during plan execution: Connection refused to host: localhost; nested exception is:
     java.net.ConnectException: Connection refused
     at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:601)
     at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:198)
     at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:184)
     at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:110)
     at java.rmi.server.RemoteObjectInvocationHandler.invokeRemoteMethod(RemoteObjectInvocationHandler.java:178)
     at java.rmi.server.RemoteObjectInvocationHandler.invoke(RemoteObjectInvocationHandler.java:132)
     at $Proxy8.getSerialVersion(Unknown Source)
     at oracle.kv.impl.util.registry.RemoteAPI.(RemoteAPI.java:32)
     at oracle.kv.impl.sna.StorageNodeAgentAPI.(StorageNodeAgentAPI.java:51)
     at oracle.kv.impl.sna.StorageNodeAgentAPI.wrap(StorageNodeAgentAPI.java:58)
     at oracle.kv.impl.util.registry.RegistryUtils.getStorageNodeAgent(RegistryUtils.java:243)
     at oracle.kv.impl.admin.plan.task.DeploySN.call(DeploySN.java:94)
     at oracle.kv.impl.admin.plan.task.DeploySN.call(DeploySN.java:35)
     at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
     at java.util.concurrent.FutureTask.run(FutureTask.java:138)
     at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
     at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
     at java.lang.Thread.run(Thread.java:662)
Caused by: java.rmi.ConnectException: Connection refused to host: localhost; nested exception is:
     java.net.ConnectException: Connection refused
     ... 18 more
Caused by: java.net.ConnectException: Connection refused
     at java.net.PlainSocketImpl.socketConnect(Native Method)
     at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:351)
     at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:213)
     at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:200)
     at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
     at java.net.Socket.connect(Socket.java:529)
     at java.net.Socket.connect(Socket.java:478)
     at java.net.Socket.(Socket.java:375)
     at java.net.Socket.(Socket.java:189)
     at sun.rmi.transport.proxy.RMIDirectSocketFactory.createSocket(RMIDirectSocketFactory.java:22)
     at sun.rmi.transport.proxy.RMIMasterSocketFactory.createSocket(RMIMasterSocketFactory.java:128)
     at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:595)
     ... 17 more
     at oracle.kv.impl.admin.AdminServiceFaultHandler.getThrowException(AdminServiceFaultHandler.java:84)
     at oracle.kv.impl.fault.ProcessFaultHandler.rethrow(ProcessFaultHandler.java:205)
     at oracle.kv.impl.fault.ProcessFaultHandler.execute(ProcessFaultHandler.java:144)
     at oracle.kv.impl.admin.CommandServiceImpl.executePlan(CommandServiceImpl.java:234)
     at oracle.kv.impl.admin.CommandServiceAPI.executePlan(CommandServiceAPI.java:162)
     at oracle.kv.impl.admin.webapp.server.AdminUIServiceImpl.createPlan(AdminUIServiceImpl.java:554)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:597)
     at com.google.gwt.user.server.rpc.RPC.invokeAndEncodeResponse(RPC.java:569)
     at com.google.gwt.user.server.rpc.RemoteServiceServlet.processCall(RemoteServiceServlet.java:208)
     at com.google.gwt.user.server.rpc.RemoteServiceServlet.processPost(RemoteServiceServlet.java:248)
     at com.google.gwt.user.server.rpc.AbstractRemoteServiceServlet.doPost(AbstractRemoteServiceServlet.java:62)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
     at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:538)
     at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:476)
     at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:119)
     at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:517)
     at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:225)
     at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:934)
     at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:404)
     at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:183)
     at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:869)
     at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:117)
     at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:114)
     at org.eclipse.jetty.server.Server.handle(Server.java:341)
     at org.eclipse.jetty.server.HttpConnection.handleRequest(HttpConnection.java:589)
     at org.eclipse.jetty.server.HttpConnection$RequestHandler.content(HttpConnection.java:1065)
     at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:823)
     at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:220)
     at org.eclipse.jetty.server.HttpConnection.handle(HttpConnection.java:411)
     at org.eclipse.jetty.io.nio.SelectChannelEndPoint.handle(SelectChannelEndPoint.java:515)
     at org.eclipse.jetty.io.nio.SelectChannelEndPoint$1.run(SelectChannelEndPoint.java:40)
     at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:529)
     at java.lang.Thread.run(Thread.java:662)
(from Plans.PlanCallback)

920601 wrote:
Thanks, Charles. I use network host name or network host IP address instead of localhost and it well resolved my former problem. I can deploy the remote SN. But there is a new problem when I deploy the store. It looks like that these Replication Node at different SN can not communicate with each other, because of mis-match IP address format.
Note that the node "community01/10.193.128.223" is the first deployed node who holds the administration process, "mi-desktop/127.0.1.1:5011" is another node. I don't understand why the second node uses its loopback adress. Can you help me to find out the solution?
Here is the original error log.
"mi-desktop/127.0.1.1:5011 the address associated with this node, is a loopback address. It conflicts with an existing use, by a different node of the address:community01/10.193.128.223:5011 which is not a loopback address. Such mixing of addresses within a group is not allowed, since the nodes will not be able to communicate with each other."I'm not sure I have any good advice, but I would check your /etc/hosts to see if mi-desktop maps to the loopback address (127.0.0.1). If it does, then you need to use a name that does not map to the loopback.
Charles Lamb

Options for deployment via Remote Desktop Services / Terminal Server

Currently we have volume licenses for CS which is deployed via remote desktop services in a multi-server load balanced farm.
When reaching out to support, they informed me that CC cannot be deployed via RDS/terminal services.
Seeing that CS is discontinued, how does Adobe suggest deployment of their apps via RDS/Terminal services?
The support rep really didn't have an answer for me.
I find it hard to believe that Adobe's going to abandon deployment of their apps in the enterprise as things are moving towards thin clients rather than traditional desktops.
We'd like to avoid needing to go VDI instead of RDS if possible.
I'd imagine VDI would have the same licensing issues assuming you don't want to have a dedicated VM for each user rather than having a shared pool of VMs.
Thank You.

The only link I have is http://forums.adobe.com/community/download_install_setup/creative_suite_enterprise_deploym ent
Otherwise, Adobe contact information - http://helpx.adobe.com/contact.html since this forum is about the "regular" Cloud

Basic NAC deployment question

Hi,
Am I right in assuming that at a minimum, a NAC deployment must consist of 2 appliances - one server and one manager? or is the manager an application that can run on a Windows server? can the manager run on the same appliance as the server?
My second question regards Cisco Trust Agent and Clean Access Agent. Has CTA effectively been succeeded by CAA? from what I can see, CTA was part of the old NAC framework before they started using appliances.
Many Thanks in advance,
Dom

Both manager and server can run on two PCs or Cisco appliances, which are actually HP ProLiant DL140 G3 or HP ProLiant DL360 G5 PCs ;) You'll need two devices in any case.
As to second question - nobody knows what will happen with the whole technology in the future. Will it be completely replaced by MS NAP? Will the NAC Framework be canceled? Both Cisco solutions are not perfect. What customers actually need is to have all the NAC appliance features to run directly on Cisco switches and routers. No Clean Access Server will be needed in this case, only Manager! And OOB mode which is difficult to configure, support and troubleshoot will gone away. NAC framework is run directly on Cisco devices, but it is not as feature-reach as NAC Appliance.

Interesting! JDeveloper deploy to remote server uses HTTP POST

The documentation clearly mentions that the bpelc ant task only deploys to local server using a file copy. I was wondering how JDeveloper is able to deploy to remote servers. Turns out is just does a HTTP POST of multipart/form-data to upload the BPEL suitcase jar file. Given below is the trace of the POST. Of course, it is all proprietary for now and is not documented. Maybe Oracle can wrap this as a custom ant task?
--Nizam
POST /integration/services/deploy/deployProcess.jsp HTTP/1.1
Host: bpel.server.com:9700
Connection: Keep-Alive, TE
TE: trailers, deflate, gzip, compress
User-Agent: RPT-HTTPClient/0.3-3
BPELDomain: default
BPELPassword: bpel
Accept-Language: en
Accept-Encoding: gzip, x-gzip, compress, x-compress
Content-type: multipart/form-data;boundary=*****
Content-length: 10690
Content-Disposition: form-data; name="upload";BPELDomain="default"; filename="E:\work\MyBPELWS\HelloWorld\output\bpel_HelloWorld_1.0.jar"
PK..
........3................META-INF/....PK..
........3...#............META-INF/MANIFEST.MFManifest-Version: 1.0
Process-GUID: MD5{9d2c0a4b850da042548cc6bdf1c04d68}
Created-By: 1.4.2_06 (Sun Microsystems Inc.)
Process-Id: HelloWorld
Timestamp: 1124360790893
Process-Class: BPEL
Implementation-Package: bpel.p0
Revision-Tag: 1.0
PK..
........3................BPEL-INF/PK..
........3.\.Z............bpel.xml<?xml version="1.0" encoding="UTF-8"?>
<BPELSuitcase guid="MD5{9d2c0a4b850da042548cc6bdf1c04d68}" timestamp="1124360790893" revision="1.0">
<BPELProcess process-impl="bpel.p0.BPEL_BIN" src="HelloWorld.bpel" id="HelloWorld">
<partnerLinkBindings>
<partnerLinkBinding name="client">
<property name="wsdlLocation">HelloWorld.wsdl</property>
</partnerLinkBinding>
</partnerLinkBindings>
</BPELProcess>
</BPELSuitcase>
PK..
........3[...5...5.......build.xml<?xml version="1.0" ?>

<project name="HelloWorld" default="main" basedir=".">

<property name="deploy" value="default" />

<property name="rev" value="1.0" />
<target name="main">

<bpelc input="${basedir}/bpel.xml" rev="${rev}" deploy="${deploy}" />
</target>
</project>PK..
........3,.JaZ...Z.......graphics.xml<?xml version = '1.0' encoding = 'UTF-8'?>
<graphics>
<partnerlink_locations>
<partnerlink name="client" x="15" y="215" side="left"/>
</partnerlink_locations>
<diagram popupeditor="false" centerzoom="true" validateonload="true" confirmbeforedelete="true" SELECTED_PARTNERLINK_COLOR="0,0,153" SWIMLANE_BACKGROUND="255,255,225" SWIMLANE_DIVIDER_BACKGROUND="236,233,216" GRAPH_BACKGROUND="255,255,255" SELECTED_BORDER_BACKGROUND="204,255,204" CONNECTED_PARTNERLINK_COLOR="204,204,255" CONNECTABLE_PARTNERLINK_COLOR="0,0,255" UNCONNECTED_PARTNERLINK_COLOR="192,192,192"/>
</graphics>
PK..
........3O ..............HelloService.wsdl<definitions
targetNamespace="http://tempuri.org/"
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:bpws="http://schemas.xmlsoap.org/ws/2003/03/business-process/"
xmlns:s0="http://tempuri.org/"
xmlns:plnk="http://schemas.xmlsoap.org/ws/2003/05/partner-link/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
>
<import namespace="http://tempuri.org/" location="http://localhost/HelloEnglish/Service1.asmx?WSDL"/>
<plnk:partnerLinkType name="Service1Soap_PL">
<plnk:role name="Service1Soap_Role">
<plnk:portType name="s0:Service1Soap"/>
</plnk:role>
</plnk:partnerLinkType>
</definitions>
PK..
........3.....
......HelloWorld.bpel
<process name="HelloWorld" targetNamespace="http://xmlns.oracle.com/HelloWorld" xmlns="http://schemas.xmlsoap.org/ws/2003/03/business-process/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:bpws="http://schemas.xmlsoap.org/ws/2003/03/business-process/" xmlns:xp20="http://www.oracle.com/XSL/Transform/java/oracle.tip.pc.services.functions.Xpath20" xmlns:ldap="http://schemas.oracle.com/xpath/extension/ldap" xmlns:bpelx="http://schemas.oracle.com/bpel/extension" xmlns:client="http://xmlns.oracle.com/HelloWorld" xmlns:ora="http://schemas.oracle.com/xpath/extension" xmlns:orcl="http://www.oracle.com/XSL/Transform/java/oracle.tip.pc.services.functions.ExtFunc">
<partnerLinks>
<partnerLink name="client" partnerLinkType="client:HelloWorld" myRole="HelloWorldProvider"/>
</partnerLinks>
<variables>
<variable name="inputVariable" messageType="client:HelloWorldRequestMessage"/>
<variable name="outputVariable" messageType="client:HelloWorldResponseMessage"/>
</variables>
<sequence name="main">
<receive name="receiveInput" partnerLink="client" portType="client:HelloWorld" operation="process" variable="inputVariable" createInstance="yes"/>
<assign name="Assign_1">
<copy>
<from expression="concat("v1.1: Hello ", bpws:getVariableData('inputVariable','payload','/client:HelloWorldProcessRequest/client:input'))"/>
<to variable="outputVariable" part="payload" query="/client:HelloWorldProcessResponse/client:result"/>
</copy>
</assign>
<reply name="replyOutput" partnerLink="client" portType="client:HelloWorld" operation="process" variable="outputVariable"/>
</sequence>
</process>PK..
........3.....
......HelloWorld.wsdl<?xml version="1.0" encoding="UTF-8"?>
<definitions name="HelloWorld"
targetNamespace="http://xmlns.oracle.com/HelloWorld"
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:client="http://xmlns.oracle.com/HelloWorld"
xmlns:plnk="http://schemas.xmlsoap.org/ws/2003/05/partner-link/">
.
.<types>
..<schema attributeFormDefault="qualified"
...elementFormDefault="qualified"
...targetNamespace="http://xmlns.oracle.com/HelloWorld"
...xmlns="http://www.w3.org/2001/XMLSchema">
...<element name="HelloWorldProcessRequest">
....<complexType>
.....<sequence>
......<element name="input" type="string"/>
.....</sequence>
....</complexType>
...</element>
...<element name="HelloWorldProcessResponse">
....<complexType>
.....<sequence>
......<element name="result" type="string"/>
.....</sequence>
....</complexType>
...</element>
..</schema>
.</types>
.
.<message name="HelloWorldRequestMessage">
..<part name="payload" element="client:HelloWorldProcessRequest"/>
.</message>
.<message name="HelloWorldResponseMessage">
..<part name="payload" element="client:HelloWorldProcessResponse"/>
.</message>
.
.
.<portType name="HelloWorld">
..<operation name="process">
...<input message="client:HelloWorldRequestMessage" />
...<output message="client:HelloWorldResponseMessage"/>
..</operation>
.</portType>
.
.<plnk:partnerLinkType name="HelloWorld">
..<plnk:role name="HelloWorldProvider">
...<plnk:portType name="client:HelloWorld"/>
..</plnk:role>
.</plnk:partnerLinkType>
</definitions>
PK..
........3..............................META-INF/....PK..
........3...#......................+...META-INF/MANIFEST.MFPK..
........3..........................T...BPEL-INF/PK..
........3.\.Z......................{...bpel.xmlPK..
........3[...5...5.................i...build.xmlPK..
........3,.JaZ...Z.....................graphics.xmlPK..
........3O ........................I...HelloService.wsdlPK..
........3.....
....................HelloWorld.bpelPK..
........3.....
....................HelloWorld.wsdlPK...............&....
*****

If anyone is interested, I've created a custom ant taks to leverage this HTTP post for deploying the BPEL suitcase jar to remote servers. We didn't want to use FTP, as we'd have to change permissions on the files.
To do this, I've leveraged the oracle.tip.pc.infra.deploy.DeployRemote class. You just have to pass it the path the the jar, server url (http://host:port/deploy/deployProcess.jsp), domain, and password.
This seems to work fine for us.
-Mike

PRI to BRI connection between h.o and remote branch

Dear all,
in my H.O i have a 2801 with VWIC2-1MFT E1/T1 and i have an E1 leased connection which is 2.048Mb, and at the branch side
i have 1841 and ISDN BRI card and my ISDN BRI connection is ready at remote branch
i need to connect between these 2 offices, can anybody give a sample configuration, i will be connecting 10 remote offices in future.
i will rate all the posts.
regards
BInoy

hi james,
thank you for your reply.
i have couple of doubts.as i have explained in my first post, i have a leased line which is E1 and for sure i can channelize it. suppose site 1 using BRI so the site 1 router need to dial into my H.Q correct me if i'm wrong?
as it is a leased line at H.Q i will not be getting seperate no's for PRI channels. i'm really confused it will be great if you can provie your views.

[Forum FAQ] How to deploy applications remotely

In some situations, we may need some ways to install applications remotely, here we summarize four general ways to deploy applications.
1. Using PowerShell to install
We can use the Win32_Product class to install Windows Installer packages, remotely or locally, so in this way, we can use powerShell command to invoke this function. For example, to install the NewPackage.msi package located in the network
share \\AppServ\remote on the remote computer PC01, type the following command at the Windows PowerShell prompt:
(Get-WMIObject -ComputerName PC01 -List | Where-Object -FilterScript {$_.Name -eq "Win32_Product"}).Install(\\AppSrv\remote\NewPackage.msi)
In same method, we can use the following command to deploy .exe application:
(Get-WMIObject -ComputerName PC01 -List | Where-Object -FilterScript {$_.Name -eq "Win32_Process"}).Create(\\AppSrv\remote\NewPackage.exe)
Note: The applications should use Windows Installer technology.
2. PsExec tool: one of sysinternals utilities
PsExec's most powerful uses include launching interactive command-prompts on remote systems and remote-enabling tools like IpConfig that otherwise do not have the ability to show information about remote systems. So, we can use this feature to install our
applications, in fact this is similar with PowerShell methods, the only difference is that PsExec is a comprehensive tool. Similarly, we can use the following command to achieve our goal:
psexec \\PC01 cmd /c "\\AppSrv\remote\NewPackage.msi" /quiet /norestart
Note: we can also use PsExec tool to install Microsoft Update file (.msu)
psexec \\PC01 -s -h -d wusa.exe "\\AppSrv\remote\NewPackage.msu" /quiet /norestart
3. Group Policy Software Installation
In domain environment, this method is very useful to deploy our software. It only supports MSI package for deployment.
We can choose assign a program to user or computer. If you assign the program to a user, it is installed when the user logs on to the computer. When the user first runs the program, the installation is completed. If you assign the program to a computer,
it is installed when the computer starts, and it is available to all users who log on to the computer. When a user first runs the program, the installation is completed.
You can get the installation information of group policy software installation in event viewer, including success or failure.
4. System Center Configuration Manger
The Microsoft System Center Configuration Manager software distribution feature provides a set of tools and resources that help you create and manage packages and advertisements used to distribute software to client resources within your enterprise. This
is a comprehensive suit for deployment.
How to Deploy Applications in Configuration Manager
http://technet.microsoft.com/en-us/library/gg682082.aspx
Summary:
There are a lot of methods for software deployment, here just introduce some generic ways.
Here is another important point of software deployment: Some applications do not use windows installer technology.
Applications that do not use Windows Installer technology may have application-specific methods for automated deployment. For example, a .exe file may be just a wrapper, it can be anything. To determine whether there is a method for deployment automation,
check the documentation for the application or consult the application vendor's support system. In some cases, even if the application vendor did not specifically design the application for installation automation, the installer software manufacturer may have
some techniques for automation.
Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

In some situations, we may need some ways to install applications remotely, here we summarize four general ways to deploy applications.
1. Using PowerShell to install
We can use the Win32_Product class to install Windows Installer packages, remotely or locally, so in this way, we can use powerShell command to invoke this function. For example, to install the NewPackage.msi package located in the network
share \\AppServ\remote on the remote computer PC01, type the following command at the Windows PowerShell prompt:
(Get-WMIObject -ComputerName PC01 -List | Where-Object -FilterScript {$_.Name -eq "Win32_Product"}).Install(\\AppSrv\remote\NewPackage.msi)
In same method, we can use the following command to deploy .exe application:
(Get-WMIObject -ComputerName PC01 -List | Where-Object -FilterScript {$_.Name -eq "Win32_Process"}).Create(\\AppSrv\remote\NewPackage.exe)
Note: The applications should use Windows Installer technology.
2. PsExec tool: one of sysinternals utilities
PsExec's most powerful uses include launching interactive command-prompts on remote systems and remote-enabling tools like IpConfig that otherwise do not have the ability to show information about remote systems. So, we can use this feature to install our
applications, in fact this is similar with PowerShell methods, the only difference is that PsExec is a comprehensive tool. Similarly, we can use the following command to achieve our goal:
psexec \\PC01 cmd /c "\\AppSrv\remote\NewPackage.msi" /quiet /norestart
Note: we can also use PsExec tool to install Microsoft Update file (.msu)
psexec \\PC01 -s -h -d wusa.exe "\\AppSrv\remote\NewPackage.msu" /quiet /norestart
3. Group Policy Software Installation
In domain environment, this method is very useful to deploy our software. It only supports MSI package for deployment.
We can choose assign a program to user or computer. If you assign the program to a user, it is installed when the user logs on to the computer. When the user first runs the program, the installation is completed. If you assign the program to a computer,
it is installed when the computer starts, and it is available to all users who log on to the computer. When a user first runs the program, the installation is completed.
You can get the installation information of group policy software installation in event viewer, including success or failure.
4. System Center Configuration Manger
The Microsoft System Center Configuration Manager software distribution feature provides a set of tools and resources that help you create and manage packages and advertisements used to distribute software to client resources within your enterprise. This
is a comprehensive suit for deployment.
How to Deploy Applications in Configuration Manager
http://technet.microsoft.com/en-us/library/gg682082.aspx
Summary:
There are a lot of methods for software deployment, here just introduce some generic ways.
Here is another important point of software deployment: Some applications do not use windows installer technology.
Applications that do not use Windows Installer technology may have application-specific methods for automated deployment. For example, a .exe file may be just a wrapper, it can be anything. To determine whether there is a method for deployment automation,
check the documentation for the application or consult the application vendor's support system. In some cases, even if the application vendor did not specifically design the application for installation automation, the installer software manufacturer may have
some techniques for automation.
Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

Application not working after deployment in remote server

I have a standard web application working in my localhost. But when I deploy the same in a remote server it gives the following exception. This happens for all the jsp:useBean. why is the container not able to fund the Beans. The Tomcat is installed properly and I use it's manager tool to deploy the WAR.
I checked the WEB-INF/lib directory and it has all the required JARs.
Error:
org.apache.jasper.JasperException: Exception in JSP: /test/CurWeatherBean.jsp:22
19:         <a href="index.jsp">[ index ]</a>
20:
21:         <h2>CurrentWeatherMapBean.ATOMICS</h2>
22:         <jsp:useBean id="cwmDAO" class="com.news.pub.weather.CurWeatherBean$ATOMICS" scope="request"/>
23:         <ul>
24:             <li>
25:                 <h3>List<CurWeatherBean> get()</h3>
Stacktrace:
     org.apache.jasper.servlet.JspServletWrapper.handleJspException(JspServletWrapper.java:506)
     org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:395)
     org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314)
     org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264)
     javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
root cause
java.lang.NullPointerException
     com.news.pubt.forc.oc.Container.getReference(Container.java:68)
     com.news.pubt.forc.cfg.PropertyBag.getBag(PropertyBag.java:80)
     com.news.pubt.forc.cfg.PropertyBag.getProperty(PropertyBag.java:60)
     com.news.pubt.atomicsbeans.impl.ATOMICSBean.<init>(ATOMICSBean.java:61)
     com.news.pubt.atomicsbeans.ATOMICSAwareBean.<init>(ATOMICSAwareBean.java:175)
     com.news.pubt.weather.CurWeatherBean$ATOMICS.<init>(CurWeatherBean.java:131)
     org.apache.jsp.test.CurWeatherBean_jsp._jspService(CurWeatherBean_jsp.java:65)
     org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97)
     javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
     org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:334)
     org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314)
     org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264)
     javax.servlet.http.HttpServlet.service(HttpServlet.java:802)Please help me.
Edited by: danbrown on Feb 8, 2008 8:32 AM

Your error stack refers to a class with the package sequence "com.news.pubt.weather....." but your jsp file refers to a class "com.news.pub.weather...
Is there an error in your jsp page? If so, did you change the package name, and do you still have old class files on the classpath on your local machine with the old name?
Anyway, the top of the error stack refers to line number 68 in the Container class. So that is where you should see a problem regarding the NullPointerExcpetion. You could post that line of code.

Error while deploying to remote server

Hi,
I'm trying to deploy an application from Java Studio Creator2 (running in my home office) to a Java System Applicatio Server PE 8.2 (running in our company). The server is behind a NAT router an has a private IP address on the company LAN (10.0.0.0 network). The ports 4848, 8080 and 8181 are open and directed to the server and I can connect using a web browser.
I can also register the server in JSC2 as a remote deployment server and that little green arrow shows up imediately (I can see/change settings, ...). If I start to deploy an application to this server it fails. JSC2 and the server start talking to each other but after a few minutes I get a timeout error. This is the output in the JSC console:
Building jar: /export/home/tim/Documents/source/Creator/Projects/Test/dist/Test.war
Deleting directory /export/home/tim/Documents/source/Creator/Projects/Test/dist/tmp
dist:
run-deploy:
Distributing /export/home/tim/Documents/source/Creator/Projects/Test/dist/Test.war to [ni000g02:4848_server]
Start registering the project's server resources
Finished registering server resources
Deployment error: Deployment timed out after 240 seconds.. See the server log file for details.
Exception=Deployment error: Deployment timed out after 240 seconds.. See the server log file for details.
Deployment error: Deployment timed out after 240 seconds.. See the server log file for details.
The Application is on the server but it's disabled and theres no automatic test (starting the browser, calling the page). This only works once. After I removed the crippled app from the server, I can't redeploy it.
Maybe the problem is the server being behind a NAT router?
Any help is appreciated!
Tim Richter

Hi,
I did a fresh install (plain vanilla) and tried to deploy again. Here's the complete log:
[#|2006-05-01T10:41:52.958+0200|INFO|sun-appserver-pe8.2|javax.enterprise.tools.launcher|_ThreadID=10;|
/usr/java/bin/java
-client
-Xmx512m
-XX:NewRatio=2
-Dcom.sun.aas.defaultLogFile=/opt/SUNWappserver/domains/domain1/logs/server.log
-Djava.endorsed.dirs=/opt/SUNWappserver/lib/endorsed
-Djava.security.policy=/opt/SUNWappserver/domains/domain1/config/server.policy
-Djava.security.auth.login.config=/opt/SUNWappserver/domains/domain1/config/login.conf
-Dsun.rmi.dgc.server.gcInterval=3600000
-Dsun.rmi.dgc.client.gcInterval=3600000
-Djavax.net.ssl.keyStore=/opt/SUNWappserver/domains/domain1/config/keystore.jks
-Djavax.net.ssl.trustStore=/opt/SUNWappserver/domains/domain1/config/cacerts.jks
-Djava.ext.dirs=/usr/java/jre/lib/ext:/opt/SUNWappserver/domains/domain1/lib/ext:/opt/SUNWappserver/derby/lib
-Djdbc.drivers=org.apache.derby.jdbc.ClientDriver
-Djavax.management.builder.initial=com.sun.enterprise.admin.server.core.jmx.AppServerMBeanServerBuilder
-Dcom.sun.enterprise.config.config_environment_factory_class=com.sun.enterprise.config.serverbeans.AppserverConfigEnvironmentFactory
-Dcom.sun.enterprise.taglibs=appserv-jstl.jar,jsf-impl.jar
-Dcom.sun.enterprise.taglisteners=jsf-impl.jar
-Djavax.xml.parsers.SAXParserFactory=com.sun.org.apache.xerces.internal.jaxp.SAXParserFactoryImpl
-Dcom.sun.aas.configName=server-config
-Dorg.xml.sax.parser=org.xml.sax.helpers.XMLReaderAdapter
-Ddomain.name=domain1
-Djmx.invoke.getters=true
-Djavax.xml.parsers.DocumentBuilderFactory=com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderFactoryImpl
-Dcom.sun.aas.promptForIdentity=true
-Dorg.xml.sax.driver=com.sun.org.apache.xerces.internal.parsers.SAXParser
-Dcom.sun.aas.instanceRoot=/opt/SUNWappserver/domains/domain1
-Djavax.xml.transform.TransformerFactory=com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl
-Dcom.sun.aas.domainName=domain1
-Djava.util.logging.manager=com.sun.enterprise.server.logging.ServerLogManager
-Dproduct.name=Sun-Java-System/Application-Server
-Dcom.sun.enterprise.overrideablejavaxpackages=javax.faces,javax.servlet.jsp.jstl,javax.xml.bind,javax.help
-Dcom.sun.aas.configRoot=/opt/SUNWappserver/config
-Djava.library.path=/usr/java/jre/lib/i386/client:/usr/jdk/instances/jdk1.5.0/jre/lib/i386/client:/usr/jdk/instances/jdk1.5.0/jre/lib/i386:/usr/jdk/instances/jdk1.5.0/jre/../lib/i386:/opt/SUNWappserver/lib:/usr/lib/lwp:/opt/SUNWappserver/lib:/usr/lib/lwp:/usr/jdk/instances/jdk1.5.0/jre/lib/i386/client:/usr/jdk/instances/jdk1.5.0/jre/lib/i386:/usr/jdk/instances/jdk1.5.0/jre/../lib/i386:/opt/SUNWappserver/lib:/opt/SUNWappserver/lib:/opt/SUNWappserver/lib::/usr/lib
-Dcom.sun.aas.instanceName=server
-Dcom.sun.aas.processLauncher=SE
-cp
/usr/java/lib/tools.jar:/opt/SUNWappserver/lib/appserv-rt.jar:/opt/SUNWappserver/lib/j2ee.jar:/opt/SUNWappserver/lib/activation.jar:/opt/SUNWappserver/lib/mail.jar:/opt/SUNWappserver/lib/appserv-cmp.jar:/opt/SUNWappserver/lib/admin-cli.jar:/opt/SUNWappserver/lib/appserv-admin.jar:/opt/SUNWappserver/lib/appserv-jstl.jar:/opt/SUNWappserver/lib/commons-launcher.jar:/opt/SUNWappserver/lib/commons-logging.jar:/opt/SUNWappserver/lib/j2ee-svc.jar:/opt/SUNWappserver/lib/jaxr-api.jar:/opt/SUNWappserver/lib/jaxr-impl.jar:/opt/SUNWappserver/lib/jaxrpc-api.jar:/opt/SUNWappserver/lib/jaxrpc-impl.jar:/opt/SUNWappserver/lib/dom.jar:/opt/SUNWappserver/lib/relaxngDatatype.jar:/opt/SUNWappserver/lib/jax-qname.jar:/opt/SUNWappserver/lib/saaj-api.jar:/opt/SUNWappserver/lib/saaj-impl.jar:/opt/SUNWappserver/lib/xsdlib.jar:/opt/SUNWappserver/lib/jmxremote.jar:/opt/SUNWappserver/lib/jmxremote_optional.jar:/opt/SUNWappserver/lib/jsf-api.jar:/opt/SUNWappserver/lib/jsf-impl.jar:/opt/SUNWappserver/lib/rmissl.jar:/opt/SUNWappserver/lib/xalan.jar:/opt/SUNWappserver/lib/xercesImpl.jar:/opt/SUNWappserver/lib/appserv-assemblytool_zh_CN.jar:/opt/SUNWappserver/lib/appserv-cmp_zh_CN.jar:/opt/SUNWappserver/lib/appserv-rt_zh_CN.jar:/opt/SUNWappserver/lib/commons-launcher_zh_CN.jar:/opt/SUNWappserver/lib/deployhelp_zh_CN.jar:/opt/SUNWappserver/lib/j2ee_zh_CN.jar:/opt/SUNWappserver/lib/appserv-assemblytool_ja.jar:/opt/SUNWappserver/lib/appserv-cmp_ja.jar:/opt/SUNWappserver/lib/appserv-rt_ja.jar:/opt/SUNWappserver/lib/j2ee_ja.jar:/opt/SUNWappserver/lib/commons-launcher_ja.jar:/opt/SUNWappserver/lib/deployhelp_ja.jar:/opt/SUNWappserver/lib/j2ee_ko.jar:/opt/SUNWappserver/lib/appserv-assemblytool_ko.jar:/opt/SUNWappserver/lib/appserv-cmp_ko.jar:/opt/SUNWappserver/lib/appserv-rt_ko.jar:/opt/SUNWappserver/lib/commons-launcher_ko.jar:/opt/SUNWappserver/lib/deployhelp_ko.jar:/opt/SUNWappserver/lib/appserv-assemblytool_fr.jar:/opt/SUNWappserver/lib/appserv-cmp_fr.jar:/opt/SUNWappserver/lib/appserv-rt_fr.jar:/opt/SUNWappserver/lib/commons-launcher_fr.jar:/opt/SUNWappserver/lib/deployhelp_fr.jar:/opt/SUNWappserver/lib/j2ee_fr.jar:/opt/SUNWappserver/lib/appserv-assemblytool_es.jar:/opt/SUNWappserver/lib/appserv-cmp_es.jar:/opt/SUNWappserver/lib/appserv-rt_es.jar:/opt/SUNWappserver/lib/commons-launcher_es.jar:/opt/SUNWappserver/lib/deployhelp_es.jar:/opt/SUNWappserver/lib/j2ee_es.jar:/opt/SUNWappserver/lib/appserv-assemblytool_zh.jar:/opt/SUNWappserver/lib/appserv-cmp_zh.jar:/opt/SUNWappserver/lib/appserv-rt_zh.jar:/opt/SUNWappserver/lib/commons-launcher_zh.jar:/opt/SUNWappserver/lib/j2ee_zh.jar:/opt/SUNWappserver/lib/deployhelp_zh.jar:/opt/SUNWappserver/lib/appserv-upgrade.jar:/opt/SUNWappserver/lib/appserv-ext.jar:/opt/SUNWappserver/lib/install/applications/jmsra/imqjmsra.jar:/opt/SUNWappserver/imq/lib/jaxm-api.jar:/opt/SUNWappserver/imq/lib/fscontext.jar:/opt/SUNWappserver/lib/ant/lib/ant.jar
com.sun.enterprise.server.PEMain
start
display|#]
[#|2006-05-01T10:41:56.585+0200|INFO|sun-appserver-pe8.2|javax.enterprise.resource.jms|_ThreadID=10;|JMS5023: JMS service successfully started. Instance Name = imqbroker, Home = [/opt/SUNWappserver/imq/bin].|#]
[#|2006-05-01T10:41:56.588+0200|INFO|sun-appserver-pe8.2|javax.enterprise.system.core|_ThreadID=10;|CORE5098: AS Socket Service Initialization has been completed.|#]
[#|2006-05-01T10:41:57.161+0200|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0046:The Platform MBeanServer is available. It will be used to register Application Server MBeans. Platform MBeans will also be available for browsing while using standard JMX Console.|#]
[#|2006-05-01T10:41:57.166+0200|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0001:MBeanServer initialized successfully|#]
[#|2006-05-01T10:41:57.289+0200|INFO|sun-appserver-pe8.2|javax.enterprise.system.core.security|_ThreadID=10;|SEC1143: Loading policy provider com.sun.enterprise.security.provider.PolicyWrapper.|#]
[#|2006-05-01T10:41:57.800+0200|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|Created virtual server server|#]
[#|2006-05-01T10:41:57.805+0200|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|Created virtual server __asadmin|#]
[#|2006-05-01T10:41:58.418+0200|INFO|sun-appserver-pe8.2|javax.enterprise.resource.corba.ee.S1AS-ORB.rpc.transport|_ThreadID=10;|"IOP00710299: (INTERNAL) Successfully created IIOP listener on the specified host/port: all interfaces/3700"|#]
[#|2006-05-01T10:41:58.721+0200|INFO|sun-appserver-pe8.2|javax.enterprise.resource.corba.ee.S1AS-ORB.rpc.transport|_ThreadID=10;|"IOP00710299: (INTERNAL) Successfully created IIOP listener on the specified host/port: all interfaces/3820"|#]
[#|2006-05-01T10:41:58.724+0200|INFO|sun-appserver-pe8.2|javax.enterprise.resource.corba.ee.S1AS-ORB.rpc.transport|_ThreadID=10;|"IOP00710299: (INTERNAL) Successfully created IIOP listener on the specified host/port: all interfaces/3920"|#]
[#|2006-05-01T10:41:59.436+0200|INFO|sun-appserver-pe8.2|javax.enterprise.system.core.transaction|_ThreadID=10;|JTS5014: Recoverable JTS instance, serverId = [3700]|#]
[#|2006-05-01T10:42:03.014+0200|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1079: Initialization of AMX MBeans successful|#]
[#|2006-05-01T10:42:03.154+0200|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.deployment|_ThreadID=10;|[AutoDeploy] Selecting file /opt/SUNWappserver/lib/install/applications/MEjbApp.ear for autodeployment.|#]
[#|2006-05-01T10:42:03.671+0200|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.deployment|_ThreadID=10;|DPL5109: EJBC - START of EJBC for [MEjbApp]|#]
[#|2006-05-01T10:42:03.674+0200|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.deployment|_ThreadID=10;|Processing beans ...|#]
[#|2006-05-01T10:42:03.702+0200|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.deployment|_ThreadID=10;|DPL5110: EJBC - END of EJBC for [MEjbApp]|#]
[#|2006-05-01T10:42:03.809+0200|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.deployment|_ThreadID=10;|Total Deployment Time: 554 msec, Total EJB Compiler Module Time: 31 msec, Portion spent EJB Compiling: 5%
Breakdown of EJBC Module Time: Total Time for EJBC: 31 msec, CMP Generation: 0 msec (0%), Java Compilation: 0 msec (0%), RMI Compilation: 0 msec (0%), JAX-RPC Generation: 24 msec (77%),
|#]
[#|2006-05-01T10:42:03.880+0200|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.deployment|_ThreadID=10;|deployed with moduleid = MEjbApp|#]
[#|2006-05-01T10:42:03.993+0200|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1041:Sent the event to instance:[ApplicationDeployEvent -- reference-added MEjbApp]|#]
[#|2006-05-01T10:42:04.066+0200|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1042:Status of dynamic reconfiguration event processing:[success]|#]
[#|2006-05-01T10:42:04.084+0200|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1041:Sent the event to instance:[ApplicationDeployEvent -- deploy MEjbApp]|#]
[#|2006-05-01T10:42:04.213+0200|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.ejb|_ThreadID=10;|Instantiated container for: ejbName: MEJBBean; containerId: 75135249527799808|#]
[#|2006-05-01T10:42:04.314+0200|INFO|sun-appserver-pe8.2|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010: All ejb(s) of [MEjbApp] loaded successfully!|#]
[#|2006-05-01T10:42:04.316+0200|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1042:Status of dynamic reconfiguration event processing:[success]|#]
[#|2006-05-01T10:42:04.317+0200|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.deployment|_ThreadID=10;|[AutoDeploy] Successfully autodeployed : /opt/SUNWappserver/lib/install/applications/MEjbApp.ear.|#]
[#|2006-05-01T10:42:04.317+0200|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.deployment|_ThreadID=10;|[AutoDeploy] Selecting file /opt/SUNWappserver/lib/install/applications/__ejb_container_timer_app.ear for autodeployment.|#]
[#|2006-05-01T10:42:04.498+0200|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.deployment|_ThreadID=10;|DPL5109: EJBC - START of EJBC for [__ejb_container_timer_app]|#]
[#|2006-05-01T10:42:06.770+0200|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.deployment|_ThreadID=10;|Processing beans ...|#]
[#|2006-05-01T10:42:06.770+0200|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.deployment|_ThreadID=10;|DPL5110: EJBC - END of EJBC for [__ejb_container_timer_app]|#]
[#|2006-05-01T10:42:06.815+0200|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.deployment|_ThreadID=10;|Total Deployment Time: 2488 msec, Total EJB Compiler Module Time: 2272 msec, Portion spent EJB Compiling: 91%
Breakdown of EJBC Module Time: Total Time for EJBC: 2272 msec, CMP Generation: 649 msec (28%), Java Compilation: 1567 msec (68%), RMI Compilation: 0 msec (0%), JAX-RPC Generation: 0 msec (0%),
|#]
[#|2006-05-01T10:42:06.857+0200|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.deployment|_ThreadID=10;|deployed with moduleid = __ejb_container_timer_app|#]
[#|2006-05-01T10:42:06.908+0200|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1041:Sent the event to instance:[ApplicationDeployEvent -- reference-added __ejb_container_timer_app]|#]
[#|2006-05-01T10:42:07.028+0200|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1042:Status of dynamic reconfiguration event processing:[success]|#]
[#|2006-05-01T10:42:07.039+0200|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1041:Sent the event to instance:[ApplicationDeployEvent -- deploy __ejb_container_timer_app]|#]
[#|2006-05-01T10:42:07.133+0200|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.ejb|_ThreadID=10;|Instantiated container for: ejbName: TimerBean; containerId: 75135249728798720|#]
[#|2006-05-01T10:42:07.392+0200|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.ejb|_ThreadID=10;|EJB5109:EJB Timer Service started successfully for datasource [jdbc/__TimerPool]|#]
[#|2006-05-01T10:42:07.392+0200|INFO|sun-appserver-pe8.2|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010: All ejb(s) of [__ejb_container_timer_app] loaded successfully!|#]
[#|2006-05-01T10:42:07.393+0200|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1042:Status of dynamic reconfiguration event processing:[success]|#]
[#|2006-05-01T10:42:07.393+0200|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.deployment|_ThreadID=10;|[AutoDeploy] Successfully autodeployed : /opt/SUNWappserver/lib/install/applications/__ejb_container_timer_app.ear.|#]
[#|2006-05-01T10:42:07.398+0200|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0302: Starting Sun-Java-System/Application-Server.|#]
[#|2006-05-01T10:42:07.455+0200|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [__default-admingui] in virtual server [__asadmin] at []|#]
[#|2006-05-01T10:42:07.521+0200|WARNING|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0500: default-locale attribute of locale-charset-info element has been deprecated and is being ignored. Use default-charset attribute of parameter-encoding element instead|#]
[#|2006-05-01T10:42:07.611+0200|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [adminapp] in virtual server [__asadmin] at [web1]|#]
[#|2006-05-01T10:42:07.623+0200|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [admingui] in virtual server [__asadmin] at [asadmin]|#]
[#|2006-05-01T10:42:07.625+0200|WARNING|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0500: default-locale attribute of locale-charset-info element has been deprecated and is being ignored. Use default-charset attribute of parameter-encoding element instead|#]
[#|2006-05-01T10:42:07.636+0200|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [com_sun_web_ui] in virtual server [__asadmin] at [com_sun_web_ui]|#]
[#|2006-05-01T10:42:07.711+0200|INFO|sun-appserver-pe8.2|org.apache.catalina.core.StandardEngine|_ThreadID=10;|Starting Servlet Engine: Sun-Java-System/Application-Server|#]
[#|2006-05-01T10:42:09.084+0200|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|Initializing Grizzly Non-Blocking Mode|#]
[#|2006-05-01T10:42:09.085+0200|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0703: Initializing Sun-Java-System/Application-Server-PE HTTP/1.1 on 8080|#]
[#|2006-05-01T10:42:09.097+0200|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0712: Starting Sun-Java-System/Application-Server-PE HTTP/1.1 on 8080|#]
[#|2006-05-01T10:42:09.156+0200|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|Initializing Grizzly Blocking Mode|#]
[#|2006-05-01T10:42:09.157+0200|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0703: Initializing Sun-Java-System/Application-Server-PE HTTP/1.1 on 8181|#]
[#|2006-05-01T10:42:09.160+0200|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0712: Starting Sun-Java-System/Application-Server-PE HTTP/1.1 on 8181|#]
[#|2006-05-01T10:42:09.189+0200|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|Initializing Grizzly Non-Blocking Mode|#]
[#|2006-05-01T10:42:09.189+0200|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0703: Initializing Sun-Java-System/Application-Server-PE HTTP/1.1 on 4848|#]
[#|2006-05-01T10:42:09.195+0200|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0712: Starting Sun-Java-System/Application-Server-PE HTTP/1.1 on 4848|#]
[#|2006-05-01T10:42:09.332+0200|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1504: Here is the JMXServiceURL for the Standard JMXConnectorServer: [service:jmx:rmi:///jndi/rmi://ni000g02.kidogo.net:8686/jmxrmi]. This is where the remote administrative clients should connect using the standard JMX connectors|#]
[#|2006-05-01T10:42:09.333+0200|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1506: Status of Standard JMX Connector: Active = [true]|#]
[#|2006-05-01T10:42:09.363+0200|INFO|sun-appserver-pe8.2|javax.enterprise.system.core|_ThreadID=10;|Application server startup complete.|#]
[#|2006-05-01T10:50:57.639+0200|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.deployment|_ThreadID=11;|DPL5109: EJBC - START of EJBC for [Test]|#]
[#|2006-05-01T10:50:57.640+0200|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.deployment|_ThreadID=11;|Processing beans ...|#]
[#|2006-05-01T10:50:57.640+0200|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.deployment|_ThreadID=11;|DPL5110: EJBC - END of EJBC for [Test]|#]
[#|2006-05-01T10:50:57.681+0200|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.deployment|_ThreadID=11;|Total Deployment Time: 229 msec, Total EJB Compiler Module Time: 2 msec, Portion spent EJB Compiling: 0%
Breakdown of EJBC Module Time: Total Time for EJBC: 2 msec, CMP Generation: 0 msec (0%), Java Compilation: 0 msec (0%), RMI Compilation: 0 msec (0%), JAX-RPC Generation: 0 msec (0%),
|#]
[#|2006-05-01T10:50:57.723+0200|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.deployment|_ThreadID=11;|deployed with moduleid = Test|#]
[#|2006-05-01T10:50:58.419+0200|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.admin|_ThreadID=12;|ADM1041:Sent the event to instance:[ApplicationDeployEvent -- reference-added Test]|#]
[#|2006-05-01T10:50:58.451+0200|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.admin|_ThreadID=12;|ADM1042:Status of dynamic reconfiguration event processing:[success]|#]
[#|2006-05-01T10:50:58.674+0200|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.admin|_ThreadID=13;|ADM1041:Sent the event to instance:[ModuleDeployEvent -- deploy web/Test]|#]
[#|2006-05-01T10:50:58.687+0200|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.admin|_ThreadID=13;|ADM1042:Status of dynamic reconfiguration event processing:[success]|#]
Tim

Authentication throu controler 4402 from remote branch office

Hi
We have head office with 4402 controller and few 1130AG series access points. Clients PCs access to wifi network after authentication throu http site (service is woking on 4402 controler).
In other branch (connected to head office throu WAN-VPN) we have one 1130AG AP and we would like to use the same www authentication for clients. Is is possible ? How is the best way to do this ? Can we do this using differents LAN ip addressing for branch AP and clients ?
thanks in advance
James

The ideal solution would be to use the 4402 web-auth page and then route Internet traffic locally, instead of through the VPN. Unfortunatly I'm not aware of such a solution.
If you don't have the remote 1130 AP set to HREAP mode all traffic will be tunneled back to the WLC and clients will be forced to use the web-auth on the 4402.
If you are using HREAP, traffic would get routed locally and not forced to the 4402 page.
Depending on the remote users' traffic patterns and how secure you want authentication/encryption, it might be okay just to tunnel the traffic back. This is also dependant on a good WAN. If it goes down, no wireless access at remote side.

Can't access EJB deployed on remote OC4J - what am I doing wrong?

I'm unable to access an EJB deployed on a remote OC4J instance (ie, part of a 9iAS installation on another machine vs local in JDeveloper).
I've reverted to a stupid-simple EJB in hopes of getting it going prior to trying my actual code. The EJB works fine in JDev (9.0.3) - I 'run' the EJB to start the local OC4J instance, run my client code (generated via the "New Sample Java Client..." option in the Navigator context popup) and all is well.
I then create an EAR file via the the "Create EJB Jar Deployment Profile..." context popup of the ejb-jar.xml node, followed by "Deploy to EAR file" from the context popup of the resulting ejb1.deploy node. I next "Deploy EAR File" via the "Oracle Enterprise Manager" that comes with 9iAS (the :1810 port). After successfully deploying, I modify my client code in JDeveloper, specifying the new connection information for the remote machine via the Hashtable constructor of InitialContext and attempt to run it. I've tried a number of Context.PROVIDER_URL forms, including: ormi://registered_pingable_host_name:23791/deployed_application_name
ormi://registered_pingable_host_name:23791/session_deployment_name (from the <enterprise-beans><session-deployment name="xxx"/></enterprise-beans> section of my orion-ejb-jar.xml file, as per a tip in this forum)
I've tried prefixing ormi:// with http:, but get no response whatesoever in this case.
I've also tried it without the port number (this port number matches that in my remote OC4J's <oc4j_instance_home>/config/rmi.xml file).
On the Context.SECURITY_PRINCIPAL and Context.SECURITY_CREDENTIALS settings, I've tried various values, generally using the 'admin' user, with passwords taken from:
<oc4j_instance_home>/principals.xml
<oc4j_instance_home>/application-deployments/application_name/principals.xml
I've also tried matching the password in the jazn-data.xml, to no avail - this password appears encrypted anyway, but thought I'd give it a try on the off-chance that it was just a randomly-generated password - no go.
I've also tried SCOTT/TIGER, anonymous, etc. Incidentally, the 'deactivated' attribute of the <user> tag is set to "false" in my principals.xml files.
No matter what I do, I always get back "javax.naming.NamingException: Lookup error: java.net.ConnectException: Connection refused: connect"
Additionally, I get this same message when I try to establish an Application Server Connection via JDev.
Clearly, I'm missing something critical (and probably simple), but I can't for the life of me figure it out.
Any help would be much appreciated!
Thanks,
Jim Stoll

Ok, well this is a bit strange...
3103 - 3103 also fails, and some experimentation has led me to find that any time that I specify a range smaller than 6 (3101 - 3106 works, 3101 - 3105, 3101-3101, 3103-3103, etc does not), the OC4J instance will not restart. I get "An error occurred while starting. The opmn request has failed. From opmn: HTTP/1.1 204 No Content Content-Length: 0 Content-Type: text/html Response: 0 of 1 processes started. Check opmn log files such as ipm.log and ons.log for detailed." in the OEM window (I specify the RMI port range, hit Apply, go to the OC4J instance home page, see that the Status is 'Down', hit Start, and get that message.) <ORACLE_HOME>/product/iasinfra/opmn/logs/ipm.log tells me:
02/12/03 09:41:12 There is no rmi port left for starting an OC4J process. Please check oc4j's port property in OPMN's configuration file.
02/12/03 09:41:12 start_proc: UID 3719788: failed to build args
02/12/03 09:41:12 start_proc_req: failed to start a process in GID OC4JJim2, type: 2
If I bump it up to 3101 - 3106 or higher, it starts right up. Running opmnadmin debug, as suggested by Venky (thanks Venky!), yields:
PROCESS TABLE
UID PID FLAGS TYPE STATUS REF HTTP AJP RMI JMS
3654011 84 00000040 OC4J Alive 1 0 3005 3106 3206
424987 604 00000000 Apache Alive 1 7777 0 0 0
2932088 14849 00000000 OC4J Alive 1 0 3003 3103 3203
3063160 14878 00000000 OC4J Alive 1 0 3001 3101 3201
3194232 14906 00000000 OC4J Alive 1 0 3000 3105 3205
3325304 14936 00000000 OC4J Alive 1 0 3002 3102 3202
3456376 14964 00000000 OC4J Alive 1 0 3004 3104 3204
Which is what I would expect, given the specified range of 3101-3106. Trying each of these ports in turn, I've found that I can hit the EJB successfully on 3106, but 3101 - 3105 all fail with:
javax.naming.NamingException: Lookup error: javax.naming.AuthenticationException: No such domain/application: Project7_2; nested exception is:
     javax.naming.AuthenticationException: No such domain/application: Project7_2
     java.lang.Object com.evermind.server.rmi.RMIContext.lookup(java.lang.String)
          RMIContext.java:134
     java.lang.Object javax.naming.InitialContext.lookup(java.lang.String)
          InitialContext.java:350
     void Samplemypackage9.MySessionEJBClient1.main(java.lang.String[])
          MySessionEJBClient1.java:15
I'm a little concerned about assuming the high-end of the range to be the active port on a regular basis (though thus far, among about 20 - 30 tries spaced over 20 - 30 minutes, it has been...) - I guess I can have my code loop through the range until it finds a good port or exhausts the list, but that seems a bit excessive.
Can you think of a reason that my OC4J instance won't start with a range size of less than 6? I'm on 9iAS 9.0.2, if that makes any difference.
Thanks,
Jim

Images do not show when deployed on remote server

We are using jdeveloper 11.1.2.1, adf and integrated weblogic and remote server has weblogic where we deploy the application for testing.
We have a login.html page. when deployed and running the image in login.html does not show in FF or IE 8. It shows on IE9. when deployed on the remote server.
When deployed on the integrated server only fire fox shows the image. None of the other web browsers show the image in login,html
Here is my login.html
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>

<meta http-equiv="Content-Type" content="text/html;charset=UTF-8"/>
<title>Application Login</title>
</head>
<body>
<div class="header">
<div class="head_logo"><img src="images/imageLogo.JPG" alt="DASIS Logo" height="73" width="862"/></div>
</div>
<div class="navigation"></div>
<div class="content">
<div class="contentTitle">
Welcome to ISATS online.
<hr/>
</div>
<div class="contentArea">
<p class="Arial">To login, enter your user ID and password, then click the Login button.
</p>
<form method="POST" action="j_security_check">
<TABLE CELLPADDING="5"
SUMMARY="This table contains a web form
with fields for ID and password entry." >
<TBODY>
<TR>
<TD ALIGN="right" VALIGN="top">
<span class="Arial">User ID:</span>
</TD>
<TD VALIGN="top" ALIGN="left">
<input type="text" value="" alt="Enter User ID" name="j_username"></input>
</TD>
</TR>
<TR>
<TD ALIGN="right" VALIGN="top">
<span class="Arial">Password:</span>
</TD>
<TD VALIGN="top" ALIGN="left">
<input type="password" name="j_password" value="" alt="Password"></input>
</TD>
</TR>
<TR>
<TD ALIGN="right" VALIGN="top" width="85">
</TD>
<TD VALIGN="top" ALIGN="left">
<input type="submit" name="submit" value="Submit"></input>
</TD>
</TR>
</TBODY>
</TABLE>
</form>
<span class="Arial">
Please contact Help Desk for assistance with the User ID and Password.
<br>
The Help Desk number is XXX) XXX-2300.
</span>
</div>
</div>
</body>
</html>
Any help is appreciated
Edited by: user597294 on Jan 11, 2012 3:58 PM
Edited by: user597294 on Jan 11, 2012 4:01 PM

The problem does not seem to be with TopLink or JPA, so you may want to post this question to a different forum, such as the JDeveloper/ADF forum at:
JDeveloper and ADF
If the image itself is being sent but not loaded, you might check that it is a display issue with the browser being used.
Best Regards,
Chris

Weblogic no-stage mode deployment from remote machine

Context:
1. Build server is on machine A, where ant script builds the file and package ear
2. WLST deployment.py script is on build server (machine A).
3. weblogic admin server in machine B. The managed servers are on machine B and C.
4. ear file is copied to NFS shared drive mounted on server B and server C.
5. The deployment.py (which is on machine A) connects using WLST to Admin server of machine B to execute no-stage mode deployment
Question:
In above scenario it is observed that deployment fails and observed that though deployment.py is connected using WLST of remote admin server(machine B). the WSLT deployment command tries to validate .ear path on machine A. Is this constraint of the WLST? or Can the WLST deployment command can be invoked form script (in this scenario deployment.py) from build server (machine A) connection to admin server (machine b)?

Hi,
Make sure that you give App path in NFS shared location instead of the Machine A.
You build every thing was successful but when you place the app you need to specify application location. I hope you place app in the shared location.
Regards,
Kal

NAC deployment on Remote Branch

Similar Messages

Maybe you are looking for