I trying to connect to em console through wlst. But I could connect only to weblogic admin console. I need to change some of the mediator properties(soa-infra which is a web application) through em console. Can anyone please help me in connecting to emconsole and thereby changing the mediator properties.
For this I executed oracle_home/oracle_common/common/bin/wlst.sh
Everything goes through the admin console, since that controls the entire domain and deployments/applications. The following links all have examples on how to edit soa-infra properties:
http://rreddy.blogspot.com/2012/03/wlst-soa-mbeans-examples.html
http://bibeksoa.blogspot.com/2013/10/wlst-script-soa-process-deployment.html
http://www.qualogy.com/wlst-change-script-to-soa-common-bpel-an-bpmn-properties/
http://go2kavinkumar.wordpress.com/2011/08/28/using-wlst-to-manage-web-service-policies/
Specifically you want to grab the Application=soa-infra object to use it.
Make sure that you have the EM console installed. It may not me installed in your domain by default (unless you checked it when creating your domain).
You can add the EM console by running config.sh from your domain and selecting Enterprise Manager console from the list. Then you should be able to access it via
http://admin_server_url:port/em
Related
I'm deploying an ear to one of my Weblogic servers with CustomRoles security model. From the console it's not a problem to define a new role and to assign it to a group.
However I'm trying to do this from the WLST console with no success. Is there a way to do this with WLST? The deployment/undeployment gives me no problem using the following commands
deploy('app','app.ear','server', securityModel='CustomRoles')
undeploy('app','server')
See the oracle docs
You want to do something like
serverConfig()
auth=cmo.getSecurityConfiguration().getDefaultRealm().lookupAuthenticationProvider("DefaultAuthenticator")
auth.createUser(login, password, login)
auth.addMemberToGroup(group, login)
I have made application ASP.NET C# and my connection string is as follows:
<add name="ASPNETDB" connectionString="Server=tcp:MYDATA.database.windows.net,1433;Database=MYDATA;User ID=MYDATA;Password=MYDATA;Trusted_Connection=False;Encrypt=True;Connection Timeout=30;" providerName="System.Data.SqlClient" />
Now it doesn't work at all, I mean I can't connect to my SQL server on Azure at all. When I want to login nothing happens, when I want to register nothing happens too. I get exception when I press to update DB, ie Publish->Settings-> Check box "Update database" Configure database updates . It seems to me that it doesn't work at all. The exception is of following type:
Error 22 Web deployment task failed. (Could not deploy package.
Unable to connect to target server.
Learn more at: http://go.microsoft.com/fwlink/?LinkId=221672#ERROR_EXECUTING_METHOD.) 0 0
What should I do? Please help?
I would recommend logging into the azure management portal and re downloading the publish profile for the application. If you are not working using a publish profile , then at least re download the connection string that is setup for the app and the DB. while in there check that the application (web site or VM) is up and running, and that the database it is connected to is also up and running.
I had to set firewall rule 0.0.0.0 to 255.255.255.255. Even though my firewall rule was set for my address, somehow it didn't register, because communication was relying to my website-DB and ip address of my website wasn't included there too. So I put rule as said before and now it works like a charm. :-)
I was deploy pentaho bi server on my running tomcat server ref from here.
Now I want to create JNDI bases datasource so I login through pentaho administration console but in that web page nothing to shows users lists, user role. After googling some times I was found that change console.xml then I was changed my console.xml file as below
<?xml version="1.0" encoding="UTF-8"?>
<console>
<solution-path>/home/pc-name/pentaho-solutions</solution-path>
<war-path>/home/pc-name/apache-tomcat-7.0.47/webapps/pentaho</war-path>
<platform-username>joe</platform-username>
<biserver-status-check-period-millis>30000</biserver-status-check-period-millis>
<homepage-url>http://www.pentaho.com/console_home</homepage-url>
<homepage-timeout-millis>15000</homepage-timeout-millis>
<!-- comma separated list of roles (no spaces) -->
<default-roles>Authenticated</default-roles>
<default-server-dir>biserver-ce</default-server-dir>
</console>
then I was stopped administration console and then again start but still it not shows me any user lists, role lists. After that I hard coded start-pac.sh as below
DIR_REL=`dirname $0`
cd $DIR_REL
DIR=`/home/pc-name/apache-tomcat-7.0.47`
cd -
. "$DIR/set-pentaho-env.sh"
setPentahoEnv "$DIR/../biserver-ce/jre"
but running at start-pac.sh it shows set-pentaho-env.sh not found but in my first steps deploying pentaho bi server on existing tomcat it not mentioned anything about set-pentaho-env.sh where to copy or set. Can any one knows how to solve this problem?
Short answer: Pentaho 5.0 doesn't have an admin console because both user roles and database connections are easily configured in the user console. It seems you just started to deploy your biserver so I suggest you upgrade to the new version and leave admin console behind. Trust me. You will like it.
Long answer: If you still wish to stay with 4.8 for some strange reason:
Don't change anything in Pac-start.bat, revert to the original version before your changes. If you need to change the default URL or port, then
find biserver-ce\tomcat\conf\server.xml
the default for pentaho user console is 8080, and the default admin console port is 8443. Change those to your preference. Once done,
find biserver-ce\tomcat\webapps\pentaho\WEB-INF\web.xml
change here:
<context-param>
<param-name>fully-qualified-server-url</param-name>
<param-value>http://localhost:8080/pentaho/</param-value>
</context-param>
then find the list of trusted Ip's and add additional trusted IP's here (this is somewhere around line 133)
<param-name>TrustedIpAddrs</param-name>
<param-value>127.0.0.1,0\:0\:0\:0\:0\:0\:0\:1(%.+)*$</param-value>
<description>Comma separated list of IP addresses of a trusted hosts.</description>
(Also covered in this article: http://wiki.pentaho.com/display/ServerDoc2x/Setting+up+trust+between+Administration+Console+and+BI+Server)
Make sure when you start the admin console, pentaho biserver is running already. Admin console will not work if the biserver is not running.
Make sure you use the correct JDK, because a wrong java configuration, or wrong java_home_path can also cause admin console to not stand up.
Really, just go with Pentaho 5.0.1.
We've been trying without much success to enable LDAP user authentication for the Worklight Application Center. We've carefully followed the instructions here:
http://pic.dhe.ibm.com/infocenter/wrklight/v5r0m5/index.jsp?topic=%2Fcom.ibm.help.doc%2Fwl_home.html
First, we created the LDAP repository in the WAS console and added it to the federated repositories config:
http://pic.dhe.ibm.com/infocenter/wrklight/v5r0m5/index.jsp?topic=%2Fcom.ibm.worklight.help.doc%2Fappcenter%2Fc_ac_was8_ldap.html
Then we configured the LDAP authentication for users and groups following:
http://pic.dhe.ibm.com/infocenter/wrklight/v5r0m5/index.jsp?topic=%2Fcom.ibm.help.doc%2Fwl_home.html
Finally we enabled ACL management with LDAP as suggested by:
http://pic.dhe.ibm.com/infocenter/wrklight/v5r0m5/index.jsp?topic=%2Fcom.ibm.help.doc%2Fwl_home.html
After the server restart these are the results:
Worklight Console: Works OK.
Application Center: Shows a ?????? in the user space with the following error in every screen related to users: FWLAC0401W: No user appears to be logged, check the Application Center security configuration.
Worklight WAS Console: We are locked out. The LDAP users do not work, the initial worklight/worklight user does not work. The only way to get in is changing the security.xml for the instance to get back in and rollback the security changes.
What are we doing wrong?
Is there a more "tutorial like" documentation to accomplish these tasks, we might be making some mistakes following the infocenter.
About the application center effect: Technically, the message means that the Web Security Context does not contain a principal (i.e. a user name). In general, Application Center must be configured so that the login screen appears (is this the case for you?).
I know two possible reasons:
Application Security is disabled in WAS. Open the WAS console and select Security > Global Security. Ensure that "Enable Application Security" is checked. Ensure also that "Enable Administrative Security" is checked.
The appcenteradmin role is mapped to special subject "Everyone". Both the appcenteradmin role and the appcenteruser role cannot be mapped to this special subject, because it simply disables the authentication and hence the security context does not know anymore which user is logged in. Look in Applications > Application Types > WebSphere Enterprise Applications > AppCenter > Security Role to user/group mapping. Here you can see how the roles are mapped and you can change it.
Since you also have a problem with the Worklight WAS console, I would guess that your situation is 1., since 2. is local to the Application center and does not affect the WAS console.
I am using SP 2010.
I created a new site collection from central admin.
and it gave me "site created successfully"
when I visit the new site collection, I get below error:
Cannot connect to the configuration database
What are my options?
Go to services (Start --> Run --> Type services.msc) and start the service SQL Server(SHAREPOINT)
Its probably the app pool you are running your site collection under, have you got any other site collections in the same web application?
If not take a look at the permissions on the app pool for that web app
This problem came to me after a password expired in the AD and had to be updated.
When i changed the password i had to sync in to the ad and used this site: http://info.izzy.org/Blog/archive/2010/08/04/how-to-fix-an-out-of-sync-password-issue-in-sharepoint-2010.aspx
Then i found out that the problem was that SharePoint Timer Service wasnt running och the Front end server. So I had to do an iisreset on the front end server to get the Service to start, since the account using the service was the account with a new password. And then everything was back on track again!
in my case the problem was secondary replica of Always on Was Empty and does not have Config database
i have configured an always Solution and at start i connect sharepoint to alias via cliconfig.exe and alias was connecting to AG listener
fail over back to instance where Config db exists solved my problem