Thursday, 2 March 2017

"Asus: In Search of Incredible" Amounts of Bloatware!

Recently I bought an Asus Vivo PC Stick. God knows It's unusable out of box.

When I saw it first thing came to my mind was "who is this product's product manager and how can he or she allow such a bad experience to go out into the wilds". It's ridiculously slow because of Asus's maniacal obsession with bloat/crap wares. And then I thought "that's actually ok! I'll upgrade it to the latest Windows Version (1607) and then do a 'Reset this PC' option from the recovery menu. This will get rid of everything that's not Microsoft."

Right? Am I right? Right?

God NO! Nothing gets rid of those horribly machine slower crapware. Nothing you can do cleans nearly everything from this computer. It's horrible. Later on I uninstalled most of the craps manually. I Deleted some files so Windows can't start the stupid Asus services at the start-up etc... and now it is behaving normally & operating with an acceptable speed and it's usable.

However I really wonder if Microsoft is aware of this situation? I mean that "Reset this PC" option won't work. I also wonder if they have anything to say about it.

Anyways before I put the screenshots, lastly I must write that I hear it is not this way with Asus only for this PC stick business. It's true for notebooks and phones also. So what I suggest is think thrice before you buy an Asus (software installable) product if you seek performance. Because you know I'm actually incredibly happy with my Asus Strix Headsets.

Here's the screenshots;





Monday, 27 February 2017

Harry Potter and the J.K. Rowling’s Nazi Love!!?

Hello everyone. Long time no see. I’m back but this time with some strange news. We are going to stray away from the technology a little bit this time. So excuse me.

Apparently all those Nazi symbolism in Harry Potter books and movies are not for nothing.

There are some photos recently surfaced that speaks for themselves, and sources quotes; “the author J. K. Rowling herself finds dressing up as Nazis to costume parties is very arousing.” And most of all and most troublesome part is that she does not condemn such photos and behaviour.

This is very problematic on so many degrees. First of all even this is 2017; the subject is very delicate. What someone finds arousing could be very offensive for some other souls. Dressing up as Nazi and writing books and producing movies filled with full of Nazi symbolism could be damaging not just one’s persona but to also the companies to work with. In this case for instance Warner Bros. When the next movie of hers hit theaters it will quite possibly be a PR nightmare for them. Knowing that the giants they are, after all they are Warner Bros., it will not be as problematic as 2016’s Ghostbusters fiasco for example; I imagine. Remember the whole social justice warriors issue and the dislikes on YouTube? What I am humbly trying to say is; still in this age that every trend is driven by the power of internets and social media, I believe every network should avoid such troubles online no matter the cost. Because no one can guestimate the real damage till it occurs. And by the time it happens it is almost always too little too late. Damage is done and cannot be undone.

One can ask again in this age of mis- and disinformation what is fake or what is not? What is out of context and what is cherry picked and served? What can I tell you? The answer is rather simple. One have to do some research. Examine some info, give a chance and the benefit of the doubt to the subject in question.

Of course you can read click-bait headlines and roll with them on your own risk. Besides; if it is on the internet, it must be true. Right?

Thursday, 26 June 2014

Virtual Datapower First Configuration and Initialization!

Finally I got my hands on with DataPower Virtual Appliance. It was hard to tinker on real environments. Even using them as your lab environment is somehow bothersome. But having a virtual one is very good since one can do most of the software tinkering without having to worry.

I will show you how to get the thing up and running with admin gui, in fact it is so pretty easy; this whole post is like unnecessary.

Once it boots the first screen we saw is login screen. It is dummy at this point. Just type admin for login name and admin for password...

After that it asks if Disaster Recovery mode to be enabled, say yes,

Just right after it is going to ask a new password, not every password will be accepted. Type a secure one,

Then it is going to ask if wizard is to be used. 'Yes' is the answer,

First to be configured is Network. It is also true for the hardware variation. Until network to be configured, we use the serial telnet connection. It holds true for virtual one, in theory we are using the console port right now. No interface has ip yet, configure as needed. I use dhcp for all 4 interfaces, VM host side interfaces should be 'bridged' not NAT. Least until initial configuration part is done,


Step 1 (network is completed), now is time for the step 2 and 3. They are easy, give a DNS and unique identifier... Such as;

Step 4-5-6-7 are also easy, screenshot is below and pretty much self explanatory;

Now it is actually done but we cannot use DataPower yet. We need to accept the terms and license. This can only be done via the Web-GUI. it actually tells how to enable it, type it exactly...
 

web-mgmt
admin-state enabled
local-address 0 9090
exit
 
open up a browser of choice. Type the first interface's ip like http://x.x.x.x:9090 then accept the terms. If you do not know the ip that it took from dhcp type "show interface" without quotes.
 
In the console now you can write mem and save the config. That's it. You can use you DPXI52 virtual appliance as if it is a real one.

Sunday, 13 April 2014

Hostname Change for WebSphere 7+

Hello, this post is also about WebSphere. As you may prolly know WebSphere family is a `hostname dependent`, uhmm let's say, architecture. If you want to migrate your server or even take a clone of the OS and sysprep it and start it, you are going to need some extra steps to start Websphere correctly. Even many cases without below steps you may not be able to start even Deployment Manager. Frankly the errors WebSphere generate are also no help at all, messy and confusing. So doing as below will save you a lot of trouble.

Let's assume you successfully migrated your server (or clone etc...), everything is in order and starting WebSphere is the next thing in place. Great! As you are aware since we cannot start DMGR and wsadmin.sh connects to DMGR upon initialized we are in a little bit trouble. We need to start wsadmin.sh without connecting, fortunately IBM thought a parameter to do so. In some cases this parameter is unnecessary, cause if it cannot connect to an active DMGR it simply goes offline mode, this is exactly what we need but most of the cases it will give and error and you are not going to be able to do anything with it. So let's be safe and use the parameter. Start the wsadmin.sh under the bin directory of DMGR profile like below;

./wsadmin.sh -conntype NONE -lang jython

After this we have 2 choices to change the hostname config of the DMGR. An interactive one and a automated silent one. Let's do the interactive one. You can easily automate the process if you write some python code. Type the below command to start interactive mode;

AdminTask.changeHostName ('[-interactive]')

*Node Name (nodeName):

type the nodeName of the DMGR node. Usually people use dmgr01 or something like that. Type it an press enter.

*Host Name (hostName):

Type the new hostname. This hostname should be pingable from the machine you are working on. So if there is a dns suffix or anything type it as it should be.

System Name (systemName):

Type the name of the cell that the DMGR manages.

Regenerate Certificates (regenDefaultCert):

Just press enter. This'll generate the cell and node certificates so the dmgr and nodes can talk to each other securely as before. It is at this point an unavoidable thing to do in fact. You can change them later if your company's internal security dictates or anything like that. Anyways press enter and let it renew them.

After that, it'll ask to finish or cancel it;

Select [F, C]: [F] F

Finish is the default answer. Just press enter or type F and press enter. It'll give the wsadmin command line back. We should save our new config;

AdminConfig.save()

After saving the config we can exit.

At this point our DMGR is in working order once again. But if we have any other node on this machine, we should change their hostnames too... Let's start wsadmin.sh the same way and start the interactive way and change the hostname for the other node. Below the commands and an example;

AdminTask.changeHostName ('[-interactive]')

*Node Name (nodeName): AppServerNode01
*Host Name (hostName): newhostnameoftheserver
System Name (systemName): wascell
Regenerate Certificates (regenDefaultCert):


Finish it and save the config just like we do for DMGR. Exit the wsadmin.sh for good and return to shell or command prompt.

We still have some work to do, as this is not enough; nodeAgent won't start if you try to do so. we need to manually sync the node, so node will know the new configuration and start correctly. Go to the profile's binary directory.

sh syncNode.sh DMGRHOST DMGRSOAPPORT

Type the username and the password if the console security is enabled. Let it sync itself. That's it, now the node agent should start normally and we are done.

PS: If you are doing all this when your original server is running, there is a probability that new dmgr connects to the old machine's working nodeagent. I know it is silly, just to be safe after all this just restart the dmgr and nodeagent one last time and you are done.

Thursday, 3 April 2014

WebSphere Messaging Engine and Stuck Messages

Hi, in this post we are going to do some house keeping to WebSphere Messaging Engine. In some cases messages got stucked in committing or removing state (IBM calls them indoubt messages). When that happens, it is impossible to manage them via administration console.

Service Integration > Buses > xyzServiceBus > Messaging Engines > abcMEBus > Queue Points > queueA > Runtime > message > delete etc...

So we need to use wsadmin.sh and some commands. I always use the wsadmin.sh under the DMGR profile. So start the wsadmin.sh and connect to DMGR, type your username and password if your cell is secure. What we need first is to get the correct message id. Use below command;

$AdminControl invoke [$AdminControl queryNames type=SIBMessagingEngine,*] getPreparedTransactions

This will give us a very long string, expect something like

!V0FTRAAAACQAAAFC72342347HesQAAAAIAAj8tAnvvXi34ge4rh5tjhe4f43e3wov5krh54i-r62ZrKqTBuEAAAAAAA2AAABQu*x3rEAAAACAAI-LQJRGDRHDRGS7714qL*ZK432fw4r2eeIv6*tmayqkwbhAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAAAAAC

Did you get such an id? Good. Now we are going to use this id in another command.

$AdminControl invoke [$AdminControl queryNames type=SIBMessagingEngine,*] commitPreparedTransaction msgid

Do not use quoation or anything just paste the message id we got from previous command as a whole instead of where I wrote msgid in italic.

This will commit any stuck messages in any state, if this does not solve your problem we have another parameter for rolling back the message.

$AdminControl invoke [$AdminControl queryNames type=SIBMessagingEngine,*] rollbackPreparedTransaction msgid

This will rollback, but I usually don't need to use it, committing manually solves almost all stuck messages.

Have a nice debugging.