The Proxy connection area in this page points to an example page which results in a 404.
https://docs.cloud.oracle.com/iaas/Content/API/SDKDocs/javasdk.htm
page resulting in 404
https://github.com/oracle/oci-java-sdk/blob/master/bmc-examples/src/main/java/HttpProxyExample.java
Basically, if I do not want to set a proxy on the JVM but want to use the following style of setting a proxy, is there a full example for this version? Is ProxyConfig supported in OCI java sdk and how do I use it?
ProxyConfig proxyConfig =
ProxyConfig.builder()
.host("proxy.mydomain.com")
.port("80")
.username("username")
.password("password")
.protocol(ProxyConfig.Protocol.HTTP)
.build();
The Apache Connector Provider add-on that is bundled with Oracle Cloud Infrastructure Java SDK 1.2.44 enables the option to specify an HTTP(S) proxy that is for a specific client and not a JVM setting.
For more information, please refer to the README.md hosted on GitHub
An example of configuring a proxy can also be found here.
Related
I am using the "C4 DSL Extension" of VSCode to show previews of my architecture diagrams. The previews are rendered through the WebviewPanel. The source code can be found here: https://gitlab.com/systemticks/c4-grammar/-/blob/master/extension/src/c4-structurizr-preview.ts
It works through a direct connection, but once connected with my corporate network, all requests have to pass through a proxy. VSCode itself handles proxies through the http_proxy and https_proxy variables. However, the WebviewPanel does not seem to take those settings.
The following figure shows an excerpt of the console. You can see, that the request to query the "structurizr-embed.js" failed.
Is this behavior intended? I could not find a setting in VSCode to enable WebviewPanel to request via proxy.
Note: I am using the Linux version of VSCode.
I found a solution by setting the http.proxy variable in VSCode. We are using authentication for proxies and previously I exported the http_proxy environment variable in the form of http_proxy=http://<username>:<password>#<host>:<port>.
However, VSCode expects this variable without credentials: http_proxy=http://<host>:<port>. Now I don't understand where it talks the credentials from, but it works.
I trying find file standalone.xml in remote access in openshift in wildfly 8 and wildfly 9 too, but not result.
I found page: http://blog.arungupta.me/wildfly-custom-standalone-configuartion-file-openshift/ where described where should find the location of the file, but it is not there.
my console files:
is there any ways, how use own configuration xml ?
Openshift Online allows you to override the default standalone.xml from your app by placing a file in your apps repository. The location is slightly different for v3 as it was for v2.
Overriding standalone.xml in Openshift Online v3
Place the file with your override in
/cfg/standalone.xml
Overriding standalone.xml in Openshift Online v2
Place the file with your override in
/.openshift/config/standalone.xml
Look for standalone.xml in %WILDFLY_HOME%\standalone\configuration. There you should find standalone.xlm and also standalone-full.xml and standalone-full-ha.xml (if you want to also drive your wildfly in different mode).
it's possible to setup a Open URL for MIME type support at (console.developer.google.com). That's create and works fine for my application. But only for the product instance at Google Cloud. In detail:
I've released my application in version 1. It's AppEngine base and it supports a Open URL myapp.appspot.com/oauth2callback. So after the release I will going on with feature development for version 2. I use the local AppEngine dev setup. So I take my second client ID and change the Open URL to my local workstation mydev.workstation.com:8080/oauth2callback. That works fine, but it breaks my product instance. Is there any workaround to use Open URL for the production instance and a second Open URL for my dev instance? In my opinion the Drive SDK settings should be:
enable Authentication Production:
Client ID: xxx
Additional Scopes:
Install URL:
Open URL: https://myapp.appspot.com/oauth2callback
enable Authentication Development:
Client ID: xxx
Additional Scopes:
Install URL:
Open URL: http://devworkstation.com:8080/oauth2callback
Jens
Create separate projects in the console for prod/qa/dev
The answer from #SteveBazyl is the preferred one for all the reasons stated. A kludgy alternative would be to have the servlet that is bound to the Open URL detect when it is dealing with a test scenario and do a 301 redirect to your dev server.
Also, the API URL is pretty consistent, so once you've sniffed it once, it's not to difficult to path the host and use it in a curl script or browser bookmark for local testing.
As an aside "oauth2callback" is a slightly odd name for your Drive Open URL. It's not wrong, but "driveopen" would show the separate concerns.
I have written a Chrome extension that uses the managed storage API to allow Google Apps administrators to configure its "options" via a policy name and value. When I install the extension I see a new section at chrome://policy for the extension and an indication that there are "No policies set."
I'm trying to figure out how to set this from the Google Apps management console. I have a Chrome management license and can install the extension, but I don't see any obvious place to define values for the extension's option as defined in its schema.json file.
I do see documentation at http://www.chromium.org/administrators/configuring-policy-for-extensions but I'm on a Chromebook and am assuming there is some way to specify this from admin.google.com for my domain.
Am I missing something obvious? Thanks.
We're still working on it :-) This is being tracked at https://code.google.com/p/chromium/issues/detail?id=361156 (sorry, only visible by project members for now) and we're targeting ChromeOS 37.
We're also interested in use cases you'd like to support via this API and the console. Please file bug reports or feature requests at crbug.com, using the Enterprise template.
This is now available in chromebox management console for managed devices under: Device Management -> Chrome App Management -> App Name, then "Upload configuration file".
Following process outlined here to create a axis service from a pojo:
Webinar: Building Applications with Carbon Studio for On-Premise and the Cloud.
I create the axis services as described in the webinar.
I did a mvn package sucessfully.
I start the WS02 ESB in eclipse sucessfully.
But when I deploy my app to the WS02 ESB, I see the following in the console:
INFO - ApplicationManager Deploying Carbon Application : MyCarbonApp-1.0.0.car...
WARN - ApplicationManager No artifacts found to be deployed in this server. Ignoring
Carbon Application : MyCarbonApp-1.0.0.car
and the service does not appear on the ESB console's web services list.
When I look at the file called MyAxisService.service I see the following:
#Contains the information about the axis2 service generation information from the eclipse workspace
#Fri May 25 15:53:09 NZST 2012
Class-name=com.unisys.comms.esbselection.MyAxisService
Type=FROM_CLASS
Service-name=MyAxisService
Projects=MyCarbonApp
What does this warning mean?
What can I do to further investigate the cause?
Is there some obvious step I've missed when creating the app?
Thanks in advance.
Please follow these steps to solve this issue.
Go to carbon.xml file locate in ....\wso2esb-4.9.0\repository\conf
Add new server role to xml elemet
EnterpriseServiceBus
ApplicationServer
Restart the server
This error means the Server Roles of the C-App Artifacts found in your Carbon Application Archive (CAR), does not match the Server Role of the ESB.
Reason is, Axis2 Web Services are by default has the Server Role of "ApplicationServer". Hence if you deploy it on the WSO2 AS, it will deploy without any problem. But in this case, you have tried to Deploy it the WSO2 ESB. Since the WSO2 ESB has the Server Role "EnterpriseServiceBus" and your Axis2 web service has the Server Role "ApplicationServer", they do not match each other. Result is the C-App deployer will ignore the C-App.
To solve this, you need to change the Server Role of your Axis2 Web Service. In order to do that, follow the steps below.
Go the C-App project you created and browse to the Axis2 Service Artifact folder in the "Artifacts" folder of the C-App.
Inside this Axis2 Service Project, you will see a file called "Artifact.xml". Open this file by double clicking on the file.
Once you double click on the file, file will be opened in the Artifact editor. Scroll the Editor down a bit.
There you will see a Drop Down next to a Label called "Server Role".
Select "EnterpriseServiceBus" option from the Drop down list and click on "Save All" button on the Eclipse Tool bar.
Go to the Servers view in Carbon Studio and click on the expand icon infront of the Carbon Server (WSO2 ESB in this case)
Once you expand the Server, you will be able to see the Server Module (C-App project) you deployed in the ESB.
Right Click on the C-App module under the ESB Server and Select "Redeploy".
Now you will see that Carbon Studio redeploy the C-App project and if you followed all the steps above correctly, your Axis2 Web Service will be deployed in the ESB.
Hope this helps!!
Thanks.
/Harshana