A client requests Mpeg2 intra, 50Mb/s how do I make it?

All I have is the clients request. The Clip is currently ProRes 422.
I think it has something to do with I-Frames and GOP stuff, but don't know exactly what I need to do. I have no specifications for which container they want. I assume QT will be fine.
I don't think they want elements but a file that includes audio. I am not sure what they want to do with it and have no opportunity to ask.
Any Ideas?

Can't be sure without exact information because MPEG-2 is the basis for a ton of formats, some HD, some not. You might be able to make it with Compressor, or you might need something like Episode. It's possible they want an m2t file, which is a common format for satellite delivery.

Similar Messages

Client request

Hi All,
how clients requests process in weblogic servers ,how to find out the managed sever load is high .
Thanks in advance.
Balaji kumar

Hi,
If you have web servers in your environment then web server will forward this request to application server (WebLogic) , well it will need some configuration based on which web server you are using.
When client request hit the weblogic and will search for any specific object on application server a replica aware object will be provided to client it have list of the servers present in the cluster and which routing algorithm need to use.
To check which server have high load you can use weblogic admin console
AdminConsole --> server -->managed server--->monitoring tab

How can I have my servlet accept 100 concurrent client requests?

          My servlet extends HttpServlet so it is multithreaded. Then I have written a java
          client which starts 100 concurrent threads that try to contact the servlet.
          There are always lots of threads which are refused by the Weblogic Server 6.0.
          They get a 'Connection refused' exception. Sometimes there are 50 refused connections,
          sometimes there are 0 refused connections (not very often), sometimes there are
          80 refused connections (usually).
          I have checked the 'Servlet' documentation and the 'J2EE Design Considerations
          for Weblogic Server' which recommends not to exceede the execute thread count
          number of 15. I have not changed that value, I do not even know if it still exists
          in Weblogic 6.0 as the document refers to the 5.0 version.
          Does anybody know how to solve this problem? How can I have the client requests
          waiting rather than being refused? Of course the main goal is to serve all the
          client requests, not to refuse.
          This is the code that the client thread uses to contact the servlet:
          URL url = new URL("http://localhost:7001/examplesWebApp/myServlet");
          URLConnection conn = url.openConnection();
          conn.setDoInput(true);
          conn.setDoOutput(true);
          DataOutputStream os = new DataOutputStream(conn.getOutputStream());
          os.writeBytes()
          os.writeBytes()
          Thanks for your time,
          David


          The key is
          KKEY_LOCALMACHINE\SYSTEM\CurrentControlSet\Services\TCPIP\Parameters
          There you may need add a value "MaxUserPort" as REG_DWORD (5000 is default), also
          change "TcpTimedWaitDelay" to small number (30 is minimum). You may have trouble
          to find them. Just add them.
          You can also use Microsoft Web Application Stress Tool to test your Weblogic applications.
          As a free test tool, it is really powerful, although not so flexible.
          I guess you write your own test tool with java.net.URLConnection. I am not sure
          about the power of this class. In my case, I wrote my stress test tools with Java
          Socket. I can test application on Weblogic 6 with 1000 threads with my own tool
          and Microsoft tool, depending on memory and CPU of the machines I use. I run my
          tests on both Windows 2000 professional and Solaris.
          Check your CPU and memory usage with task manager.
          On the other hand, you should check log message on Weblogic 6. Try to turn on
          HTTP debug by add the following in your config.xml in tag <Server>.
          <ServerDebug DebugHttp="true" DebugURLResolution="true"
          JDBCConn="true" JDBCSQL="true" ListenThreadDebug="true" Name="myserver"/>
          "David Ruana" <[email protected]> wrote:
          >
          >Xiang, I really appreciate your help. I changed my Weblogic server configuration
          >from the console but I still experience the same problems.
          >
          >I start my 100 threads, and from about the 20th onward all them get the
          >'Connection
          >refused' exception in the URLConnection::getOutputStream() function,
          >always after
          >a successful URLConnection::openConnetion().
          >
          >My system is Windows 2000 Professional (Spanish version). I tried to
          >check the
          >open client socket descriptor limit but I was not able to find the TCPIP/MAXUSERPORT
          >in the registry. Do you know how is this entry called in Windows 2000?
          >
          >At this point I am not sure whether my problems are related to the Weblogic
          >server
          >or to the operative system. I will keep trying... I would appreciate
          >any other
          >suggestion.
          >
          >Thank you very much.
          >
          >
          >
          >"Xiang Rao" <[email protected]> wrote:
          >>
          >>It is better to use Weblogic 6 console to configure Weblogic server.
          >>In the console,
          >>there is tab Servers->myServer->Congiguration->Tuning, you can find
          >execute
          >>length
          >>and backlog.
          >>
          >>If you use Windows as test client, note Windows have a 5000 open client
          >>socket
          >>descriptors limit. You need change Windows Registry (TCPIP/MAXUSERPORT)
          >>to change
          >>this parameter.
          >>
          >>On the other hand, during test, you should monitor your test via Weblogic
          >>console
          >>(myServer->Monitoring->Performance), here you can see the change of
          >wait
          >>queue.
          >>If the queue keeps increaing, you are in trouble.
          >>
          >>Since you know how to use MBean, try to write customized (servlet, for
          >>example)
          >>to collect the following data: opened socket number, open socket number,
          >>opened
          >>session number and open session number. The two "open" numbers will
          >give
          >>you some
          >>clue. Also record your CPU and memory usage.
          >>
          >>BTW, what is the output you get from your test in terms of number of
          >>requests
          >>per second, response time and number of bytes downloaded/uplodaed per
          >>second?
          >>Are your test client and Weblogic running on the same machine?
          >>
          >>
          >>
          >>"David Ruana" <[email protected]> wrote:
          >>>
          >>>By the way, this is a piece of the config.xml file where you can see
          >>>my Server
          >>>configuration. It is the configuration which is installed in the examplesServer
          >>>in the free evaluation of Weblogic 6.0. I only modified the AcceptBacklog
          >>>value,
          >>>and added the ThreadPoolSize="15" line which was missing (I copied
          >from
          >>>the petstoreServer).
          >>>
          >>> <Server AcceptBacklog="1000" AdministrationPort="0" ClusterWeight="1"
          >>> ConsoleInputEnabled="false" DGCIdlePeriodsUntilTimeout="2"
          >>> DefaultProtocol="t3" DefaultSecureProtocol="t3s"
          >>> HttpdEnabled="true" JavaCompiler="C:\bea\jdk130/bin/javac"
          >>> ListenPort="7001" Name="examplesServer" NativeIOEnabled="true"
          >>>     ThreadPoolSize="15"
          >>> SocketReaderTimeoutMaxMillis="10"
          >>> TransactionLogFilePrefix="config/examples/logs/"
          >>> TunnelingClientPingSecs="45" TunnelingClientTimeoutSecs="40"
          >>>XMLRegistry="examplesXMLRegistry">
          >>> <ServerDebug Name="examplesServer"/>
          >>> <WebServer DefaultWebApp="DefaultWebApp_examplesServer"
          >>> LogFileName="./config/examples/logs/access.log"
          >>> LoggingEnabled="true" Name="examplesServer"/>
          >>> <Log FileName="./config/examples/logs/weblogic.log" Name="examplesServer"/>
          >>> <KernelDebug Name="examplesServer"/>
          >>> <SSL Enabled="true" ListenPort="7002" Name="examplesServer"
          >>> PeerValidationEnforced="0"
          >>> ServerCertificateChainFileName="./config/examples/ca.pem"
          >>> ServerCertificateFileName="./config/examples/democert.pem"
          >>> ServerKeyFileName="./config/examples/demokey.pem" TrustedCAFileName="./config/examples/ca.pem"/>
          >>> </Server>
          >>>
          >>>
          >>>
          >>>
          >>>
          >>>"Xiang Rao" <[email protected]> wrote:
          >>>>
          >>>>You only need to change Weblogic HTTP configuration. Give the server
          >>>>a big socket
          >>>>Backlog number. Since you test with 100 threads, you can think 1000
          >>>to
          >>>>5000, i.e.,
          >>>>1000 to 5000 requests will be in queue before got served. Aslo, you
          >>>might
          >>>>need
          >>>>to change your OS TCP/IP settings (both test clients and servers),
          >>such
          >>>>as maximum
          >>>>number of sockets and timeout value(so closed sockets will release
          >>socket
          >>>>descriptors
          >>>>immediately).
          >>>>
          >>>>On the other hand, the number of executive threads can be much larger
          >>>>than 15
          >>>>(50-200 is a normal number), depending on the features of your application.
          >>>>You
          >>>>can try your stress test tools to find a reasonable number by analyzing
          >>>>the relationships
          >>>>among (throughtput, response time, number of executive threads, etc).
          >>>>
          >>>>
          >>>>"David Ruana" <[email protected]> wrote:
          >>>>>
          >>>>>My servlet extends HttpServlet so it is multithreaded. Then I have
          >>>written
          >>>>>a java
          >>>>>client which starts 100 concurrent threads that try to contact the
          >>>servlet.
          >>>>>
          >>>>>There are always lots of threads which are refused by the Weblogic
          >>>Server
          >>>>>6.0.
          >>>>>They get a 'Connection refused' exception. Sometimes there are 50
          >>refused
          >>>>>connections,
          >>>>>sometimes there are 0 refused connections (not very often), sometimes
          >>>>>there are
          >>>>>80 refused connections (usually).
          >>>>>
          >>>>>I have checked the 'Servlet' documentation and the 'J2EE Design Considerations
          >>>>>for Weblogic Server' which recommends not to exceede the execute
          >thread
          >>>>>count
          >>>>>number of 15. I have not changed that value, I do not even know if
          >>>it
          >>>>>still exists
          >>>>>in Weblogic 6.0 as the document refers to the 5.0 version.
          >>>>>
          >>>>>Does anybody know how to solve this problem? How can I have the client
          >>>>>requests
          >>>>>waiting rather than being refused? Of course the main goal is to
          >serve
          >>>>>all the
          >>>>>client requests, not to refuse.
          >>>>>
          >>>>>This is the code that the client thread uses to contact the servlet:
          >>>>>
          >>>>>URL url = new URL("http://localhost:7001/examplesWebApp/myServlet");
          >>>>>URLConnection conn = url.openConnection();
          >>>>>conn.setDoInput(true);
          >>>>>conn.setDoOutput(true);
          >>>>>
          >>>>>DataOutputStream os = new DataOutputStream(conn.getOutputStream());
          >>>>>os.writeBytes()
          >>>>>os.writeBytes()
          >>>>>...
          >>>>>
          >>>>>Thanks for your time,
          >>>>>David
          >>>>>
          >>>>
          >>>
          >>
          >

Jpd client request with attachments

I'm currently attempting to wrap a custom control in a jpd file for the added benefits
of a Java process. The problem I'm encountering is due to the fact that the control
I'm using takes file content as input (I'm currently using the DataHandler type,
since this is how attachments are transferred to/from the client using jws files).
I've set the process up so that the client request has an argument of type javax.activation.DataHandler.
When working with jws files, this was sufficient allow the service to accept
a SOAP attachment. When I try to set this up through a process, however, I get
the following error: "java.lang.ClassCastException: javax.activation.DataHandler".
This error occurred when I invoked the process as a web service via the BEA-generated
client proxy jar.
Is there a different way of utilizing SOAP attachments with jpd files, or am I
simply missing another step?
Thanks.
-Brian

What are different jar files in your classpath. You might be missing the standard
jar file that contains the javax.activation.DataHandler class. Please check and
apply a proper Jar file.
"Brian McLoughlin" <[email protected]> wrote:
>
I'm currently attempting to wrap a custom control in a jpd file for the
added benefits
of a Java process. The problem I'm encountering is due to the fact that
the control
I'm using takes file content as input (I'm currently using the DataHandler
type,
since this is how attachments are transferred to/from the client using
jws files).
I've set the process up so that the client request has an argument of
type javax.activation.DataHandler.
When working with jws files, this was sufficient allow the service to
accept
a SOAP attachment. When I try to set this up through a process, however,
I get
the following error: "java.lang.ClassCastException: javax.activation.DataHandler".
This error occurred when I invoked the process as a web service via
the BEA-generated
client proxy jar.
Is there a different way of utilizing SOAP attachments with jpd files,
or am I
simply missing another step?
Thanks.
-Brian

Jpd client requests with attachments

I'm currently attempting to wrap a custom control in a jpd file for the added benefits
of a Java process. The problem I'm encountering is due to the fact that the control
I'm using takes file content as input (I'm currently using the DataHandler type,
since this is how attachments are transferred to/from the client using jws files).
I've set the process up so that the client request has an argument of type javax.activation.DataHandler.
When working with jws files, this was sufficient allow the service to accept
a SOAP attachment. When I try to set this up through a process, however, I get
the following error: "java.lang.ClassCastException: javax.activation.DataHandler".
This error occurred when I invoked the process as a web service via the BEA-generated
client proxy jar.
Is there a different way of utilizing SOAP attachments with jpd files, or am I
simply missing another step?
Thanks.
-Brian

Hi Brian,
This sounds like a known bug. Could you take this issue up with our
award winning support team [1] and reference CR129731.
Thanks,
Bruce
[1]
http://support.bea.com
[email protected]
Brian McLoughlin wrote:
>
I'm currently attempting to wrap a custom control in a jpd file for the added benefits
of a Java process. The problem I'm encountering is due to the fact that the control
I'm using takes file content as input (I'm currently using the DataHandler type,
since this is how attachments are transferred to/from the client using jws files).
I've set the process up so that the client request has an argument of type javax.activation.DataHandler.
When working with jws files, this was sufficient allow the service to accept
a SOAP attachment. When I try to set this up through a process, however, I get
the following error: "java.lang.ClassCastException: javax.activation.DataHandler".
This error occurred when I invoked the process as a web service via the BEA-generated
client proxy jar.
Is there a different way of utilizing SOAP attachments with jpd files, or am I
simply missing another step?
Thanks.
-Brian

What is client in SAP???how to explain as a technical Consultant??

What is client in SAP???how to explain as a technical Consultant??
this is the question asked by SAP labs,India.
Can anyone giv me a proper Answer
Thanks in Advance.

Hi,
Normally we have 3 clients in our real time scenario.Development,Quality and production client.Each client has different client numbers like 100 ,200, 300. First we develop our applications in development client.We will assign this to a package like ZDE. at this time a request will be assigned .then we will release this from se01 or se10. then we need to import themin quality client. In quality client we have the data which is closed to Production system.Here we will perform all the testing .If any changes we want to do then once again we will do in dev client and transport it to quality.If everything is ok.Then we will transport this to Production client where key users will use our applications.
Hope u understand.
Regds,
Vinsa.R

Controllers not re-directing client requests to ISE

Please find attached a simple BYOD/ISE document I uploaded to kick start my new Wireless setup. Its all configured on my ISE sever and Controller as per doc.
My setup:
3600 AP's
Internal 5508 Controller
DMZ 5508 Controller (acts as a DHCP server for wireless clients)
Controllers have established connectivity (mobility acnhors), as a client I can connect fine to my new SSID get a DHCP IP address back from DMZ WLC and at the moment can connect out to the Internet fine (using no WLAN Security as a test). So this part is working.
I have now followed the document configured ISE, enabled AAA on the Internal WLC only and used the AAA override setting on WLAN as in the attached document.
I connect to SSID expecting to be redirected to my ISE Guest Portal, nothing happens other than connecting to Internet WebPages.
My question is, if I have followed this document correctly why is the Internal WLC not redirecting client requests to ISE, is this because my mobility anchors need to be re-configured, perhaps the AAA/ISE config needs to be applied to my DMZ WLC not internal WLC?
I would prefer the Internal WLC to redirect the login to ISE, doesn't make sense to traverse through the DMZ Firewall onto DMZ WLC back into the Internal Network again to the ISE to authenticate.
Or am I missing something additionally to this document to make sure clients are directed to the ISE Guest portal login.

After you configure web authentication, if the feature does not work as       expected, complete these troubleshooting steps:
Check if the client gets an IP address. If not, users can uncheck             DHCP Required on the WLAN and give the wireless client a             static IP address. This assumes association with the access point. Refer to the             IP addressing issues section of Troubleshooting             Client Issues in the Cisco Unified Wireless Network for troubleshooting DHCP             related issues.
On WLC versions earlier than 3.2.150.10, you must manually enter             https://1.1.1.1/login.html in order to navigate to the web             authentication window.
The next step in the process is DNS resolution of the URL in the             web browser. When a WLAN client connects to a WLAN configured for web             authentication, the client obtains an IP address from the DHCP server. The user             opens a web browser and enters a website address. The client then performs the             DNS resolution to obtain the IP address of the website. Now, when the client             tries to reach the website, the WLC intercepts the HTTP Get session of the             client and redirects the user to the web authentication login page.
Therefore, ensure that the client is able to perform DNS resolution             for the redirection to work. On Windows, choose Start >             Run, enter CMD in order to open a command window, and             do a “nslookup www.cisco.com" and see if the IP address comes back.
On Macs/Linux: open a terminal window and do a “nslookup             www.cisco.com" and see if the IP address comes back.
If you believe the client is not getting DNS resolution, you can             either:
Enter either the IP address of the URL (for example,                 http://www.cisco.com is http://198.133.219.25)
Try to directly reach the controller's webauth page with                 https:///login.html. Typically this is                 http://1.1.1.1/login.html.
Does entering this URL bring up the web page? If yes, it is most             likely a DNS problem. It might also be a certificate problem. The controller,             by default, uses a self-signed certificate and most web browsers warn against             using them.
For web authentication using customized web page, ensure that the             HTML code for the customized web page is appropriate.
You can download a sample Web Authentication script from             Cisco Software             Downloads. For example, for the 4400 controllers, choose             Products > Wireless > Wireless LAN Controller > Standalone             Controllers > Cisco 4400 Series Wireless LAN Controllers > Cisco 4404             Wireless LAN Controller > Software on Chassis > Wireless Lan Controller             Web Authentication Bundle-1.0.1 and download the             webauth_bundle.zip file.
These parameters are added to the URL when the user's Internet             browser is redirected to the customized login page:
ap_mac—The MAC address of the access point to which the wireless                 user is associated.
switch_url—The URL of the controller to which the user                 credentials should be posted.
redirect—The URL to which the user is redirected after                 authentication is successful.
statusCode—The status code returned from the controller's web                 authentication server.
wlan—The WLAN SSID to which the wireless user is                 associated.
These are the available status codes:
Status Code 1: "You are already logged in. No further action is                 required on your part."
Status Code 2: "You are not configured to authenticate against                 web portal. No further action is required on your part."
Status Code 3: "The username specified cannot be used at this                 time. Perhaps the username is already logged into the                 system?"
Status Code 4: "You have been excluded."
Status Code 5: "The User Name and Password combination you have                 entered is invalid. Please try again."
All the files and pictures that need to appear on the Customized             web page should be bundled into a .tar file before uploading to the WLC. Ensure             that one of the files included in the tar bundle is login.html. You receive             this error message if you do not include the login.html             file:
Refer to the             Guidelines             for Customized Web Authentication section of             Wireless             LAN Controller Web Authentication Configuration Example for more             information on how to create a customized web authentication window.
Note: Files that are large and files that have long names will result                 in an extraction error. It is recommended that pictures are in .jpg                 format.
Internet Explorer 6.0 SP1 or later is the browser recommended for             the use of web authentication. Other browsers may or may not             work.
Ensure that the Scripting option is not blocked on             the client browser as the customized web page on the WLC is basically an HTML             script. On IE 6.0, this is disabled by default for security purposes.
Note: The Pop Up blocker needs to be disabled on the browser if you                 have configured any Pop Up messages for the user.
Note: If you browse to an https site, redirection does                 not work. Refer to Cisco bug ID                 CSCar04580 (registered customers only)          for more information.
If you have a host name configured for the             virtual interface of the WLC, make sure that the DNS             resolution is available for the host name of the virtual interface.
Note: Navigate to the Controller > Interfaces menu                 from the WLC GUI in order to assign a DNS hostname to the                 virtual interface.
Sometimes the firewall installed on the client computer blocks the             web authentication login page. Disable the firewall before you try to access             the login page. The firewall can be enabled again once the web authentication             is completed.
Topology/solution firewall can be placed between the client and             web-auth server, which depends on the network. As for each network             design/solution implemented, the end user should make sure these ports are             allowed on the network firewall.
Protocol Port
HTTP/HTTPS Traffic
TCP port 80/443
CAPWAP Data/Control Traffic
UDP port 5247/5246
LWAPP Data/Control Traffic (before rel 5.0)
UDP port 12222/12223
EOIP packets
IP protocol 97
Mobility
UDP port 16666 (non secured)                       UDP port 16667 (secured IPSEC tunnel)
For web authentication to occur, the client should first associate             to the appropriate WLAN on the WLC. Navigate to the Monitor >             Clients menu on the WLC GUI in order to see if the client is             associated to the WLC. Check if the client has a valid IP             address.
Disable the Proxy Settings on the client browser until web             authentication is completed.
The default web authentication method is PAP. Ensure that PAP             authentication is allowed on the RADIUS server for this to work. In order to             check the status of client authentication, check the debugs and log messages             from the RADIUS server. You can use the debug aaa             all command on the WLC to view the debugs from the RADIUS             server.
Update the hardware driver on the computer to the latest code from             manufacturer's website.
Verify settings in the supplicant (program on             laptop).
When you use the Windows Zero Config supplicant built into             Windows:
Verify user has latest patches installed.
Run debugs on supplicant.
On the client, turn on the EAPOL (WPA+WPA2) and RASTLS logs from a             command window, Start > Run > CMD:
netsh ras set tracing eapol enable
      netsh ras set tracing rastls enable
In order to disable the logs, run the same command but replace             enable with disable. For XP, all logs will be located in             C:\Windows\tracing.
If you still have no login web page, collect and analyze this             output from a single client:
debug client
debug dhcp message enable
debug aaa all enable
debug dot1x aaa enable
debug mobility handoff enable
If the issue is not resolved after you complete these steps,             collect these debugs and use the             TAC Service Request Tool (registered customers only)          in order to open a Service             Request.
debug pm ssh-appgw enable
debug pm ssh-tcp enable
debug pm rules enable
debug emweb server enable
debug pm ssh-engine enable packet

Cannot perform client request

Hi all,
i'm using OWSM for build a request soap in ws-security mode.
Executing the request, i have this response:
"<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"><SOAP-ENV:Body><SOAP-ENV:Fault><faultcode xmlns:p="http://schemas.oblix.com/ws/2003/08/Faults">p:Client.UndeliverableFault</faultcode><faultstring>Cannot perform client request</faultstring><detail/></SOAP-ENV:Fault></SOAP-ENV:Body></SOAP-ENV:Envelope>"
Any help how to resolve p:Client.UndeliverableFault issue
Thanks

Hi,
i resolved the problem!! In practice, i was wrong to set url of the endpoint In the Configure Messenger Step for New Service page.
Now, as response, i have:
<?xml version="1.0" encoding="UTF-8"?>
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"><env:Header/><env:Body><env:Fault xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"><faultcode xmlns:jboss-wsse="http://www.jboss.com/jbossws/ws-security">jboss-wsse:InternalError</faultcode><faultstring>An internal WS-Security error occurred. See log for details</faultstring></env:Fault></env:Body></env:Envelope>
how i can resolve the problem?
Thanks
The message is build in this mode:
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns="#######################################">
<soap:Header>
<wsse:Security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" xmlns="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" soap:mustUnderstand="1">
<wsse:BinarySecurityToken xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" ValueType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509v3" EncodingType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#Base64Binary" wsu:Id="#######################################">
</wsse:BinarySecurityToken>
<dsig:Signature xmlns="http://www.w3.org/2000/09/xmldsig#" xmlns:dsig="http://www.w3.org/2000/09/xmldsig#">
<dsig:SignedInfo>
<dsig:CanonicalizationMethod Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"/>
<dsig:SignatureMethod Algorithm="http://www.w3.org/2000/09/xmldsig#rsa-sha1"/>
<dsig:Reference URI="#######################################">
<dsig:Transforms>
<dsig:Transform Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"/>
</dsig:Transforms>
<dsig:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"/>
<dsig:DigestValue>#######################################</dsig:DigestValue>
</dsig:Reference>
<dsig:Reference URI="#######################################">
<dsig:Transforms>
<dsig:Transform Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"/>
</dsig:Transforms>
<dsig:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"/>
<dsig:DigestValue>#######################################</dsig:DigestValue>
</dsig:Reference>
</dsig:SignedInfo>
<dsig:SignatureValue>
</dsig:SignatureValue>
<dsig:KeyInfo>
<wsse:SecurityTokenReference xmlns="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="#######################################">
<wsse:Reference URI="#######################################"/>
</wsse:SecurityTokenReference>
</dsig:KeyInfo>
</dsig:Signature>
<wsu:Timestamp xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" xmlns="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="#######################################">
<wsu:Created>2012-06-27T08:45:33Z</wsu:Created>
</wsu:Timestamp>
</wsse:Security>
</soap:Header>
<soap:Body xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="#######################################">
<ns:hello>
<arg0>string</arg0>
</ns:hello>
</soap:Body>
</soap:Envelope>
There are some difference.
How i can modify the build of soap message??
Thanks
Edited by: Eremita383 on 27-giu-2012 1.52

Client Request/Response Context

I'm new to Weblogic Integration and have a question regarding client response action.
I've seen an example of a quick workflow where the webpage calls the process
and gets a response back. In essence the workflow is synchronous.
Now I want to include a long running process, using Worklists and involving many
different actors. During the worklist task acceptance I want to get some feedback
from the user. My questions is what context does the Client Request/Response
execute in. The example in the docs shows the worklist application. Is this
absolutely required? How about a client response to a portlet.
Thanks,
noah

One of the Certification mandates logging the remote client IP AND PORT for each log-event.
I cannot pass these from GUI client because the user may
be on a private network. This calls for capturing the IP and PORT at GUI server end.
Capturing remote IP is simple as SOAP library exposes the request object from which the IP can be obtained.
The dificult part is to capture port. I addressed this problem by introducing a
new Tomcat Service Engine, CSMServiceEngine. This engine has access to the underneath socket using which
i obtain the client port and pass it across to SOAP layer as a x-csm-client-port HTTP theader.
I have a custom SOAP provider, CSMSoapSPI, which obtains the port using the above x-header and the
client IP from its request object. THese are done only for 'login' task and hence i published a new
SOAP service: LoginCommand.
But bcoz of upgradation of tomcat from 4.0 to 5.0.28 the invoke method in the StandardEngine(which was initially extended by class i posted) is made final with JDK 1.5 and i can no longer use the StandardEngine. Hence i tried with the Valve class.But with no luck.
Hope this answers ur question

Howto prepare RMI objects before clients request

Hi, here is what I intend to do on the server side.
Server Roles:
- provide authentication.
- have a queue of data ready to deliver to clients requests. (to build this queue the server must get information from the DB, do some filtering and priority)
- Keep record of logged clients (this will affect the queue as well)
- on clients responses (do some processing and insert data to DB
my worries are how should I prepare this queue before clients start requesting. Here is my approach
Use some flag mechanism to prevent delivery until objects are ready.
Execute an application (queue controller) on same rmi server (or other) that actually prepares this queue objects, once prepared set flags ready for delivery.
The queue controller would need to act as a daemon or service and keep an eye on the queue, acting on it if necessary.
How does this sound?
any suggestions
Thanks

Don't export the server until the queue is ready. Don't extend UnicastRemoteObject: instead, call UnicastRemoteObject.exportObject(remote, port) after you have made the queue ready for service.

Arrowpoint Cookies, Reverse Proxy and Multiplexed Client Requests

Hi,
I have a reverse proxy which is performing SSL offload and making backend connections to two web servers. Between the reverse proxy and the two webservers, a CSS is in place to load balance between the web servers. There is a requirement for session stickiness on the web servers and since client IP details are lost through the reverse proxy I have used the arrowpoint-cookie method to load balance connections.
However, the reverse proxy seems to make only a handful of connections to the servers compared to the number incoming client connections and we have noticed that stickiness is broken. Now, I would assume this is correct if arrowpoint-cookie makes a load balancing based on the first HTTP get in a tcp stream and not on a per transaction basis AND our reverse proxy is multiplexing client requests. However, I can not convince myself of how the arrowpoint-cookie method actually works.
I wondered if anyone had any insight on this or had experienced similar issues with arrowpoint cookies?

Hi Gilles,
I have implemented this today, and we are still seeing issues with requests hitting the wrong server.
A bit more info, the reverse proxy is an AXG Web Aopplication Firewall. I have been looking at this and am considering disabling connection re-use on here.
However I am also wondering if this might be to do with the flow timeout multiplier I am using which is 5 (80 seconds). Perhaps this is too low?
Thanks, David.

What is the format for a Client Request JMS message.

I am trying to send directly to the JMS queue to start a WLI process. From the Workshop browser, the message is received. However, when sending my own JMS message, WebLogic complains with an "Unexpected message format" onMessageException.
What is the correct format for a WLI Client Request node? A text message? Please help. Thanks - Frank.

Kai,
Thanks for the info. I have created a MB channel and a JMS event generator. But now it seems that my problem has simply been moved further out. Case in point: If I send a simple XML text message to the JMS event queue, the WebLogic JPD throws a MBConnectorException ("Could not determine channel type").
So I am wondering if this is still not the best practice to accomplish what I want. Should I be using a MDB which then simply calls a JCX control that knows how to talk to the WLI start node? The whole idea is that I want to start the workflow with a simple JMS message.
Thanks in advance,
Frank

Parallel nodes can't enclose in client request Nodes

Hi,
I have a parallel node in my JPD.
I want to add a clientRequest-Response node which will take a input xml and will return an response xml. But having a parallel node its not allwoing to have a single clientrequest-response node. It works only if I add 2 saperate ( 1 client request node and 1 client response node( calkback).
But when I try to call the clientrequest node from my webservice it has a return type as void. but i need it to be responsedocument?
How can we solve this problem?
<b>ERROR: MyProcess.jpd:84: 'parallel' nodes cannot be enclosed within 'clientRequest' nodes.
ERROR: 1 error(s), 0 warning(s).</b>

This question has been moved to
<pre> weblogic.developer.interest.integration group
http://forums.bea.com/bea/thread.jspa?threadID=600010081&tstart=0
</pre>

How can I make a server differ between two or more clients?

How can I make a server differ between two or more clients?
The clients can connect and talk to the server fine, but how can I make the server talk to one, two or all clients? i.e. what would be a good way to implement this?
Currently, the server listens for connections like this:
while (listening) {
try {
new ServerThread(this, serverSocket.accept()).start();
I guess one way would be to add the ServerThreads to a Hashtable with the client ID as key, and then get the ServerThread with the proper client ID, but this seems unnecessary complicated. Any ideas?

Complicated was perhaps the wrong word, I should have
written something like it doesn't "feel" right. Or is
this a common and good way to solve communication
between a server and multiple clients?Thats pretty much how I do it. I normally use an array or ArrayList of Sockets instead of HashTable, with [0] being the first player etc.... Then you can communicate with exactly who you want. If you want to send bytes to all of them, just send the same thing to each socket individually (or is there a better way to do this?).

How can I make two copies of the same picture one with my watermark and one without for printing for clients?

how can I make two copies of the same picture one with my watermark and one without for printing for clients?

Export the photo twice, once with a watermark and once without a watermark.

A client requests Mpeg2 intra, 50Mb/s how do I make it?

Similar Messages

Maybe you are looking for