I am using JBOSS 7.1.1 for running my applications.
I have to configure proxy hosts to access my server. I tried setting up the changes in standalone.xml file
I added it as
<system-properties>
<property name="http.proxyHost" value="My proxy Host here"/>
<property name="http.proxyPort" value="My proxy Port here"/>
</system-properties>
But i added this while my server is running . I cant connect through the proxy still. the changes doesn't seems to be reflecting.
Does the server needs a restart for the changes to apply?
For any changes in standalone xml file to apply, we need to restart the server.
The changes got applied only after i made a restart.
Related
Create a new web application in VS2017
Right-click web application->Add->Container Orchestration support-> Service Fabric
Run (F5) locally (success), loads on http://machinename:<port in manifest>
Publish to Azure SF cluster + container registry
This URL should load http://<azurecluster>:<port in manifest>
But it is not loading.
The only thing that loads in the cluster is the Service Fabric Explorer, which shows the application running without error.
Am I doing anything wrong?
I think this has something to do with an incorrect port.
When adding a container ourselves through the template (as in the pic below), these are the options:
Host Port and container Port. Are these mapped correctly in
Container Orchestration support (step #2 above)?
In Host port help icon, it says the port might need to be opened on
load balancer. Do I need to do such things in my steps above?
Moreover, only the container port is provided in
config (applicationManifest.xml) in Step #2. So what about the host port?
How is the container port mapped to the application port?
Why didn't we have to do it locally (if this is the problem)?
The service specifies the container port in the manifest:
<Resources>
<Endpoints>
<Endpoint Name="Guest1TypeEndpoint" UriScheme="http" Port="8081" Protocol="http"/>
</Endpoints>
</Resources>
The application specifies the host port in the manifest:
<Policies>
<ContainerHostPolicies CodePackageRef="Code">
<PortBinding ContainerPort="80" EndpointRef="Guest1TypeEndpoint"/>
</ContainerHostPolicies>
</Policies>
In this example, container port 8081 is mapped to host port 80.
More info here.
You also need to configure an Azure Load Balancer rule and probe, to forward traffic (on port 80) into the cluster.
After that, you should see it work properly.
I am unable to setup SSL/TLS between wildfly 10 and Mysql. I have been trying to the following configurations for the datasource : .
<datasource jta="true" jndi-name="java:/jdbc/transit" pool-name="transit" enabled="true" use-ccm="true">
<connection-url>jdbc:mysql://myInstance.rds.amazonaws.com:3306/dbname?ssl=true</connection-url>
<driver-class>com.mysql.jdbc.Driver</driver-class>
<driver>mysql-connector-java-5.1.40.jar_com.mysql.jdbc.Driver_5_1</driver>
<security>
<user-name>example</user-name>
<password>secret</password>
</security>
<validation>
<valid-connection-checker class-name="org.jboss.jca.adapters.jdbc.extensions.mysql.MySQLValidConnectionChecker"/>
<background-validation>true</background-validation>
<exception-sorter class-name="org.jboss.jca.adapters.jdbc.extensions.mysql.MySQLExceptionSorter"/>
</validation>
</datasource>
The configuration of JDBC to use SSL is database vendor specific. The and tags of the datasource provide the needed flexibility to add the required JDBC configuration options to enable SSL database connections. Check with the database vendor what string or property can be added to connection URL or connection property and can configure it in datasource configuration at the JBoss end, this might require providing a truststore at the JBoss end to provide the trust on the database server. This can added in the following way :
JAVA_OPTS="$JAVA_OPTS -Djavax.net.ssl.trustStore=/path/to/db_cert.truststore
In domain mode the system property javax.net.ssl.trustStore needs to be set for the server which will be using the datasource .
The JBoss Administration and Configuration Guide discusses datasource configuration in chapter 13:
https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/configuration-guide/#datasource_management
For anyone looking for concrete implementation of the above steps, follow the steps:
make sure that MySql is build with support for secure connections (OpenSSL or yaSSL)
make sure that ssl is enabled (-ssl option in MySql)
the certificates are generated (mysql_ssl_rsa_setup)
import the MySQL server CA Certificate(for AWS RDS : you can download the certs from the AWS site, Link: https://s3.amazonaws.com/rds-downloads/rds-combined-ca-bundle.pem and https://s3.amazonaws.com/rds-downloads/rds-ca-2015-root.pem ) into a Java truststore or create a truststore in the current directory, and import the server's CA certificate
either
import the client certificate that matches the CA certificate you just imported, or create a new client certificate.
set the system properties.
For setting up the datasource in WildFly you may set the properties in the connection url like:
jdbc:mysql://${hostname}:3306/test?autoReconnect=true&useSSL=true&verifyServerCertificate=true&trustCertificateKeyStoreUrl=file:///${pathToYourTruststore}/truststore&trustCertificateKeyStorePassword=${yourPassword}&clientCertificateKeyStoreUrl=file:///${pathToYourKeystore}/keystore&clientCertificateKeyStorePassword=${yourPassword}&requireSSL=true
When I run Tomcat configuration I get the error below.
Unable to open service BOEX140Tomcat.
Here is the error I get when I run SAP Crystal Server management
Here are the installed components of Crystal Report Server:
I would like to know what other software and components I need to install or what configuration changes I need to make .
apache tomcat for bi 4 automatically stop it self
[enter image description here][3]
and changed the config file inside tomcat to below
the apacha bi for tomcat services automatically get stopped in Central Configuration manager.
From your first screenshot, it appears that IIS is active on port 8080. If Tomcat has been installed along with Crystal Reports server and you've used the default port settings during the installation, then Tomcat will be configured to use port 8080 as well.
Only one process can bind to a given port. So as port 8080 is taken by IIS, Tomcat will stop and exit with an error. You can probably find the error message in one of the log files (check the log subfolder in the Tomcat installation folder).
Here's what you can do. Either:
Change the port Tomcat is using (as described here).
Change the port IIS is using (as described here).
Stop the IIS service if you don't need it (as described here)..
I can not configure the proxy to download the dependencies:
Initially when I tried to build the project. received the message timeout. Now gotta find a configuration file that solved my problem in parts.
the file is net.properties which is inside the directory of the jdk, it is where I can specify the proxy server but can not get past the User and password for authentication.
any idea what to do?
You could try setting the following additional parameters in your net.properties file.
http.proxyUser=xxxxx
http.proxyPassword=xxxxx
Else, you can setup a local proxy server (with no authentication) which supports authentication to the proxy server you are using and point your net.properties to it.
Cheers.
I installed TeamCity and got it working against my project. However, I have since realized that I don't want it the administration page to be configured on port 80. I'm going to have other websites on that server that I want on the default port. How do I change the configured port?
I wandered around the configurations a bit and looked through the administration settings but couldn't figure it out.
The port number can be edited in the <TeamCity home>/conf/server.xml file, line <Connector port="8111" protocol="HTTP/1.1".
from Installing and Configuring the TeamCity server
To add to the answer provided by #sfussenegger you will also need to make sure that your build agents can still connect to the TeamCity server instance on the new port, or else your builds won't run.
To do this, you'll need to change the build agent configuration files to reflect the new serverUrl value. You can find this setting in the C:\TeamCity\buildAgent\conf\buildAgent.properties file.